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-08T21:33:28+00:00

    My spellcheker is broken but not my OS!

    Ahead of you by miles long strech!

    I am living in 3018 while you in back in 1998!

    Bye Felicia!

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  2. Anonymous
    2018-01-08T21:12:37+00:00

    I do not work for Ubuntu. I am telling you by experince how to get rid of your problem. Since I stop using Windows my life is much better and more managable. 

    So far Linux has demotrated to be more stable and on top of both issues better than Microsoft. 

    Is okay if you are fan, and see options a threat, but so far all the patches I have received has not render my pc obsolote. :)

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  3. Anonymous
    2018-01-08T21:12:04+00:00

    Don't hold your breath on Microsoft fixing this. They only have to support Windows 10 on systems that the manufacturer's support it on, and no manufacturer is going to have 10 support for an ancient 939/AM2 machine.

    This is wrong assumption. Nobody said that it is not compatible. In fact the upgrade assistant showed that its compatible. If I knew it's not compatible and that the OS would kill my machines few months later, I wouldn't' buy the licenses. It's simple.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  4. Anonymous
    2018-01-08T21:08:24+00:00

    I am helping hundreds of people with this is issue. The fix is actually rather simpler. Here is the steps to fix it:

    Visit https://www.ubuntu.com/desktop and download 16.04, install by removing windows completly.

    There is hundreds of software for replacement, and if the one you need is windows only, you can run windows application on ubuntu with wineHQ or a paid option.

    Enjoy!

    So EJ, you work for Ubantu or what?

    Yes, that is exactly what we need a OS that may or may not address the Meltdown and Spectre issue. I really don't want to reload Windows 10 much less a different OS in place of it. Thank you so much for going off the rail with this "helpful" reply.

    Was this answer helpful?

    1 person found 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