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

Question

Hi,

I have older AMD Athlon 64 X2 6000+, Asus MB, after installation of KB4056892 the system doesn't boot, it only shows the Windows logo without animation and nothing more. After several failed boots it do roll-back then it shows error 0x800f0845. Unfortunately, it seems it's not easy to disable the automatic updates without gpedit tweaks, so it tries installing and rolling-back the update over and over. The sfc /scannow shows no problem, in-place upgrade also doesn't seem to help. I can try full reinstall, but I doubt it will change anything. It seems like the update is binary incompatible with my old CPU. I understand that making the machine unbootable is the best protection from remote exploitation, but I would rather have the OS working. Especially if my CPU is not vulnerable to the Meltdown attack and the MS mitigation attempts for Spectre is more than questionable. I could find only some German and Italian people reporting the same issue (well the CPU is quite pre-historic and the KB update is very fresh), but no info / acknowledgment from the MS so far. I have Czech localization. Could anybody provide more information?

Answer 1

Thanks for info, but it doesn't seem to be related. I tried disabling both Virtualization and HPET and all combinations like Virtualization only and HPET only, but still the same, no boot. I rolled back the update and disabled automatic updates through the gpedit because otherwise the machine is unusable.

Answer 2

There is no antivirus installed, except  MS Defender and the update sneaked-in automatically through the Windows update.

Answer 3

Microsoft has officially acknowledged the problem today:

https://support.microsoft.com/en-us/help/4073707/windows-os-security-update-block-for-some-amd-based-devices

The problem is - how do you fix a non-booting system?  Well, we had around 20+ systems yesterday in our environment that wouldn't boot because of this issue.  We ended up swapping harddrives into a new model system as a quick fix, but there is another way.  Since Microsoft has called back the update for AMD systems, here is what you can do to get your AMD system booting again:

1)  Boot into a recovery environment (we had recovery environment disabled so students can't mess with things on our systems).  You can make a recovery drive by going to any Windows 10 system (one that still works, obviously :) ) - go on the Start Menu - type Create a Recovery Drive - follow the steps

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

Here is a screenshot of it removing the package and for reference:

I hope this helps someone out there.  We've fixed all of our systems another way already, but this might be handy to know for future.

Just to add some more details.  After you get the system booting again, you might have to remove the update right away again.

You can use the same DISM command with the /online switch to remove it if Windows tries to reinstall it right away.  Then, run the Show/Hide update tool to hide the January update so it doesn't reinstall.  Here is a link for that:

https://support.microsoft.com/en-us/help/3073930/how-to-temporarily-prevent-a-driver-update-from-reinstalling-in-window

Answer 4

I am helping hundreds of people with this is issue. The fix is actually rather simpler. Here is the steps to fix it:

Visit https://www.ubuntu.com/desktop and download 16.04, install by removing windows completly.

There is hundreds of software for replacement, and if the one you need is windows only, you can run windows application on ubuntu with wineHQ or a paid option.

Enjoy!

Answer 5

seems is the same bug that is affecting Insiders in Build 17063.

check if this help you… enter in your BIOS options and check if there are options for HPET or Virtualization, and disable one of them or both if needed, then Windows should be able to boot again without stuck in Windows logo during startup.