Windows 10: Cumulative Update KB4093112 Windows 10 v1709 Build 16299.371 - Apr. 10

Keep getting the error with System Restore when i try to open it after Windows was updated, everything else seems ok.

 

Is there a restore point? If any, try to create a new one.

PowerShell admin:

Code: Get-ComputerRestorePoint[/quote]

 

I initiated Windows Update and found this update. It downloaded and attempted to install during active hours; WU message indicated it failed with error code 0x800705b4, but there was no record of it in Update History. Attempting to reset Windows Update failed because update service (wuauserv) failed to stop.
Ran troubleshooter after shutdown and reboot and got message "pending system changes require restart".
Restarted and installation began. When the system came back up, I checked Windows Update and got "system is up to date" with no error messages. Update History showed installation had failed with error code 0x8007139f.
However, it is on the list of installed updates on the uninstall updates page. Both the system's OS Build info and winver show Build 16299.371.
This leaves me with questions: should I uninstall/reinstall the update? Should I let WU troubleshooter uninstall it if it wants to? Should I let well enough alone?
How I wish one could actually learn something from these episodes . . .

 

Alongside with this CU there was the other one - for Adobe Flash. Interestingly, it kept saying of a system restart pending as well.

It seems like a system restart is NOT recognised by Windows Update for whatever reason.

 

In my computer, the cumulative updating is getting stuck while downloading at 100%. Ran windows update troubleshooter a couple times, but always end up halting at the 100% mark. *Sad

 

[/quote]
Did it, but nothing happened. I cannot create restore points either.

 

Ten seconds upon executing the following code

Code: SC config wuauserv start= auto SC config bits start= auto SC config cryptsvc start= auto SC config trustedinstaller start= auto[/quote] a proper system restart initiated, now I have both KB4093110 and KB KB4093112 show up in appwiz.cpl in windows updates, status installed.

Yet the list of installed updates in Settings - Windows Updates still has a reference to the previous error...

 

Downloaded manually and then installed, successfully.

 

Do you have another AV? If yes, try disabling it. A new program installed recently nay also cause this. Check the link below for help.

http://www.thewindowsclub.com/system...orking-windows

You may also try the troubleshooting section (Settings)<< program compatibility troubleshooter> to see if it helps.

 

Updated three PCs today (my own and other two at work). No issues here.

 

Why not trying to reconfigure System Restore in its properties dialog box. Put everything that is "On" to "Off" by clicking on Configure. After that, reboot your PC and go again to System Restore's properties dialog box to put everything back "On" again. Once done, try to create a system restore and see if that works this time around.




That has usually worked for me in the past when I had this kind of problem with SR.

 

a proper system restart initiated, now I have both KB4093110 and KB KB4093112 show up in appwiz.cpl in windows updates, status installed.

Yet the list of installed updates in Settings - Windows Updates still has a reference to the previous error...[/quote] That's normal. It's a log file entry. Simply what happened at a certain time. A successful install will not erase/delete the failed log entry. It's history.

 

Just dl and installed this latest update. All went well and my old ultra notebook is humming! *Smile

 

Leave it alone, winver is the last word on your current system version and you ARE up to date, sometimes WU doesn't always give accurate information. I've had the same thing happen before and it caused no problems, just leave things as they are. Unless you find an operation problem better to leave things as they are.

This kind of issue seems to be a regular occurrence with many users. But causes no other issues. *chuckle

 

Thanks. I did believe the update was installed, just don't want WU to be confused when the spring update appears. *Smile