New
#100
I installed with Malwarebytes Premium and Windows Defender running both real time. Didn't get that issue.
Cumulative Update KB4093112 Windows 10 v1709 Build 16299.371 - Apr. 10
-
-
New #101
Yes, MBAM free won't do anything. But I have seen Avast cause it. Seems like it puts the user into a temporary position, lets the upgrade go through, and then moves the temp user back to the original user (not the user's data though). I've seen this several times with Avast, and reboots have eventually resolved it.
-
New #102
Anybody else have the issue with an Update to Windows defender platform installing but then the next Definition Update failing? I got it working in the end but just curious
-
New #103
-
New #104
Yes!
Just done one of my test PCs which hadn't been touched since January as I've been away.
I downloaded the CU and installed it manually along with the routine updates. (Defender, SW Removal Tool, Flash Player.) Defender updated once, then refused the same update (???).
I rebooted, did a Check for Updates and it found a newer Defender update and installed it successfully.
Thus I went straight from OS Build 16299.194 to OS Build 16299.371 and skipped all the February and March updates.
Rebooted twice since and just looked at Event Viewer - all is good.:)
-
-
New #106
Anybody have runtime broker inexplicably fail since this update? Never had any issues with it before. Unsure what it is but I think it may be something to do with Cortana?
-
New #107
Not runtime but the start menu is occasionally crashing once a day for the last three days with MoApp crash & somthing along line of shellhostexperience.exe listed in reliability monitor. Wonder if is this update that caused it although I'm sure the start menu crashes only started at the weekend when this CU was installed a few days beforehand. Seems to be a daily crash that happens only the once and it immediately works again when I open start again. Could be the CU or a dodgy app live feed to blame or something cortana is pushing once a day.
-
New #108
Yet another Windows 10 fubar
My desktop wants me to reboot to accept this abortion. Hmmm ...
KB4093112 is the April 2018 cumulative update for Windows 10 Fall Creators Update (version 1709), and unsurprisingly, it fails to install just like many of its predecessors.
http://news.softpedia.com/news/how-to-fix-windows-10-cumulative-update-kb4093112-issues-520719.shtml
Unfortunately, the more systems get this update, the more users confirm the failed installs, and as we’ve told you already, the typical behavior is experienced every time: KB4093112 downloads correctly and prompts the user to reboot the system only to then fail with various errors, undo changes, and return to the desktop.The same cumulative update is then re-offered and Windows Update requires another system boot, only for KB4093112 to fail again and pretty much pushing the computer into an infinite loop.Microsoft hasn’t said anything about how users can address these problems, and there’s a chance nothing will be shared until the next cumulative updates ship on the May 2018 Patch Tuesday.
-
-
New #109
I had this issue with two cumulative updates when I had version 1703. I was getting message "... couldn't install updates, undoing changes.." I ran sfc /scannow command. It found problems and fixed them. Then updates installed OK.
My suspicion is that it is related to Cortana. I had Cortana app folder renamed so that b***h process doesn't run in the memory at all because I don't use it. It could've been something else. It is just my guess.
Try to run sfc /scannow and then try update again.
Quote
Related Discussions
