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

Anonymous

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?

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

210 answers

Anonymous

2018-01-07T20:47:36+00:00

I have a dual boot system Windows 7 Pro 32 bit and Windows 10 Pro 64 bit. Windows 7 updated just fine on my AMD unit, however Windows 10 just hangs on boot. This is even after doing a clean install.
Was this answer helpful?

0 comments No comments
Anonymous

2018-01-07T20:30:16+00:00

You should have in your possession, a self created DVD Windows 10 MediaCreationTool digital download.

It is the only tool that saved me and 'F1' was the debugging choice all the way to 'F10' that rolls the damaged file back to uninstalled state. You then install 'wushowhide' to block the annoying download until Microsoft can offer a fix for it.
Was this answer helpful?

0 comments No comments
Anonymous

2018-01-07T18:11:53+00:00

Same issue here. Windows 10 64-bit, tried to install 2018-01 update a couple days ago after reading articles on Specter and Meltdown saying to "install latest Windows and browser updates." Well that bricked my PC, took a couple hours of trying to fix and eventually do a system restore. Tried again today thinking "hey, maybe it'll work this time." Newp! One hour and one system restore later, here I am griping along with everyone else affected by this flawed update.
Was this answer helpful?

0 comments No comments
Anonymous

2018-01-07T16:20:54+00:00

I used my digital Windows 10 Disk and then went through the repair process. It could not repair and then I rebooted without any need for Windows 10 Disk and chose option F1 debugging.

It then rolled back the previous 2018-01 *Cumulative Update for Windows 10 Version 1709 for x86-based Systems (KB4056892)*and I was presented with the logon screen to sign back-in.

If you want to block this package file until Microsoft come up with a solution, simply download 'wushowhide' *Troubleshooting Pack Cabinet (.diagcab)*and this will stop its startup process.

You may download for free Here

If users go to Here and download the Microsoft Update Standalone Package (.msu), the file is downloaded whilst the user is in Windows and after reboot again, one is locked out with the startup blue logo 'hanging'. Microsoft were not aware of this anomaly at the time but I have now reported it to the technical dept and developers will offer a 'fix' after they have repaired the problem.

I have also reported it to the feedback hub app that resides on ones OS PC.
Was this answer helpful?

2 people found this answer helpful.

0 comments No comments
Anonymous

2018-01-07T14:45:58+00:00

From what I've read about WU for W10 Pro, the user can "defer" updates for several "days" or "months" but security updates will still be downloaded and installed. Secondly, you have the ability to prevent or delay the restart after the install. Bottom line, MS controls the PCs all together. Because even if you can defer or prevent the restart. It will only be for a limited window of time. Many non-Microsoft applications require restarts. So if there are pending MS updates, you then "complete" the MS update process at that time.
Was this answer helpful?

0 comments No comments