Windows 10: Windows 10 update: endless failed installation reboot Feb 2017

Hi,
I work in IT in a University and last week I prepped and set up a number of W10 computers for Student Admin DYI use. Everything up to date, tested, functioning smoothly. Today, (first day of classes and I go in to just make sure) and the computers have been bricked by an update. Endless 'Installation failed, press any key to restart' and on it goes. Safe mode doesn't work. Win10 install Disc Repair doesn't work. Nothing works. This is totally unacceptable, particularly when advice received goes along the lines of "If you are stuck in a reboot cycle please go to the control panel and .....". We have resigned ourselves to the inevitability of a complete rebuild and a huge delay/cost associated with that. I will point out that no cloning/dsim or other reproduction techniques were used. This was a clean individual install of W10Ent to several machines. We have applied for extra manpower solely to deal with the expected W10 problems but I'm getting the feeling that the unexpected ones are going to require even more. This is not a suitable OS for mission critical situations (and this is not the first major stoppage, we have 2 surface pro 4's on their way back to MS for un****ing, and I have a list of tickets with similiar inquiries/faults). I use to think I was a Pro in IT but W10 has reduced me to damn near tears. Just saying.

:)

 

fail to install Cumulative Update for Windows 10 Version 1067 for x64-based Systems (KB3206632)

Hi, PA Bear:

Since Windows Malicious Software Removal Tool for Windows 8, 8.1, 10 and Windows Server 2012, 2012 R2, 2016 x64 Edition - February 2017 (KB890830) and Security Update for Adobe Flash Player for Windows 10 Version 1607 (for x64-based Systems) (KB4010250)
were installed to my computer successfully on Feb. 24, 2017, Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB3213986) comes back to my computer again and it installs and fails to install every time I turn on my computer.

What should I do?

Thank you.

 

Windows 10 Anniversary Update Reboot in endless loop

I updated my HP Windows 10 Pro laptop with the recent Windows 10 Anniversary update. It was successful for the most part however the last update reboot went into an endless loop for more than 24 hours, so I have tried Shift+F8 at Power-on and the self repair
has failed, the rollback to previous install has failed, now I am doing reinstall to factory setting while saving my data. It has also been in endless loop for more than 12 hours. Can someone please suggest a solution?

Also I had the same endless loop reboot problem on my Desktop upgrade, however I was able to overcome by aborting the reboot with Ctrl-C. I suspected that my Norton Antivirus may be keeping in the endless loop so I uninstalled it. My desktop issues is now
resolved.

However the same Ctrl-C is not working on Laptop. Also my laptop does not have antivirus but Windows Defender, so it is not the same issue there. I suspect it is some driver that is not compatible, but I not sure how to override or rollback to previous install?

 

Hi, I sympathise with your plight- fortunately not one I've experienced.

Others may have better ideas.. but noting you've not had a reply...

a. Can you invoke system restore by booting from a Win 10 install disk, then click 'Repair your computer' and navigate through Troubleshooting to System Restore?

b. Failing that, and this is significantly less than ideal, can you restore the backup copy of the registry?
Boot from e.g. a Win 10 install disk or bootable disk such as Kyhi's at the top of the Software and Apps section of this forum

The Windows 10 backup copy of the registry is under:
C:\Windows\System32\config\RegBack
Boot up the PC using WinPE or Installation Disk into command prompt and copy all files under RegBack to C:\Windows\System32\config

https://www.tenforums.com/attachmen...cture1.png?s=c1e8b753a573dc6e5ffc1ac8c4009171

(This will probably leave inconsistencies between some files and the registry, and I can't advise how you might reconcile those simply).

I'm wondering whether you have ever considered the routine use of disk imaging so you have a quick way of recovering?
Also whether you have considered any of the various was of restricting Windows updates so that you can test them before general deployment?

Windows update log files
You are probably aware of this, which seems to make accessing them in this instance remarkably challenging.
You'd have to extract them and process them on another machine, unless perhaps you can do that having booted using Kyhi's boot disk.

This indicates where they are located:
https://technet.microsoft.com/itpro/...ndowsupdatelog