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. Monkey57 3,535 Reputation points
    2018-01-12T13:09:38+00:00

    Thanks Monkey57. I did not let it finish so may try your suggestion. I did disable Windows Update in services but that has resulted in Windows no longer being activated so I need to resolve that first.

    please see:

    https://answers.microsoft.com/en-us/protect/forum/protect_other-protect_scanning-windows_10/sppextcomobjhookdll-hacktool-autokms/15ee8dad-fa65-41cd-b85b-b730b1985268

    regarding activation issue.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2018-01-12T12:58:38+00:00

    Thanks Monkey57. I did not let it finish so may try your suggestion. I did disable Windows Update in services but that has resulted in Windows no longer being activated so I need to resolve that first.

    Thanks again.

    Was this answer helpful?

    0 comments
  3. Monkey57 3,535 Reputation points
    2018-01-12T12:30:22+00:00

    Did you tried this suggestion?

    Different suggestions work for different machines.

    If a systems is able to self restore:

    If you are able to - use the Hide/Show troubleshooter to hide the Update, make sure you go into 'Control Panel-Programs&Features-view installed updates' and uninstall the update (as KB4056892 is usually awaiting a restart, if the Hide/Show troubleshooter finds it), before you reboot the system.

    "Is there a way to link a specific post in this forum?"->

    The way I do it is to click the link "Post a Reply" that it goes too from an email, then copy and paste the browser link, not the 'copy link' when right clicking in the email.

    Jssssssss is an expert at posting links, I will ask her, as my method only works in Subscribed threads from the point of subscription.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2018-01-12T11:40:15+00:00

    While I have plenty of workstations to test this ((JoeReedy's post ->"But appears to not be a problem."), I am kinda busy recovering lost systems.  I saw 2 systems relocked yesterday, before updates could be stopped..

    Did you tried this suggestion?

    Opteron185 replied on January 9, 2018 1/9/2018 8:11:49 PM (on page 18 of this same question)

    https://answers.microsoft.com/en-us/windows/forum/windows_10-update/after-installation-of-kb4056892-boot-failure-after/6c015632-2a45-4725-a882-f231f8c88f36?page=18#LastReply

    PS:

    Is there a way to link a specific post in this forum?

    Was this answer helpful?

    0 comments
  5. Anonymous
    2018-01-12T09:06:11+00:00

    I agree that AMD has terrible customer support, i.e. very similar to what MS has :) But as I wrote earlier Linux kernel patched according to similar instructions seems to boot OK on the affected machine. AFAIK at the moment there isn't publicly available microcode update for K8 CPUs, so maybe (just speculation) the Windows update brought updated microcode under NDA which was faulty? In such and similar cases AMD could be responsible for the problem, but primary responsibility is still on the MS to test the update before releasing.

    Was this answer helpful?

    0 comments