This was true in the past, but the practice has since stopped.
What the OP did was attempt to migrate their existing docker based Windows node to a Windows binary based node. They put in the wrong path to the data folder during the setup. Simple mistake, but still user error (no offense @zyvier, could have happened to the best of us).
There is nothing we can do to review already dqed nodes. Making support tickets will not help. We can only tell the SNO the same that was already explained here in this thread. There are no exceptions.
yeaā¦ no worriesā¦ mistake doneā¦ already in the process of deleting the data setā¦ hope iāll be able to get new data soon! =D
The only time we restored paused nodes was while we had some bugs in the system that resulted in some nodes getting unjustly dqed. This is no longer the case now. There are proper instructions in the documentation that caution SNOs to be very careful about properly specifying their storage folder when migrating from docker to windows gui. The documentation is not incomplete or inaccurate regarding this case.
Yeah I gathered from the posts what he did and why he did it.
I just opened the document linked above and while step 2 says to point it to the exact storage folder, being italicized isnāt 100% clear to me of what to do.
Speculating, but if the OP missed the meaning of an italicized word and pointed it to the root folder instead of the sub-folder called storage, I could understand there being a level of confusion. Especially, if someone is a hobbyist, new to pc, etc.
While there may not be a claim/review process and DQ means complete and utterly DQ - maybe this chat will help identify needs for document clarity, polishing, and updates when incidents happen.
We specifically put a paragraph with an orange exclamation mark in the documentation to alert the users not to make the mistake of pointing to the wrong folder:
Do NOT copy the path from the old config.yaml of your Docker node where the storage subfolder was not explicitly included in the path.
I donāt know how we can make this any more obvious.
Do NOT copy the path from the old config.yaml of your Docker node where the storage subfolder was not explicitly included in the path.
Well the OP would need to comment on how he missed it and made the mistake that he posted. So while only one case of a failed conversion isnāt a mass problem that would warrant review, it did happen and no document will always cover every use case.
Maybe this will help someone else who didnāt realize what an italicized word meant.
Italics, bold, underline or ALL CAPS are used to emphasize the said words.
We even included a screenshot where it is clear that storage is the name of the subfolder 
Oh yeah I get it. I donāt personally think I would have made the mistake and assume many other Windows SNs have made a successful upgrade.
I was just trying to help a brother out and see if he himself could explain his actions/mistakes in a manor to justify a review of his DQ. Never hurts to ask, can always just say no.
The fast that the OP acknowledged his mistake and moved on shows that there was no validity behind the mistake and it did not warrant writing to support seeking a review in his eyes
Yeah again not sure why the OP missed all the warnings now that I have opened the document linked above. Heck maybe he didnāt even see the document and just double clicked on an installerā¦
Only he knows the true story.
And while I love playing the devilās advocate and trying to find loopholes to gain advantages, this wouldnāt be one to climb up a hill for.
Sometimes the only way to learn something is to make the mistake on your own. Then learn from the mistake you did.
okayā¦ so i got my new node running nowā¦ with a new auth token, so new identityā¦ hmmsā¦ but my node id stays the same even after i reinstalledā¦ made sure i cleared the program folder etcā¦
is that expected?..hahaā¦ because iām seeing the node disqualified on startup 
sounds like you are still pointing to the old identity
oh yea youāre right!.. must have copied the identity files wronglyā¦
its up and running now! thanks heunland! =D
It would be nice if the email alert system would notify users of failed audits in addition to the node being offline.
You can post this idea on ideas.storj.io 
I think that this can be somewhat difficult to understand.
If i didnt know about this, im not sure if i would understand this, probably after I read it a couple of more times.
And I consider myself being good at English.
Maybe something like ,
Dont use same folder as in docker āe.g e:\storjā,
from docker to Windows GUI use āe.g e:\storj\storageā
The technical and programing skills in this forum is amasing, but I do think that the understanding of the English lanuage can make it difficult for many.
I know that i have a hard time to understand alot of the cumputer language.
Good night. Time for me to sleep
