New
#550
Hi Brink,
slightly different issue, but same result. I'll describe:
After one update in summer 2019 suddenly I started getting strange errors as if Windows could not find my data. The first to fail to login was MS OneDrive. I ignored it. Some 2 weeks passed, and I got the login error from your tutorial. I looked and I noticed <user>.000 new profile. I rebooted and the boot went fine. Beeing 2 weeks out I could not undo the update. Apparently MS screwed me over, on some error it created <user>.000 profile and 90% of the time it loggs into it without a problem. The 10% logins do this tutorial error, but simple reboot goes to <user>.000.
Apparently MS moved/copied most of the data to the 000 profile. But not all were moved, and some of the programs like MS own Onedrive continues to look into <user>.
I used your step 11 there is no .baks and .1001 shows the path to <user>.000. The other SIDs show proper paths. The whoami returns the <user> without 000.
Most often all works fine, with some programs I have to manually redirect the program to use <user>.000 for data. The biggest screwup is when working remotely and moving data around I end up sometimes saving to <user> profile instead of going to <user>.000. Clearly havoc.
Of course, MS could not care less - no help from them. Your tutorial is the closest to the solution.
The bottom line question:
Can I use the step 11 and rename the path back to <user>. Reboot. And simply move the content of <user>.000 to <user>?
Which folders/files not to move? What about the <appdata> folder and alike hidden folders?
FYI: months latter, on another few computers, after doing the Win10 major update, the very first thing I do is checking if <user>.000 was created. If it was, I immediatly am undoing the update (this option vanishes after I think 10 days) and do non-major update and few reboots. After that I allow the major update and every time the <user>.000 is not created.
Quote
