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-10T02:12:06+00:00

    My intell machine does not show a package installe on 1/6/2018 which is the date of the system restore point for the critical update.

    My machine give no boot device after booting with animated logo for a several seconds the goes blue screen with error.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2018-01-10T01:36:53+00:00

    My intel cpu machine wont boot after the update.

    But I get an animated logo for a bit then no boot device available.

    Cant use USB to "upgrade" the installed version of windows because you must beable to boot into that version of windows for the upgrade to run 

    Safe mode does not work.

    Can get to command prompt, and other repair options.

    when restoring to restore point created by critical update (which I think fails because restore point does not go away) still cant boot  {{ dont have patience to watch the system restore process}}

    Any clues as to what to try with out a fresh new install ??

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments
  3. Anonymous
    2018-01-09T23:04:07+00:00

    After 20 years of computing Microsoft have managed to do what no hacker or virus have done to my computer - shut it down with a patch that was supposed to aid my computing experience. Is this like the Apple way of getting us older users to purchase a new machine (Apple slowing usage and not allowing updates to older machines)? My laptop was working perfectly until Tuesday 8th Jan 2018 but now it hangs at logo screen. Are Microsoft going to reply to this problem? Are they working on a fix? What are they going to do to compensate me for damaging my previously perfectly working laptop (an Acer Aspire 7520 with Athlon AMD 64 x 2 processor)? This is a massive problem and needs answers not silence.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  4. Anonymous
    2018-01-09T21:59:36+00:00

    Thanks, good info.

    Was this answer helpful?

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