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-17T20:41:34+00:00

    I installed KB4056892 (I didn't reboot the machine after install), then I installed KB4073290 over it, I rebooted twice (the second reboot probably wasn't needed, but Windows Update asked for it) and everything is OK. KB4073290 is shown as installed, KB4056892 isn't shown as installed and is not installed any more. So probably just installing KB4073290 is enough.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  2. Anonymous
    2018-01-17T20:27:18+00:00

    MELERIX

    I wonder if we should open another thread telling Microsoft that they may have forgotten about us 32 Bit folk, or just wait a day or two?

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  3. Anonymous
    2018-01-17T20:13:07+00:00

    yes, one of my affected machines is 32bits and sadly there is no KB4073290 for x86 available yet :/

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  4. Anonymous
    2018-01-17T20:10:57+00:00

    MELERIX

    Now this might be a good thing but not for me.

    KB4073290 is x64 based.

    https://www.catalog.update.microsoft.com/Search.aspx?q=KB4073290

    The system here is 32 Bit.  Heck if some of those apps would have run under W-10 64 bit, that system wouldn't even be here.  Well,  there are hardware considerations also.

    True, waiting a few days is probably the best thing to do. 

    If after a few days there is no 32 Bit fix I will probably open a new thread.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  5. Anonymous
    2018-01-17T20:09:15+00:00

    the only bad news is that KB4073290 is not available for x86 yet, so 32bits machines are still affected :(

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments