Cumulative Update KB4093112 Windows 10 v1709 Build 16299.371 - Apr. 10
-
Did it, but nothing happened. I cannot create restore points either.
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.
-
Did it, but nothing happened. I cannot create restore points either.
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.
-
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
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...
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! :)
-
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?
. . .
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. 
-
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.
Thanks. I did believe the update was installed, just don't want WU to be confused when the spring update appears. :)
-
This update has confirmed issues. I just finished a remote access session with a MS support technician who said that the update was not tested and is incompatible with my device for now. The support tech disabled auto updates and told me to contact support sometime in the future when the problem may be resolved, and then I can update my computer. So I'm currently stuck at 16299.125 for a while :-(
-
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.
But there error prevent me to open that dialog box. I had to restore the system with a backup image i created recently and then install the update again and the problem is gone. I read from another forum member something about repository, but i read the message after i did the restore with the backed image i had.
-
-
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.
I received this reply after i did a restore with an image i have from before the update and then apply the update again, no problem so far, but i will try the repository thing if the problem comes back, thanks for the great help and advise, always grateful.
Quote
