Windows 10 TP2 (10041) installed fine, then rolled back to 9926 - Why?

[Elliot B.]

Is there somewhere in the OS/logs that I can find out the reason?

[Ishami]

Exactly what mine did. I left it over night, I come back and its frozen, so I hard power off and it rolls back and now I can't get it to find the update again.

[Elliot B.]

Exactly what mine did. I left it over night, I come back and its frozen, so I hard power off and it rolls back and now I can't get it to find the update again.

I used my PC for a few hours last night, no issues. I turned my PC back on this morning and went to work. I tried to connect to the PC via. TeamViewer roughly 3 hours after it was turned on, as I always do, and the program showed the PC was off.

 

I called someone near the PC who told me the monitor was showing the Windows Boot Manager. When I asked them to press Enter, they told me 9926 was being restored.

[Defcon]

Windows 10 builds are a disaster so far, and the upgrade/install process has a mind of its own. Have never seen such an unreliable upgrade process in Windows before.

[theyarecomingforyou]

I had something similar happen with some of the earlier builds, where it would do the entire install process and then rollback to my previous install. I ended up moving back to Windows 8.1. It's disappointing that there are still major issues with the install process, which needs to be robust if major updates are going to be rolled out to all users after it goes final.

[Jackaluichi]

Agreed. I still can't see how they're going to meet the summer window release. No pun intended [emoji14]

[PGHammer]

Agreed. I still can't see how they're going to meet the summer window release. No pun intended [emoji14]

I had it happen on the Enterprise side - the issue was a corrupted ESD. A cache flush and re-download fixed it.

The Pro side (from 10036) was fine (earlier the same day).