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

"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

If you were had to follow my previous posts and suggestions on this bug issue, you wouldn't be where you are now.

Every client that uses Microsoft's Windows 10 OS can create a DVD disk or if your bios allows, a USB pendrive version. This MediaCreationTool thus allows the user to gain access via rolling back the 'KB4056892' by selecting from the menu all 'F' numbered options and choosing 'F1' - Debugging.

You block the update 'KB4056892'using 'wushowhide' until the AMD chip vendor can resolve with a patch.

This is what I have done but I dernt shut the computer down or im back to square one

All such issues should first be checked out at your computer manufacturer's website.

Dell, Lenovo, HP, or other.

All have decent (and free) support (including patches to help make your device compatible with new Windows Updates.)

Remember, also, that Third Party Antivirus, and Antimalware problems can interfere with updates,

And remember that all Registry Cleaners can potentially destroy your ability to update your devices and that NONE are supported by Microsoft.

Same issue here, 3 computers running intel chips all locked or bricked. Managed to get 1 working after 2 days of troubleshooting. Working on second one now. All posted bsod after update with inaccessible boot device.