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

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

Answer 2

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.

Answer 3

As said in another thread, I have the same issue on an old AMD Athlon 64 X2 5200+ and Asus M3N78 Mb. I made a clean installation 4 days ago: until the update, it is working like a charm. Thanks for sharing Jaroslav, hoping they will fix the fix soon.

Answer 4

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 5

Same issue here, but with an AMD Sempron 3200+ processor and 32-bit Win10 Pro.  I had to do a reset to fix....