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: Oldest
  1. Anonymous
    2018-01-11T00:03:04+00:00

    If you had read a previous comment on here of mine, it referred to your system getting 'bricked' or locked out with a hanging Blue Windows logo.  I reminded others here that you must create a W10 MediaCreationTool DVD disk, reboot hitting any key and second time around boot without selecting any key still with the disk in your drive and selecting option F1 which is 'Debugging'.

    The 'KB4056892' file is then rolled back without any need to reset the system and lose your apps in the process.

    I used this method and everything was back to normal, and then I blocked the Windows update file.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2018-01-11T08:06:23+00:00

    >Now the question is: Is it safe to go back in the water and unpause Windows Update?

    No.

    I unpaused updates and did some other stuff.  Then I came back to the machine and rebooted to install some other software.  Got the big Windows blue logo and hung.  Rebooted and triggered a repair which said it was backing out an update that didn't completely install.  Finally, got the login screen.  Logged in as an administrator and paused Windows Updates.

    Will let the pause expire in 35 days before trying again.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2018-01-11T09:22:30+00:00

    Yesterday I had the same Issue with my Windows 10.

    What I did, is I wrote a "nice" message on MS Facebook site in German.

    In Germany we call this kind of software "banana software" . Send it in "green" state to the customer and wait.

    Why can't they handle updates like the Linux world does? Inform about updates and leave the decision to install to the user.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2018-01-11T18:18:19+00:00

    If you download the 'wushowhide' from this link…

    I've been following this thread because my father's machine is having this problem. The machine restarts by itself to install KB4056892. My father has had to run a System Restore several times already!

    I downloaded and ran wushowhide.diagcab as you suggested, and hid KB4056892. After it finished running, I checked the Windows updates, and alas specific update is downloading again.

    Will it merely download but be suppressed, or will it download and install?

    EDIT: KB4056892 has finished downloading and installing. So, we don't want to restart the computer, because it will mean going through the whole System Restore nonsense yet again. I just don't know how to stop it from installing!

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2018-01-11T19:22:59+00:00

    I can't fathom why you and many others appear to be having problems with the 'wushowhide' file from Microsoft.

    Once you hide this KB4056892 cumulative update, it is permanently blocked until such time you decide to release it back onto your system to be downloaded again. I would recommend that you run the 'wushowhide' one more time and check to see if this has fixed the blocking process.

    If not, go to your app folder and use the 'Get Help' app to talk to a live Microsoft technical support staff member. They will be able to assist you further with this gremlin.

    Was this answer helpful?

    0 comments No comments