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. Anonymous
    2018-01-09T16:22:43+00:00

    It's great that the problem was officially acknowledged and is worked on. Thanks everybody involved. BTW: I wonder what AMD will say about it :) i.e. whether they docs were really faulty. Considering the fact that the Linux kernel with the Meltdown patches seems to boot OK, it may be interesting to watch this cause :)

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments
  2. Anonymous
    2018-01-09T00:35:36+00:00

    My experience with "2018-01 Cumulative Update for Windows 10 Version 1709 for x86-based Systems (KB4056892)" on desktop PC, powered by Athlon 64 X2 4200+ CPU, Windows Version 1709 (OS Build 10.0.16299.125):

    Update is downloaded and installed, but after the restart PC freeze/stuck at booting stage with Windows 10 logo on the screen, with no hard drive activity on LED indicator. Need two forced reset button hits, to invoke the Windows Repair to fix this.

    I am glad that after the repair, the PC was successfully booted(Windows repair successfully fixing this thru rollback faulty KB4056892).

    Download, and install manually KB4056892 from Microsoft Update Catalog, but the same stuck/freeze Windows boot screen issue. So we wait for fix.

    But since Windows 10, there is a scheduled restart outside of active hours, so the faulty update will be auto installed - rollbacked again and again, creating a loop situation. Giving more control of the users to control/disable/enable the Windows Update process is not a bad idea.

    These freezing/stuck boot/blue screen issues from Windows Update have been increasing in the recent months. Microsoft where is your testing team? Is this team existed? What they actually do? There is a strong effort to fix/patch Meltdown/Spectre vulnerability, but please, when another Meltdwon/Spectre like vulnerability comes in the future, don't fix one issue and broke many other things, as has happened and continues to happen to date.

    I'm sure the inconvenience could have been saved if you had a reliable test team, that has just a PC/Notebook with one processor from each generation Intel/AMD CPU, to install the KB4056892 first on them, though you are Microsoft and you can afford it in the name of the company.

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments
  3. Anonymous
    2018-01-08T21:18:23+00:00

    This is also off-topic. I am long time Linux developer, but it doesn't prevent me from buying Windows licenses. And btw there are much better options than Ubuntu ;)

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments
  4. Anonymous
    2018-01-08T18:23:39+00:00

    Feedback Hub is not working. ERROR! So, no Feedback can be left.

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments
  5. Anonymous
    2018-01-08T08:34:30+00:00

    Seems the beat current 'workaround' is to pause updates for 35 days - can find the option in the Windows Update Settings -> Advanced Options.

    This provides a brief release from the hell that is Windows 10 and all of its 'intelligence' and gives the 'experts' a Microsoft time to do a proper job on the patches

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments