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: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2018-01-09T00:26:13+00:00

    It is up to AMD to patch it. They made it.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2018-01-09T00:23:06+00:00

    No good for me personally, because mine is an AMD Athlon 64 X2 Dual Core and there are no provisions for a patch.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2018-01-09T00:02:09+00:00

    Users of Intel are invited to visit https://www.intel.com/content/www/us/en/support.html

    and download the Support Tool

    Was this answer helpful?

    0 comments
  4. Anonymous
    2018-01-08T23:54:14+00:00

    If you're waiting for a fix for your CPU why not install from 

    https://support.amd.com/en-us/download

    instead of for them to send one through to Microsoft and get it there?

    Advanced Micro Devices is not a division of Microsoft.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2018-01-08T23:46:02+00:00

    If you had chosen F1 debugging *(with your W10 disk in)*you would have rolled back the incompatible update.

    There were 10 option but F1 will not resolve the issue of rollback without the W10 disk.

    Was this answer helpful?

    0 comments