After installation of KB4056892 boot failure, after roll-back error 0x800f0845

I'm running am older version of Windows 10 Pro (for specific reasons) that doesn't know what to with a feedback-hub link. So I go to the store as suggested to download and install the app and, ... wait..., I will most definitely NOT install this.

Woke up this morning to this particular laptop setting on desk with Black Screen and Microsoft logo and no animation. Nothing going on.

So same/similar issue on older HP60 with AMD Turion X2 RM70 32 bit. My error message was 0x80070643.

Not Windows 10 Pro but Windows 10 Home build 16299 - so no way to start automatic download and install.

After 3 rollbacks, found this tread so I don't feel totally stupid for having wasted most of my Sunday trying to "fix" this now known to be un-fixable problem. Had McAfee (updated) on it so with 2nd roll back had wireless off before complete boot up and took McAfee off before restarting it again. Then allowed update KB4056892 to download. Every time the PC rebooted after download and install, black screen with Windows logo and no animation was the only response I got from this particular machine.

One desktop with AMD A10-6700 no problem. 3 laptops with Intel and McAfee - no problem. One more laptop with Intel - so hopefully that one won't have issues. HP60 dead to the world until later?????

Hopefully Microsoft will get this (maybe older) AMD issue fixed quickly.

Follow up on above.

So after hearing the "good news" late last night that MS was going to stop trying to download this update on "affected AMD" computers, I thought - ok, a temporary patch will do as my wife needs her computer back. Was way too happy - way too quick! First thing this morning - Restored (for 4th time now) and after restart all was good EXCEPT I found McAfee disabled. Turn McAfee Scan back on and Windows disabled it again. Repeat. Repeat. Repeat. Removed McAfee thinking I would re-install it and Windows Update started downloading KB4056892 and installing it. (Yes- I have tried WUSHOWHIDE.DIAGCAB - multiple times/different times and it never recognized the update as being a problem nor gave the option to stop it).

Now on my 5th "restore" of this PC. Will do as I have before - Turn WiFi off - effectively locking this PC away from the crazy world of MS Update and shut the machine down until MS FINALLY gets this MESS fixed on AMD machines.

My computer, a Plex media server with 21TB of data, was also hit with this flaw.  My motherboard, a Gigabyte 770TA UD3, has two SATA controllers on board. One a SATA II for SATA drives 4, 5 and 6, and a SATA III (Marvell 91XX) for drives 1 & 2.  The Marvell one required a system driver to load prior to windows boot for the SATA boot drive (C:) to work.  After many system restores to get an operable computer, I discovered that the Marvell controller was not in the system folder anymore but marked as an unknown device with no driver in device manager.  After a long search, I found there is no driver for this anymore, particularly for Windows 10.  Probably because the motherboard is so old.  A Windows 10 driver is available, from ASUS but only in China/S.E. Asia.  LInk to it on windows forum:  Link to post on forum for driver

(hxxps://windowsforum.com/resources/marvell-91xx-sata-controller-6gb-driver-for-windows-10.40/)

Installed the driver , device moved back to system device and computer boots normally after update.  Maybe this old device (Marvell controller) while no longer supported by Microsoft/Vendor in the "new devices only" west was considered by Windows to be unsupportable during the update and removed by Windows (arbitrarily & unilaterally, they do it all the time, don't deny it MS) leaving thousands if not millions of older computers unable to boot because their boot drives were render inoperative by the update roll up from MS.  This is why, if you fight through to the option to system restore & go back to an earlier time, your computer works and then after the update it doesn't.  MS is removing a critical system/device driver it doesn't know what to do with and for which it has no Windows 10 driver, killing many older (especially AMD) computers that relied on it.  ASUS, based in S.E. Asia, has hundreds of older boards in it's inventory and millions of customers in China running older hardware, they custom made a window 10 driver for these older system rather than face the wrath of millions of angry customers, MS apparent doesn't care about these older less advanced users.  They had this unsupported device arbitrarily removed, crippling their computers.  Load the win 10 driver from ASUS as instructed in the post and your machine has a Win 10 driver for the Marvell 91XX controller and the update leaves it alone and your computer reboots normally after the update.  There are a lot of people in the world not running cutting edge Windows 10 compliant systems.  You can't forget about them when you update your OS.  Hopes my hours of looking can save some one else the trouble. Hope it helps people with this problem, it certainly did for me.

No, it is not needed anymore!

Windows operating system security update block for some AMD based devices

"To prevent AMD customers from getting into an unbootable state, Microsoft will temporarily pause sending the following Windows operating system updates to devices with impacted AMD processors at this time:

January 3, 2018—KB4056897 (Security-only update)

January 9, 2018—KB4056894 (Monthly Rollup)

January 3, 2018—KB4056888 (OS Build 10586.1356)

January 3, 2018—KB4056892 (OS Build 16299.192)

January 3, 2018—KB4056891 (OS Build 15063.850)

January 3, 2018—KB4056890 (OS Build 14393.2007)

January 3, 2018—KB4056898 (Security-only update)

January 3, 2018—KB4056893 (OS Build 10240.17735)

January 9, 2018—KB4056895 (Monthly Rollup)"

I have read that, unfortunately, for those who are not in "this state" update was still occurring this morning. It was obviously my case (build 16299.125)

So I recall what I have done to "block it manually" ;)

Alex

So blocking the update with "wushowhide.diagcab" is the best solution so far, while we expect a fix by MS/AMD.

No, it is not needed anymore!

Windows operating system security update block for some AMD based devices

"To prevent AMD customers from getting into an unbootable state, Microsoft will temporarily pause sending the following Windows operating system updates to devices with impacted AMD processors at this time:

January 3, 2018—KB4056897 (Security-only update)

January 9, 2018—KB4056894 (Monthly Rollup)

January 3, 2018—KB4056888 (OS Build 10586.1356)

January 3, 2018—KB4056892 (OS Build 16299.192)

January 3, 2018—KB4056891 (OS Build 15063.850)

January 3, 2018—KB4056890 (OS Build 14393.2007)

January 3, 2018—KB4056898 (Security-only update)

January 3, 2018—KB4056893 (OS Build 10240.17735)

January 9, 2018—KB4056895 (Monthly Rollup)"