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-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
  2. Anonymous
    2018-01-12T12:58:54+00:00

    Different suggestions work for different machines.

    I should have quoted the interesting part.

    The poster offers a way to uninstall the offending update in a system already compromised.

    If you can boot into your recovery environment and open a command prompt, you can follow its instruction starting from 3).

    3)  At the command prompt - first determine what drive letter your boot volume is assigned.  On mine, it was E:.  It will likely be C: D: or E:.  You might find that do a c: - then doing dir - hitting enter or d: - dir - enter - will be easiest to figure out which drive it is.  You could also go into diskpart and look at the Volumes (diskpart (enter) - list volumes (enter) )

    4)  Substitute the correct drive letter in each of these commands (where e:\ is your Windows volume)

    dism /image:e:\ /get-packages

    5)  After you run this command - it will show a list of packages.  Look for the most recently installed - it likely will say "Install Pending"

    6)  Take that Package identity from those results and run the following command (where package name is the package you want to remove):

    dism /image:e:\ /remove-package /packagename:Package_for_RollupFix~31bf385ad364e35~amd64~~15063.850.1.10

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  3. Monkey57 3,535 Reputation points
    2018-01-12T13:03:17+00:00

    Jssssssss's reply to my post of your question in Mod:

    See Answer in and read through this thread: How Do I Create Direct URL Links to Replies in Multi-page Threads?

    I'm using FF and made bookmarks for those scripts.  See:How Do I Create Direct URL Links to Replies in Multi-page Threads? (page=2) (JuliaIbiza March 26, 2017)

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  4. 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
  5. Monkey57 3,535 Reputation points
    2018-01-12T13:31:49+00:00

    Different suggestions work for different machines.

    I should have quoted the interesting part.

    The poster offers a way to uninstall the offending update in a system already compromised.

    If you can boot into your recovery environment and open a command prompt, you can follow its instruction starting from 3).

    3)  At the command prompt - first determine what drive letter your boot volume is assigned.  On mine, it was E:.  It will likely be C: D: or E:.  You might find that do a c: - then doing dir - hitting enter or d: - dir - enter - will be easiest to figure out which drive it is.  You could also go into diskpart and look at the Volumes (diskpart (enter) - list volumes (enter) )

    4)  Substitute the correct drive letter in each of these commands (where e:\ is your Windows volume)

    dism /image:e:\ /get-packages

    5)  After you run this command - it will show a list of packages.  Look for the most recently installed - it likely will say "Install Pending"

    6)  Take that Package identity from those results and run the following command (where package name is the package you want to remove):

    dism /image:e:\ /remove-package /packagename:Package_for_RollupFix~31bf385ad364e35~amd64~~15063.850.1.10

    Thank you for reposting Opteron185's (pg18) suggestion, I will try it on the systems that don't self restore, if it works, will then see if the bad update can be started again, so it can be hidden then uninstalled (although MS says they have stopped the update, as of last nite;  some AMD machines where still re-installing it).

    Was this answer helpful?

    0 comments