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-06T12:40:40+00:00

    This is an excellent example that the current trend about removing possibility to control/configure your own machine e.g. removing the option to just disable the automatic updates is terribly wrong.

    Was this answer helpful?

    6 people found this answer helpful.
    0 comments
  2. Anonymous
    2018-01-06T13:45:23+00:00

    Thanks for you suggestions.

    My opinion at the moment is that I should try to Reset the PC saving personal data. This is the only thing I can do when it fails to boot and tries to roll-back. This fails too but offers the Advanced Options which allow the Reset. Maybe also this will fail, then I would have to try a full reinstallation.

    Anyway, I don't understand why I cannot delete the wrong files which caused this with new good file from the DOS box in Advanced option. MicroSoft should give a recipe to do that so one can at least boot and stop the updates with your and others suggestions..

    Ciao,

     Angelo.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2018-01-06T13:59:51+00:00

    Maybe MS will provide instructions how to recover from the recovery shell, who knows. But according to my previous experience with MS I am quite skeptical about it :) Or somebody else will manage how to fix it. Maybe you could just take a list of the files from the update (e.g. http://download.microsoft.com/download/D/A/0/DA052502-1178-41A0-83CF-7120155B2009/4056892.csv)and copy them from the working machine. So if you don't need the machine you could try waiting for some solution instead of reinstalling.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2018-01-06T14:07:17+00:00

    i have this exact problem happening on mostly the same platform cpu identical motheboard is an msi one made for acer pcs and i does that after it does a roll back to previous state

    Was this answer helpful?

    0 comments
  5. Anonymous
    2018-01-06T14:36:46+00:00

    I was hoping the Hide/Show troubleshooter WUHIDESHOW.DIAGCAB tool downloaded at: https://support.microsoft.com/en-us/help/3073930/how-to-temporarily-prevent-a-driver-update-from-reinstalling-in-window

        would help, but when I run it it unfortunately shows no updates to hide or show.

    So for now, I guess I will have to leave my Windows Update Service stopped & disabled and hope for a fix.

    START>>RUN>>SERVICES.MSC     Find Windows Update Service, right-click-choose PROPERTIES and STOP the Service and choose STARTUP TYPE:  DISABLED

    I also reported it for documentation & escalation to Microsoft Support Chat but I sadly didn't get a good vibe that was going to help or do anything.  The support agent diverted the issue back to me as needing an unspecified "firmware update" by my "hardware manufacturer", not that the update was the cause or would be fixed.

    Was this answer helpful?

    0 comments