Updated to 1903 but 'user'.000 now created and holds all my user files

Same here. I've rolled back a couple of times now, on two computers, using drive images from external backup. When I talk to MS support, they seem never to have heard of this problem.

I too have wondered about the mention of Zune files causing a problem. I have Zune software installed (and use it, for my Zune), but on my computer the Zune files don't show up under AppData.

Same here. I've rolled back a couple of times now, on two computers, using drive images from external backup. When I talk to MS support, they seem never to have heard of this problem.

I too have wondered about the mention of Zune files causing a problem. I have Zune software installed (and use it, for my Zune), but on my computer the Zune files don't show up under AppData.

I found that the MS roll back facility provided under 'Settings/Update and Security/Recovery/Go back to previous Version of Windows' worked fine for me, rather than using my backups.  What I did before backing up was looked in my old user profile (without the 000) to find the files which were causing the update to fail, and in my case they were ZUNE files.  They were not easy to delete and I failed to keep a log of what I did, but I remember googling 'how to remove ZUNE files' . . . I seem to remember that they kept on popping back up every time I deleted them, and I had to stop some service(s).

So I then rolled back, deleted the ZUNE files from my profile, then installed the update successfully.  I don't use ZUNE now, so was happy to delete the files.  You may need to restore them from backup if you follow my procedure?

Good luck.

Same here. I've rolled back a couple of times now, on two computers, using drive images from external backup. When I talk to MS support, they seem never to have heard of this problem.

I too have wondered about the mention of Zune files causing a problem. I have Zune software installed (and use it, for my Zune), but on my computer the Zune files don't show up under AppData.

I found that the MS roll back facility provided under 'Settings/Update and Security/Recovery/Go back to previous Version of Windows' worked fine for me, rather than using my backups.  What I did before backing up was looked in my old user profile (without the 000) to find the files which were causing the update to fail, and in my case they were ZUNE files.  They were not easy to delete and I failed to keep a log of what I did, but I remember googling 'how to remove ZUNE files' . . . I seem to remember that they kept on popping back up every time I deleted them, and I had to stop some service(s).

So I then rolled back, deleted the ZUNE files from my profile, then installed the update successfully.  I don't use ZUNE now, so was happy to delete the files.  You may need to restore them from backup if you follow my procedure?

Good luck.

Huh. I find Zune files under Program Files, but not under my user profile, so I'd guess that's not the problem in my case. I've already rolled back from a disk image, so I can't check what was left in my original profile after the creation of .000, but there were a few things. I wonder if they had the same effect as the Zune files in your case.

I had to use the disk image restore (one time, at least) because MS tech support had me do a "clean" install of the update--which failed just as badly as the regular, but left me without the option to roll back from within Windows Update.

Is there a solution for this problem yet? I have the same issue since the 1909 update.

I spent several hours on the phone with Level 3 MS tech support, and got no solution. I tried to make it work, but Dropbox was a hopeless tangle, and I could not get it to work correctly with the .000 user profile, nor would Outlook work even after I redirected it to the new data file location. I decided to roll back to ver. 1803 -- again -- but that was only partially successful.

I am now waiting for a full restore from disk image to complete, and then I am going to try to disable Windows updates in the Services sections and stay with 1803 for as long as my computer lasts, or until I have a week of spare time available to do a clean install of the update and rebuild my platform from the ground up. (Not likely to happen.)

I am really tired of the shoddy engineering and testing that leads to these situations.