StevensNet.com

...Because someone's gotta tell the story...

Blogs

To return to the main Blog List, click Full Blog Listing.

Tags

Error
PowerShell
Technical
Troubleshoot
Windows

Windows 10 and broken updates: Part 1

Sunday, April 10, 2016 in Technical Articles (Views: 1576)
Seems since Windows 10, a lot of Windows has become more "hit and miss" when it comes to Windows Update.

One such issue I noticed was with KB3140768. Some of my Windows 10, it works fine, on one, it doesn't. It is a bit annoying since the update installs, I go through the reboot, and am forced to wait for the rollback. Of course, Microsoft loves to tease and move things, so I go to my favorite windowsupdate.log to troubleshoot. I find a file with the following.

Windows Update logs are now generated using ETW (Event Tracing for Windows).
Please run the Get-WindowsUpdateLog PowerShell command to convert ETW traces into a readable WindowsUpdate.log.


You can run this command for a nicely formatted log file on your desktop, but I humored it and went to the event log and found this little gem, although vague.

Installation Failure: Windows failed to install the following update with error 0x800F0922: Security Update for Windows (KB3140768).

An error code - I can work with this, or maybe not. It means "Failure". I'm pretty sure it didn't take a seasoned engineer to figure that one out.

So, I decide to download and install it manually. It appears to go through fine, and then on the reboot, fails as it did before.

Next, I rebuilt Windows Update and installed the update automated - failed, and manually - failed. You wonder why people can hate Windows.

From there, I did a system scan - and got the following.

C:\WINDOWS\system32>sfc /scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection found corrupt files and successfully repaired
them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For
example C:\Windows\Logs\CBS\CBS.log. Note that logging is currently not
supported in offline servicing scenarios.


Happy day, something appears to be broken and fixed. Well, I wouldn't take too much credibility in Microsoft fixing any of the issues they create. Anyone used startup repair before? I believe it's hardcoded to say "we can't fix your problem".

Since there were no issues after doing the system scan, I didn't have to worry about using DISM to do a health check, it would come up clean, but did anyway. The results?

Deployment Image Servicing and Management tool
Version: 10.0.10586.0

Image Version: 10.0.10586.0

[==========================100.0%==========================]
No component store corruption detected.
The operation completed successfully.


No surprises there.

More to come on this, as the saga continues, including the typical Microsoft responses on the forums.

 

Related Blogs You May Be Interested In:


To leave a comment, please log in and/or register.