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-09T04:40:18+00:00

    Are Microsoft accepting any feedback for Windows 7 Pro systems? I have an Athlon 64 X2 6000+ CPU in an HP workstation, got BSOD after patching with KB4056894 (auto-restart disabled);  booted into System Restore, reverted to state immediately prior to patch installation, then went into Windows Updates settings and hid the update. System Event log shows update failure error 0x800f0816. I'm ecstatic I didn't install WX on this (reliable) dinosaur.

    This computer wasn't slated for replacement until 2020- in fact, I was about to upgrade the SSD to a larger faster one, but now I'm wondering if this patch wasn't a gambit to drive up flagging sales in the desktop world, and I'll be swimming upstream.

    I'd be happy to post the technical details (sans commentary) wherever it's most useful to Microsoft, just point me.

    Thanks for your time

    Kirk

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  2. Anonymous
    2018-01-09T04:53:42+00:00

    I have a A10 and a A8 processor the system loads but you cant do anything I uninstalled this update now everything works again... hid update for 30 days ..why would you put out a update that wasnt needed for AMD ! Amd has stated these attacks cannot be done on there CPUS

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  3. Anonymous
    2018-01-09T05:12:56+00:00

    wildrex

    Interesting as this is a much newer CPU than the majority "Bricked" devices.

    If I might ask, what Motherboard (s) are you using?

    Does the lock occur on the Windows Logo screen with no animation.

    If you get by the windows Logo screen, how far do you get and what next action are you not able to take?

    How does it recover?

    This "fix" may directly impact how the processor and OS interact, however even if that is all fine, it may affect some applications such as ASUS AI Suite.

    Thanks

    Was this answer helpful?

    0 comments
  4. Anonymous
    2018-01-09T05:52:06+00:00

    Official Microsoft response about the issue: https://support.microsoft.com/help/4073707/

    Was this answer helpful?

    8 people found this answer helpful.
    0 comments
  5. Anonymous
    2018-01-09T10:03:15+00:00

    So blocking the update with "wushowhide.diagcab" is the best solution so far, while we expect a fix by MS/AMD.

    Btw, thanks guys & girls for the advice. Saving a lot of time, avoiding rollback/reinstall everything. Very much appreciated.

    Alex, AMD Athlon 64 X2 Dual Core TK-55

    PS : Don't know if it is relevant but I had pretty much this kind of issue while trying to install win10 x64 (not booting, black screen, no dots) few months ago from the up-to-date iso version of MS, I fixed by using an older version of the iso.

    Was this answer helpful?

    0 comments