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

This 2018-01 Cumulative Update for Windows 10 Version 1709 for x64-based Systems (KB4073290) is not being offered on my system as yet but ready to block if it shows any known issues as the previous one did.

see:

https://support.microsoft.com/en-us/help/4073290/unbootable-state-for-amd-devices-in-windows-10-version-1709

Released today.

can you tell me how?

Thanks 

My config:

i7 7th gen

Prime H270M-Plus Asus Mobo

I can't boot up repair from Windows 10 USB media tool anymore :(

the update also brick Intel chip.

I have I7 7th gen 7000, after updated to 16299.192 and was able to run some games until the system crashed, and now stuck in the preparing auto repair loop screen. it crashes blue screen of death in the middle of loading something...

here are random errors that i got each crash:

Bad pool caller

Machine Check exception

Page fault in non paged area

etc...

I googled those errors, looks like device incompatible, and the update may break my RAM. I am going to buy a new one and try.

I also try the WIndows 10 USB media to recover, but it gives me the same random error.

VERY BIG mistake from Microsoft!!! you can't control the auto update of your machine???? wow just follow iOS update model

"You block the update 'KB4056892'using 'wushowhide' until the AMD chip vendor can resolve with a patch." -> If the system is in an auto reset loop;  DISM may be a quick way to get a system back to usability, below are 2 methods:

On a AMD X2 L310 processored device, DISM stopped the looping.  Note the odd times in the 'results' below.  Even though MS had stopped the update, it was still Staged and on the system.... After KB4056892 (16299.192) was removed with DISM, & it is not being pushed by MS;  'Windows Update' is now running normally, after multiple checks and reboots..  

On an Auto restoring AMD X2 L310 processored device this stopped the looping:

Even though KB4056892 is showing hidden by the Hide/Show troubleshooter ... I went ahead & used DISM to remove the Staged Package from this 1709 x64 system from within Windows, to stop the looping.

from an elevated command prompt ran:

dism /get-packages /Online

pertinent results at the end:

Package Identity : Package_for_RollupFix~31bf3856ad364e35~amd64~~16299.125.1.6

State : Installed

Release Type : Security Update

Install Time : 1/12/2018 12:01 PM 

Package Identity : Package_for_RollupFix~31bf3856ad364e35~amd64~~16299.192.1.9

State : Staged

Release Type : Security Update

Install Time : 1/12/2018 3:12 AM

16299.192.1.9 locked the device; so I removed it:

Back in the elevated command prompt i ran (copy all the bolded text as one line, command may be wrapped when displayed on MC;  if your results from the previous DISM command are the same):

dism /Online /remove-package /packagename:Package_for_RollupFix~31bf3856ad364e35~amd64~~16299.192.1.9

pertinent results at the end:

Processing 1 of 1 - Removing package Package_for_RollupFix~31bf3856ad364e35~amd64~~16299.192.1.9

[==========================100.0%==========================]

The operation completed successfully.

Windows Update Completed successfully, it downloaded some Defender updates, and left no pending updates.  Even after rebooting device multiple times over many hours.

see also:

Opteron185 replied on January 9, 2018 1/9/2018 8:11:49 PM (on page 18 of this same question)

https://answers.microsoft.com/en-us/windows/forum/windows_10-update/after-installation-of-kb4056892-boot-failure-after/6c015632-2a45-4725-a882-f231f8c88f36?page=18#LastReply

"If you can boot into your recovery environment and open a command prompt, you can follow its instruction starting from step 3.

2)  USB boot your system into the recovery environment - pull up a Command Prompt

3)  At the command prompt - first determine what drive letter your boot volume is assigned.  On mine, it was E:.  It will likely be C: D: or E:.  You might find that do a c: - then doing dir - hitting enter or d: - dir - enter - will be easiest to figure out which drive it is.  You could also go into diskpart and look at the Volumes (diskpart (enter) - list volumes (enter) )

4)  Substitute the correct drive letter in each of these commands (where e:\ is your Windows volume)

dism /image:e:\ /get-packages

5)  After you run this command - it will show a list of packages.  Look for the most recently installed - it likely will say "Install Pending"

6)  Take that Package identity from those results and run the following command (where package name is the package you want to remove):

dism /image:e:\ /remove-package /packagename:Package_for_RollupFix~31bf385ad364e35~amd64~~15063.850.1.10 "

The package you need to remove (KB4056892), for 1709 x64  is -> Package_for_RollupFix~31bf3856ad364e35~amd64~~16299.192.1.9