Windows 10 Update 1903 renames User fiolder

I thought I replied to this to say I thought I managed to rectify the situation. I edited the registry to point to my non .000 profile which didn't work as the permissions weren't correct so I simply renamed the old profile so I could rename the .000 appropriately. After the first failed attempt (Windows created a temp profile) I got in on the 2nd try and OneDrive and other apps that were having problems previously seemed to be fine. 

Except Outlook, and then several more as I kept digging. It seems like paths to the .000 profile had started taking over. There were a TON of entries in the registry pointing to that path. 

Since I can't revert and this is where I'm at, I'm pretty much forced to wipe the system clean. I really don't have time for this but what choice to I have other than creating a new profile. At that point, I may as well truly start from scratch. 

Thanks Microsoft.

Thanks, @Dirge-san, @BobEadie & @TylerYanta.

Rather than mess with the registry, the safer option was to rollback to Win10 1809. Just prior to starting the restore, there was an option to troubleshoot, so I tried it.  It was hilarious that the first solution presented was this very thread!  :)  After going through another couple of suggestions I was given an option to get in touch with a MS CSR.  Spoke with a nice rep for 45 minutes who did all the troubleshooting mentioned in this thread (checking user profile folders, etc.)  However, with no easy fix, rollback was indeed the best option.  So I've done that, and I'm back to a fully working system Win10 1809.

Now I've uninstalled Zune (required using the MS uninstall troubleshooter), and disabled Plex Update Service.  The last set of files I saw in the 1903 user profile was related to "InputPersonalization" in C:\Users<USER>\AppData\Local\Microsoft\InputPersonalization

• I have not been able to find which service writes this file.  The brute force way to disable it was to rename the folder that contained the executable (C:\Program Files\Common Files\microsoft shared\ink).  Other things I tried were to disable "Allow Windows Ink Workspace" through gpedit, but Windows always recreates that folder.  Just found another related policy, "Text Input" which may be related, so I'm disabling that as well.

Now I'm making a full backup, and have downloaded Win10 1903 ISO image to attempt the upgrade again.  Not sure when I'll update, but I hope it will not run into the same problem.

If you have the Zune files on your computer, uninstalling Zune and running the troubleshooter won't work, at least in my case it didn't. The Zune file in question remained in my profile and started as a service when I logged on. The only way to delete it was to either stop the service and then delete the file, or to delete the file from another account with admin rights. I don't remember the filename or service, and neither is no longer on my computer, but I believe the file was in AppData/Local/Microsoft. I did it the first way on my desktop and the latter on a SP3 and a Lenovo T430. The upgrade then worked fine on all three.

   Renaming my .000 profile was not a good option for me, since a lot of information was missing. I had to reset a lot of things such as re-entering product keys for installed software. The worst was that my 3D printer reverted to it's default settings and I lost everything I had changed to fine-tune my printer to various materials. I did the rollback and waited for MS to fix the problem, which never happened. I did the upgrade/rollback several times over the next month or so but each time I still had the .000 profile.

  I'm surprised MS isn't aware of this, since it's an MS file. When I looked at the problem it didn't take very long to find a solution, and it took all of maybe two minutes to delete all the Zune files. All three of my Win 10 computers are now running fine under 1903. I have a Zune HD (that still works just fine) and reinstalled the Zune package on all three but I no longer see the offending file or service.

Am I stupid or doesnt this patch fix the issue?

KB4505057

Am I stupid or doesnt this patch fix the issue?

KB4505057

Hi Steve, could you share some more details about the problem you ran into and how you applied the KB fix the problem?