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-09T18:51:49+00:00

    I wish I could disable updates but unfortunately I have the home version.  I am running an AMD x2 6400+.  I have to rollback everyday due to the issue.  It is very frustrating!

    Was this answer helpful?

    0 comments
  2. Anonymous
    2018-01-09T18:56:18+00:00

    AMD Opteron Dual Core 180 Denmark (S939, L2 2048Kb not loaded .Error 0x800f0845

    Was this answer helpful?

    0 comments
  3. Anonymous
    2018-01-09T19:11:49+00:00

    Microsoft has officially acknowledged the problem today:

    https://support.microsoft.com/en-us/help/4073707/windows-os-security-update-block-for-some-amd-based-devices

    The problem is - how do you fix a non-booting system?  Well, we had around 20+ systems yesterday in our environment that wouldn't boot because of this issue.  We ended up swapping harddrives into a new model system as a quick fix, but there is another way.  Since Microsoft has called back the update for AMD systems, here is what you can do to get your AMD system booting again:

    1)  Boot into a recovery environment (we had recovery environment disabled so students can't mess with things on our systems).  You can make a recovery drive by going to any Windows 10 system (one that still works, obviously :) ) - go on the Start Menu - type Create a Recovery Drive - follow the steps

    2)  USB boot your system into the recovery environment - pull up a Command Prompt

    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

    Here is a screenshot of it removing the package and for reference:

    I hope this helps someone out there.  We've fixed all of our systems another way already, but this might be handy to know for future.

    Just to add some more details.  After you get the system booting again, you might have to remove the update right away again.

    You can use the same DISM command with the /online switch to remove it if Windows tries to reinstall it right away.  Then, run the Show/Hide update tool to hide the January update so it doesn't reinstall.  Here is a link for that:

    https://support.microsoft.com/en-us/help/3073930/how-to-temporarily-prevent-a-driver-update-from-reinstalling-in-window

    Was this answer helpful?

    10+ people found this answer helpful.
    0 comments
  4. Anonymous
    2018-01-09T19:22:45+00:00

    Thanks

    Not a problem.  As expected with a problem of this nature, confusion appears to be the order of the day.

    I am trying to keep the ASUS utility stuff in the thread mentioned in the last reply so as not to clutter a thread addressing a more severe problem.

    Do give some thought to

    1. How can I get my ASUS utilities working again.
    2. What to do if I can't.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2018-01-09T20:37:47+00:00

    Mine is a Toshiba Satellite and it started after the stupid update as well. This isn't my first issue with Windows 10 and I am getting so sick of it. They need to fix this and soon, I have work on my laptop I need to get back to. I had to go back to using my old Windows 7 machine, never had an issue like this in 7.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments