New
#60
The first two tries I had to hit the restart button on the computer. The first try the computer went through the install but reverted back. The second try the computer only restarted. The third try I deleted everything in the Download folder and rechecked for updates then because it was getting late I went to bed. This morning I woke the computer and did the power option trick. Then I put the computer to sleep mode and used the power option to restart. What ever the difference it worked. The only noticeable problem I had was that Windows Update kept telling me I needed to restart to install the update. It did go away after the third restart.
Edit: after the second try I was beginning to think that I was going to have to use my Macrium Image.
Second Edit: I was wrong about the restart needed. When I clicked the Window button to put the computer to sleep mode the restart needed message was there.
Running sfc /scannow in CMD resolved the shuttdown problem for me in this build.
Since this Restart issue has been with the last few builds, I restored 18990, the one before they broke it, and updated from there. The repeating "Restart to Update" message went away. Still had the Restart issue like almost everyone, but the persistent Restart message on check for updates was fixed. I had a little more luck using the Power>Restart option on the start menu than the Restart Now on the install screen. Command line never worked for me.
Just saw this. Both Fast Ring test PCs had already downloaded and installed the updates to the "Restart needed" point. Just fired them off a minute ago, and the X380 Yoga is already into the Post-GUI restart, while the X220 Tablet is in the same state. I'll report back if anything odd or interesting shows up. Good stuff!
--Ed--
[PS added 15 minutes later: Blue "Restarting" screen with spinning balls is still running on both test machines. Occasional disk activity lights tell me "something" is going on but this is taking much, much longer than for earlier updates to work through the process. Anybody have insight into what's going on here? Do I need to break out and run dism restorehealth and sfc scannow first, then try again. Very strange!
The latest build (19002.1) = GTX 1070 3DMark Fire Strike to go from 17000 to 12000
I did use DDU a couple of times but reverted back to 18999.1 where the score is back to normal.
Oh, and the performance loss with 19002.1 was in every 3D application/benchmark, not just 3DMark.
After my earlier failure due to unworkable "restart" did your above workaround.
First retry encountered green screen which advised do not turn off computer as M$ were taking details.
Next try success....whether this was due to your workaround or M$ during their intervention, I could not answer.