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: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2018-01-07T08:29:45+00:00

    Microsoft "Show or hide updates" troubleshooter package does indeed work to hide KB4056892.  However, the timing is tricky:  You have to run it after Windows 10 has repaired the KB4056892 update -- after the update has been rolled back but before it's been downloaded and installed again (waiting to restart).  Run wushowhide.diagcab, click "Advanced," uncheck "Apply repairs automatically," and click "Next."  After a while, you'll get two choices -- pick "Hide Updates."  You should then see KB4056892 to select to hide.  If KB4056892 isn't shown, then I guess the timing probably wasn't right for executing wushowhide.diagcab.  http://download.microsoft.com/download/f/2/2/f22d5fdb-59cd-4275-8c95-1be17bf70b21/wushowhide.diagcab

    (I tried to let Windows Update automatically install several times and then installed the standalone update, each time ending with just the Windows 10 logo with no animation and no hard disk activitity right after rebooting.  A couple of reset buttons should put you into repair mode.  My problem is on a computer with an AMD Athlon 64 X2 4200+, Asus M3N78 Pro Motherboard.  Normally, works great.  KB4056892 installed okay on all my other computers, including three other AMD processors.)

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments
  2. Anonymous
    2018-01-07T10:11:33+00:00

    Same issue with AMD Athlon 64 FX-62. Caused by Windows Update KB4056892. After update rollback I was able to resolve issue (for now) using Download the "Show or hide updates" troubleshooter package now.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2018-01-07T10:43:26+00:00

    PS.

    Jaroslav, The X2 6000+ may be a relic however it still makes a wonderful signal generator, DVD/CD Burner and general all around "grunt" work machine.

    I just wanted to say it's old, but it's still working very good for me, so I am not OK with the current state, in fact I am very angry about it and especially that the MS haven't acknowledged the problem yet and ignores it.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2018-01-07T11:18:29+00:00

    I have this issue too. AMD Athlon 64 X2 4400+.

    After spending hours trying to fix this boot problem (didn't know it was caused by this KB4056892 update...) I decided to install Windows from scratch.

    I've got a little "angry" when it got stuck at boot screen again after finish installing all updates.

    But after rebooting 2 times, Windows was able to successfully rollback the update.

    I then find out the problem was caused by the lastest cumulative update.

    So I uninstalled it and run the wushowhide.diagcab to hide it.

    And I paused Windows Update for 35 days just to give MS a chance to fix the issue in the meanwhile.

    But I'm not keeping my hopes too high...

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments
  5. Anonymous
    2018-01-07T13:43:33+00:00

    Same problem on a friend’s older PC with an Athlon X2 Brisbane CPU on a Gigabyte Motherboard . Ended up having to reinstall windows and then pause updates.

    Was this answer helpful?

    0 comments