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

Anonymous
2018-01-04T22:13:27+00:00

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?

Windows for home | Windows 10 | Windows update

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

494 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2018-01-06T06:29:52+00:00

    I'm having the identical problem with the system locking on boot after the KB4056892 update on an Athlon X2 5600 (Brisbane) W10 64 bit Home, and an Athlon 64 X2 6000 (Windsor) W10 64 bit Pro machine.  I had to restore or reset the machines to get them to boot up again. I'm putting hidden updates on hold on those machines for now.

    Interestingly, I am not having the problem with an Athlon X2 7850 (Kuma) 64 bit Home, or Athlon II X3 (Rana) 64 bit Pro machines. Those processors have slightly newer architectures compared to the K8 cores above.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2018-01-06T02:10:27+00:00

    I have a ASRock 960GC-GS FX motherboard and i quickly checked the bios settings and everything is enabled. Virtualization Enabled, ACPI HPET TABLES enabled as well.

    In Windows, Task Manager shows Virtualization enabled.

    Systeminfo shows:

    Hyper-V Requirements:     

    VM Monitor Mode Extensions: Yes

    Virtualization Enabled In Firmware: Yes

    Second Level Address Translation: No

    Data Execution Prevention Available: Yes

    Was this answer helpful?

    0 comments
  3. Anonymous
    2018-01-06T00:52:58+00:00

    Try manually rolling back to some previous restore point. If there is none, you will probably have to reinstall.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2018-01-06T00:49:21+00:00

    For recovery I booted the machine two times, both boots ended by hardlockup, so I powered the machine off and started it on again. During the third boot it automatically rolled back the update, then I disable automatic updates by gpedit. On windows Pro it can be done by e.g.: https://www.windowscentral.com/how-stop-updates-installing-automatically-windows-10

    Ciao Jaroslav,

    more or less I did the same getting the automatic roll-back (in italian: ripristino automatico) screen, but after a while it failed with the message (in italian):

      Impossibile ripristinare il tuo PC

    which translating is

      impossible to restore your PC

    So when I boot or it freezes, as described in this discussion, or it tries to roll-back but fails...

    When it fails it proposes to Switch off the PC or the Advanced Option. Here there the option Problem Resolution which offers other options. Reset the PC or other Advanced Options between which DOS box, roll-back from a restore point and so on.

    Ciao, Angelo.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2018-01-05T18:21:42+00:00

    Thanks for info. This seems very helpful and promising. My machine has some junctions, so it could be related. I will check the logs thoroughly later today. I could understand if it fails and writes the error, but it crashes hardly very early during the post-install reboot, nothing was reported. I had to powerdown the machine because it didn't react to anything. When repeated for several times (IIRC two times) it detected that something is wrong, started auto-repair and rolled back the update. Then it booted OK. Then I could see the error in the windows update.

    Was this answer helpful?

    0 comments