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

210 answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2018-01-07T21:43:51+00:00

    Thanks to Peter Leadbetter for his post! The method he described has prevented the installation of Cumulative Update for Windows 10 Version 1709 for x86-based Systems (KB4056892) .

    Background:

    I own two (of my three) computer systems which use very old AMD chips. In fact, both system are over 7 years old and perform well with Windows 10 Pro, 32-bit, Version 1709. Each system chocked after the installation of KB4056892. The hang up was at the Windows logo, which occurred after the reboot to complete the installation. 

    Briefly, here are the steps that I had attempted but which failed:

    • I used wushowhide.diagcab in Advanced mode to automatically find and apply fixes for the update process. This utility found a problem in each computer and actually applied a fix for KB4056892 (!). But then I allowed a reboot and encountered the identical hang up problems. I had two computer bricks again.
    • Next I used msconfig to force a restart of one computer in safe mode. This did not resolve its problem, so I abandoned repeating this on the second computer.

    As stated above, the only recourse I had was to block the update for KB4056892.

    • I used wushowhide.diagcab to hide KB4056892.
    • Each computer applied its pending updates, and both booted successfully.

    My third computer system is based on Intel i5 and runs Windows 10 Pro 64-bit Version 1709.

    • KB4056892 installed successfully without any assistance.

    Final comment:

    I always take frequent backups and System Restore points of my systems! Otherwise, I would have many serious nightmares.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  2. Anonymous
    2018-01-07T21:54:56+00:00

    Windows Update says:

    How do you block KB4056892 when wushowhide.diagcab doesn't show it:

    Edit: Also, why doesn't Windows Update show any of the updates above?  None of them are hidden.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  3. Anonymous
    2018-01-07T22:25:08+00:00

    Dual-Core AMD Opteron 2220 2.79 GHz (2 processors)

    24.0 gb RAM

    64-bit Operation System, x64-based processor

    Windows 10 Pro (valid license)

    Every time this update is applied, I lose 30 min. rolling it back.  I have now blocked the update using the MS "wushowhide" package for hiding drivers which break things.  We'll see if it works.

    MS - I like Win10 Pro; it has some excellent features.  However, I would like to charge YOU my full consulting rate per hour for the time I have wasted on your "service".  This is a service?  I would be fired/dropped quickly if I treated our clients like this...

    Regards,

    E. A. Thomas

    Was this answer helpful?

    0 comments
  4. Anonymous
    2018-01-07T22:29:30+00:00

    Have you run this?

    https://support.microsoft.com/en-us/help/183887/description-of-the-windows-registry-checker-tool-scanreg-exe

    You may have a registry corruption issue; it's worth a check.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2018-01-07T22:40:57+00:00

    scanreg.ex or scanregw.exe are not part of Windows 10 Pro x64.

    Was this answer helpful?

    0 comments