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

>Did you use WUT and allow it to delete all downloaded files?

I ran it and allowed it to do whatever it wanted.

I was then able to hide KB4056892.

I then ran:

net stop wuauserv

rmdir %windir%\softwaredistribution  /s /q

net start wuauserv

But KB4056892 is still showing as pending restart in Windows Update

I stopped updates all together till I see that Microsoft has fixed the AMD Processor problem with update (KB4056892).  The best and quickest way to stop updates is:

Type Services in Search

When in Services, go to WindowsUpdate

Do a right click and click Stop

Do another right click on Properties

Click on Disabled

At this point when you reboot you may still have an auto install on the bad patch.

So, cold boot it this time so as to get an Auto Repair going on the boot.

When you get that to finish it deletes the waiting bad patch and it won't try to get it again.

So the question is still how do you block KB4056892?  wushowhide.diagcab is useless as it doesn't fine KB4056892 which is waiting for a restart to install.

Obviously, KB4056892 has been downloaded since it is waiting for a restart to brick my machine.  Where is it so I can manually delete it from my machine?

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.

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.

Well if the problem is the AV then the problem is still Microsofts'. Since the only AV I have running on my PC is their very own Security Essentials.