I had the reboot loop issue. This is what I´ve done to fix the problem:
Go to: Control Panel -> Find and fix problems ->Fix problems with Windows Update. Follow the steps.
Well, it fixed some windows update components, that was the problem. Not sure if this can help anybody, but if it can, Good :)
I just checked and all the updates i had that were stuck in "Restart Required" are now listed as "Failed to install".
I checked for updates a few times and it says I'm up to date.
They never did get successfully installed.
I don't know if this means they pulled the updates, they aren't needed, etc. ...
I also had done a bare metal clean install of build 10130 since my previous post.
I see this on both the VM and bare metal installs.
I'm curious if others that had updates stuck in "Restart Required" still have them listed that way.
Hey there David,
That's just a static log and it is a bug in the way WU updates the information
To see the current status, go into
Settings > Update & Security > WU > Advanced > View update history > Uninstall updates > Installed updates
If the KB is in the list above, you have restarted your machine at least once, and the update is no longer offered, you're good to go.
IF it was a device driver that failed, you'll have to look at the driver in Dev mgr to know if it was updated successfully. I find this case to be a more annoying issue. Drivers often fail to install on this machine (who knows why ... it's preview code!) and that's what I see. The driver is not offered again because the device driver installation process resolves the issue behind the scenes. The user is not made aware of this and might wonder "Hey, how come it failed, and how come it wasn't offered again"
I'm not sure if I fed MS this one - but I will just in case (two of the same can't hurt)
Thanks for the info !Hey there David,
That's just a static log and it is a bug in the way WU updates the information
To see the current status, go into
Settings > Update & Security > WU > Advanced > View update history > Uninstall updates > Installed updates
If the KB is in the list above, you have restarted your machine at least once, and the update is no longer offered, you're good to go.
IF it was a device driver that failed, you'll have to look at the driver in Dev mgr to know if it was updated successfully. I find this case to be a more annoying issue. Drivers often fail to install on this machine (who knows why ... it's preview code!) and that's what I see. The driver is not offered again because the device driver installation process resolves the issue behind the scenes. The user is not made aware of this and might wonder "Hey, how come it failed, and how come it wasn't offered again"
I'm not sure if I fed MS this one - but I will just in case (two of the same can't hurt
Yes, I see these KB's listed in Installed Updates.
Ive been trying to install this update since it came out. I've had to clean iso install and had a million driver issues but now that thats fixed i still cant finish this update. it finally managed to get to 67% updated on reboot but then i get the update failed message and it ends up in a 3-4-9 time reboot loop trying to install it before it finally gives up and just boots without it. not only is the faied update annoying but the fact that every time i try to restart it goes through this loop is really getting on my nerves. Ive tried everything, and contact support has never opened on my computer as well as insider forum not updating my progress properly. all these problems are pretty major when you think about it and getting anyone from microsoft through the normal support channels is proving next to impossible
I am also having problems getting KB3070677 to install. Takes forever after restarting 4 times.
The problem still continues with KB3070677. Annoying to say the least. This particular KB is the only one not listed as installed. This plus four others continue to try and install, KB3058515, KB3069069, KB3070641 and KB3070675 even though they are listed with an "Installed ON date", under the update history, they are listed as awaiting a restart. Four iterations of "Couldn't complete the updates, undoing changes, Don't turn off your computer..." So now as soon as I see the windows logo, I do a CTRL-Alt-Delete to get me to the sign in screen. If this is a bug in 10130, I will just wait it out until next build.
Quote