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-08T14:11:09+00:00

    Hi CxRes,

    this is what is needed to make it work:

    • If possible in your Windows 10 version, set your connection as "metererd", this will stop automatic download of updates
    • before (but it's ok also while) the KB4056892 is downloading, use the Hide/Show troubleshooter to hide the update
    • be sure it is NOT "waiting for restart" (*) in Windows Update and restart the pc
    • check Windows Update to verify that the offending update is now ignored
    • reset your connection to not metered

    done.

    (*)

    I have managed to avoid the installation of the offending update also when it is already in the "waiting for restart" state!

    The offending update is already listed in the uninstallable updates so you can uninstall it and then restart your pc.

    How to Uninstall a Windows Update in Windows 10

    Was this answer helpful?

    0 comments
  2. Anonymous
    2018-01-08T15:13:23+00:00

    My new computer's CPU is the AMD Ryzen Threadripper 1950. For the record, I am having the same problem as everyone else.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2018-01-08T15:52:49+00:00

    I had similar experience.  Repeatedly saying, "Hi.  We have some updates..." on Acer Laptop purchased about 2008.  I let it shut down when battery ran down after about 1 1/2 hours.  Anybody have a fix?

    Was this answer helpful?

    0 comments
  4. Anonymous
    2018-01-08T15:53:02+00:00

    Wow, new CPU and you also are locked out.

    Does  your computer lock up and get stuck at the blue windows logo too?

    Keep us posted if you get an update that works

    Thanks

    Was this answer helpful?

    0 comments
  5. Anonymous
    2018-01-08T16:22:44+00:00

    KB4056892 failure on 18 month old Surface

    I had to reset my Win 10 Surface Pro 4 today following a network driver problem.  I then dutifully checked for updates and had a very lengthy encounter with KB4056892.  On restart my machine continuously hung at blue screen and "preparing to install update".  It required a hard restart and auto update began trying to install the update again.  Next restart presented the same problem and round the loop we go again!

    I tried downloading the update direct from the MS site.  Same problem occurs.

    This fairly lengthy conversation seems to point the issue at old hardware.  My Surface Pro is nearly 18 months old so very nearly obsolete!  However, I found a mechanism for a fix within this conversation. 

    1.Turn off auto updates

    1. Run wushowhide.diagcab which can be found at https://support.microsoft.com/en-us/help/3073930/how-to-temporarily-prevent-a-driver-update-from-reinstalling-in-windowand turn off KB4056892
    2. Restart - you system will hang again because it has already started to try and install KB4056892 - hard restart to interrupt blue screen
    3. Login then restart again - should restart happily?
    4. Turn on auto updates but wushowhide is now keeping KB4056892 at bay.

    I think Microsoft have a major issue here?  I look forward to an update that correct this issue so that I do not have to live with the auto updates telling me that I have got an update to install!!

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments