Forum Discussion
Not able to start desktop after update disrupted
I am updating to the fast ring latest build 17682 and stucked at 98% for 2 hours and was forced to disrupt the update. After the computer rebooted, it will keep staying in the login screen for 4-6 min...
Okay let me get and update on the situation, as well as I get and external backup and all my files were save, I have done some testing on that drive.
Before I reinstall Windows, I have try login to the system and wait to see the action, I tried to restart explore.exe and as I stated before icon reappeared, but when I press on any of the given icon it stated that token was not found.
( So I assumed this is related to the user profile begin corrupted during update, and I think actually open a new account on the PC will help get to normal use but the old files are sure dead)
I use another same model drive to reinstall Windows and plug the original drive in, and discovered that only files inside the user account are dead and my other documents saved in location out of the "user" folder we're all save.
I would like to hear updates from the Microsoft team as I sure this issue isn't just lucky happened to a small gruop and have potential to break other systems if just like ours the update are not able to proceed.
Before I reinstall Windows, I have try login to the system and wait to see the action, I tried to restart explore.exe and as I stated before icon reappeared, but when I press on any of the given icon it stated that token was not found.
( So I assumed this is related to the user profile begin corrupted during update, and I think actually open a new account on the PC will help get to normal use but the old files are sure dead)
I use another same model drive to reinstall Windows and plug the original drive in, and discovered that only files inside the user account are dead and my other documents saved in location out of the "user" folder we're all save.
I would like to hear updates from the Microsoft team as I sure this issue isn't just lucky happened to a small gruop and have potential to break other systems if just like ours the update are not able to proceed.