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: Newest
Most helpful Newest Oldest
  1. Anonymous
    2018-01-09T17:46:04+00:00

    Woke up this morning to this particular laptop setting on desk with Black Screen and Microsoft logo and no animation. Nothing going on.

    So same/similar issue on older HP60 with AMD Turion X2 RM70 32 bit. My error message was 0x80070643.

    Not Windows 10 Pro but Windows 10 Home build 16299 - so no way to start automatic download and install.

    After 3 rollbacks, found this tread so I don't feel totally stupid for having wasted most of my Sunday trying to "fix" this now known to be un-fixable problem. Had McAfee (updated) on it so with 2nd roll back had wireless off before complete boot up and took McAfee off before restarting it again. Then allowed update KB4056892 to download. Every time the PC rebooted after download and install, black screen with Windows logo and no animation was the only response I got from this particular machine.

    One desktop with AMD A10-6700 no problem. 3 laptops with Intel and McAfee - no problem. One more laptop with Intel - so hopefully that one won't have issues. HP60 dead to the world until later?????

    Hopefully Microsoft will get this (maybe older) AMD issue fixed quickly.

    Follow up on above.

    So after hearing the "good news" late last night that MS was going to stop trying to download this update on "affected AMD" computers, I thought - ok, a temporary patch will do as my wife needs her computer back. Was way too happy - way too quick! First thing this morning - Restored (for 4th time now) and after restart all was good EXCEPT I found McAfee disabled. Turn McAfee Scan back on and Windows disabled it again. Repeat. Repeat. Repeat. Removed McAfee thinking I would re-install it and Windows Update started downloading KB4056892 and installing it. (Yes- I have tried WUSHOWHIDE.DIAGCAB - multiple times/different times and it never recognized the update as being a problem nor gave the option to stop it).

    Now on my 5th "restore" of this PC. Will do as I have before - Turn WiFi off - effectively locking this PC away from the crazy world of MS Update and shut the machine down until MS FINALLY gets this MESS fixed on AMD machines.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  2. Anonymous
    2018-01-09T17:41:04+00:00

    I too am having this issue and I have been checking for any updates around the cumulative variety since it first started for me last month with the previous cumulative update 2017-12 1709 windows 10 x64, etc. where they first released the show and hide by-pass.  

    Have been very diligent checking daily for any updates similar to that one which caused me to reset my computer after reading the problems the previous update had.  I also noted the additional problem on this new update, (this forum included).

    After i went to bed last night this update was downloaded and attempted to be installed. When I woke this morning, my comp which is an HP AMD A4-5000 APU was on the welcome screen with my login showing indicating I had gotten some updates. After doing so it notified me of the failure.

    What bothers me is that I ran this show and hide feature and have been doing so daily and it did not even register that this was pending.

    if you offer people the chance to upgrade their systems from as far back as windows 7 with windows 10, then maybe you should check that far back on whether it is compatible with those systems that were available then before you do so.

    My system is a bit newer since I had it upgraded from windows 8.1 home. But I wonder at the constant trouble this is causing and if it happens again whether i can keep resetting/rolling back my computer without causing more harm down the road.

    Was this answer helpful?

    0 comments
  3. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

    Comments have been turned off. Learn more

  4. Anonymous
    2018-01-09T17:16:18+00:00

    Have the same AMD problem. Talked to a supportperson at Microsoft earlier today. He said there will be a AMD fix for kb4056892, today or latest tomorrow. Lets see if that happens... Hope so.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments
  5. Anonymous
    2018-01-09T16:22:43+00:00

    It's great that the problem was officially acknowledged and is worked on. Thanks everybody involved. BTW: I wonder what AMD will say about it :) i.e. whether they docs were really faulty. Considering the fact that the Linux kernel with the Meltdown patches seems to boot OK, it may be interesting to watch this cause :)

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments