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 No comments

494 answers

Sort by: Newest
  1. Anonymous
    2018-01-08T08:34:30+00:00

    Seems the beat current 'workaround' is to pause updates for 35 days - can find the option in the Windows Update Settings -> Advanced Options.

    This provides a brief release from the hell that is Windows 10 and all of its 'intelligence' and gives the 'experts' a Microsoft time to do a proper job on the patches

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments No comments
  2. Anonymous
    2018-01-08T08:28:54+00:00

    I have the same problem with an old AMD chip

    OS Name Microsoft Windows 10 Pro

    Version 10.0.16299 Build 16299

    Other OS Description Not Available

    OS Manufacturer Microsoft Corporation

    System Name STEVESDESKTOP

    System Manufacturer Dell Inc

    System Type X86-based PC

    System SKU Unsupported

    Processor AMD Athlon(tm) 64 X2 Dual Core Processor 5600+, 2900 Mhz, 2 Core(s), 2 Logical Processor(s)

    BIOS Version/Date Dell Inc 1.1.11, 8/2/2007

    I get a failed intall  with  repeating  uninstalls,  reboots, and reinstalls

    for KB4056892 (4) with error 0x800f0845

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments
  3. Anonymous
    2018-01-08T04:58:58+00:00

    Try advanced repair. Check fir a system restore point.  If you are lucky enough to have one or u knew to enable then u can restore. After that it is repair keeping files but lose apps.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  4. Anonymous
    2018-01-08T01:58:00+00:00

    I'm having the same issue on my AMD Athlon 4850e dual processor machine. I also did a system restore and then paused win 10 updates. My machine hangs very early in the boot process with the teal blue windows logo frozen on the screen. I created another question for my issue, but it definitely seems related, if not identical.

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2018-01-08T01:44:28+00:00

    Identical issue (Windows logo only on boot) experienced on an AMD Athlon 64 X2 5600+, just after installation of KB4056892.  Fortunately a system restore point was created prior to installation, which I could roll back to.

    Have used the "Show or hide updates" troubleshooter package (available via https://support.microsoft.com/en-gb/help/3183922/how-to-temporarily-prevent-a-windows-update-from-reinstalling-in-windo (URL is complete, even though it appears truncated!) to temporarily disable further attempts at installing this update, until MS resolve the issue...

    Was this answer helpful?

    0 comments No comments