How Do I Block 2018-01 Cumulative Update for Windows 10 Version 1709 for x64-based Systems (KB4056892)?

Anonymous
2018-01-05T07:42:12+00:00

KB4056892 is Awaiting restart

Unfortunately, when I did a restart it bricked my system. I had a large windows logo on the screen and it just sat there.  I rebooted and was able to trigger a repair.  The repair said it was backing out the last update as it would not be completely installed.

With KB4056892 is Awaiting restart I did another restart and had the same problem.  At the end I was staring at a Windows logo that just sat there.

Again I triggered a repair and the system is now usable.  However, Windows Update still says: KB4056892 is Awaiting restart

How do I block it so it doesn't get installed if I have to reboot the machine?

Windows for home | Windows 10 | Windows update

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

210 answers

Sort by: Newest
  1. Anonymous
    2018-01-18T22:04:26+00:00

    I tried to use the wushowhide.diagcab on two machines and the update still installs and asks for a restart.. 

    The best I have found is to make sure your active time is 18 hours long to minimize the hitler forced install .. 

    and then during that active time when all the new updates are downloaded and ready to  go click install 

    and let them all install .. and then click on View installed update historyand on that page click on Uninstall updates at the top of

    the page and find KB4056892 and uninstall it and then do your restart ..  

    I HATE FORCED UPDATES !! ..  

    MS should be held liable or loss of data with updates in this mode .. 

    There was nothing wrong with the way windows 7 had it where we could choose to not install a bad update

    until it got fixed .. 

    Speaking of which ..  When is KB4056892 getting fixed ... 

    My son, a senior IT guy, says that if windows defender is up to date, then the odds of someone getting into your machine 

    in a way that is required to execute meltdown or spectre is extremely minimal.

    Which beats having your PC bricked by a force update.

    In my case I COULD NOT recover .. even with a backup .. 

    Though I could still dock the drive and remove any needed data.

    Randy

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2018-01-18T10:28:09+00:00

    I had the same thought process. Wait for another update to be released to fix whatever is borking machines. 

    Mine gets stuck on the Manufacturer's loading screen and then the fan noise reduces and virtually no disk spinning noise. Its like its completely idle just displaying those spinning dots. 

    Had to System Restore twice now. From an imaged USB stick with a Windows image because apparently there is a known issue with System Restore regarding the C:\Program Files\WindowsApps folder.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2018-01-18T10:21:44+00:00

    It killed 1 of my machines. The machine has an Intel i7 purchased in 2014. The System Restore kept throwing an error on the 'C:\Program Files\WindowsApps' Folder. 

    I had to image a USB stick with the Windows Media Creation tool and then that failed. I had to update the machine I imaged the USB stick with (luckily that machine, though 1 year older than my main machine with an Intel i5 was able to update without issue). 

    After the second machine updated I was able to redownload the Media Creation Tool and properly image my USB stick and then boot from the USB stick on the main machine and use the System Restore utility that was on the USB stick.

    So yes. I would love to know how to keep the Windows Update from happening. I disabled the Windows Update Service and it still enabled itself and started to download the update again. I noticed because I was on a Skype conference call and everything stopped. My disk and CPU were pegged. 

    Tried a reboot and it tried to update then died again.

    Just was able to successfully System Restore to 2 days ago... Please help to disable these updates. I need to wait for a few rounds of updates to see if they fix this issue before letting my main machine update.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2018-01-17T22:45:17+00:00

    Installing this update manually before the broken update had a chance to install fixed the boot issue on my AMD Athlon64 X2. Thanks for the link!

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  5. Anonymous
    2018-01-17T22:42:26+00:00

    Still having the same issue here with W10, and Intel chips. Turned off auto through local services for a week and turned back on. System goes through update mode only to set at system restart, and then only to get a message that update did not complete. So I thought I'd go to Intel's drivers and software site, and found out the site is under maintenance...Hmmmm, evidentally this security patch is still being worked out.

    Was this answer helpful?

    0 comments No comments