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

AMD FX 8150, ASUS M5A97, Win 10 Pro (64Bit).  AI Suit II has stopped working.

Amongst other functions AI Suit can customize fan speeds.

Fortunately there are Fan Advance tables in BIOS .  Fan/Tempura relationship set to "Turbo"

UPDATE: originally, KB4056892 had compatibility issues with my AMD board, mainly Asus AI Suite II crashes on start.  I uninstalled the Windows update and paused updates and everything was good again.

With the release of KB4073290, which is suppose to fix AMD system bootup issues, I gave it a go again and it seems to have fixed issues with the AI Suite II program.  No problems thus far.  You can download just KB4073290 from the Windows Update Catalog and install it without having to install KB4056892 (i.e. it's a cumulative update).

AMD FX-9370, Asus Sabertooth 990FX Gen3 R2.0, Windows 10 64bit.

Alex

If you don't have a AMD CPU then installing 16299.192 would be a good thing basically. so in other words, if you got a Intel CPU chances are the update will work fine. It worked fine on my i3-2120 computer but I had a problem with the update on my 10 year old laptop which has a AMD CPU.

you can always create a restore point manually just in case or if you got another computer with a big enough hard drive to store a image you can use CloneZilla to make a image of your current 16299.125 computer as a extra precaution so if anything acts up, and say it fails to restore your computer to 16299.125 using Windows 10's built in repair mode(when it failed for me it takes 2-3 reboots before it enters automatic repair mode), you can use CloneZilla to restore the computer to exactly the state it was prior to running the update since it creates a exact duplicate of your hard drive when it images it. CloneZilla works great for imaging a computers hard drive and what's even better is it can store those images on a different computer through Samba connection (it supports v2 and higher so you ain't got to worry about the connection failing like it would if you only had Samba v1 which Windows 10 does not like as Samba v1 disabled by default). it asks you which Samba version you want to use if you use the samba portion of CloneZilla just select anything v2 or higher and it should work.

When you run Windows as a guest under your GNU/Linux host, and the Windows guest gets the update in question, does Windows still boot?

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.

It's great that the problem was officially acknowledged and is worked on. Thanks everybody involved. BTW: I wonder what AMD will say about it :) i.e. whether they docs were really faulty. Considering the fact that the Linux kernel with the Meltdown patches seems to boot OK, it may be interesting to watch this cause :)