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-02-02T19:01:23+00:00

    You could start a new topic regarding no boot after installing KB4058258 and after KB4056892 as this should had allowed for KB4056892 to install normally. But as I said it did fail to boot at first reboot after KB4056892 even with KB4058258 for me on AMD Turion 64 X2.

    But I believe this issue is a result of installing KB4056892, which I assume is bundled with the 1709 update. As suggested earlier in this thread, installing KB4058258 was said to rectify the problem. Unfortunately for me though this is not the case. My system is running an AMD A10-7700K CPU. I'll continue to search for other remedies. But if anyone knows of an easy method to block the 1709 update outright, I'd be willing to try it.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2018-02-02T15:45:59+00:00

    Was this answer helpful?

    0 comments
  3. Anonymous
    2018-02-02T15:43:09+00:00

    KB4058258 shouldn't be causing boot process to fail, because it contains the previous fixes for boot process.

    Melerix,........but it does. It did it to me as well. I updated with 4058258 yesterday and WU told me the update was successful. Computer was working normally so I switched off overnight. Just switched on and have spent half an hour getting up and running: no Windows loading, just showed my background screen. When I pressed a key to get to Windows login, it kept looping back to the background screen. Eventually used the method I'd used before, killed all power input, reconnected and went through set up after restarting. All OK now except WU is telling me there's an update in process, so I'll have to do a restart.

    The support page for 4058258 doesn't show the x64 update 4073290 in its history, only the x32 version.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2018-02-02T14:00:14+00:00

    You could start a new topic regarding no boot after installing KB4058258 and after KB4056892 as this should had allowed for KB4056892 to install normally. But as I said it did fail to boot at first reboot after KB4056892 even with KB4058258 for me on AMD Turion 64 X2.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2018-02-02T13:32:13+00:00

    Much to my dismay, I seem to also have the same issue. Everything was working fine once I rolled back from 1709 to 1607. However, it obviously detected being out of date and eventually started the upgrade process again. At this point I guess I'm not quite sure which update(s) I should block such that when 1709 goes to reinstall, I don't encounter the same non-boot issue. Or, is it simply a matter of installing patch KB4058258 before the 1709 update self-initiates? Again, much appreciated to those who are sticking around and helping the rest where this issue continues to persist.

    UPDATE**:** So I went through the 1607 to 1709 update process, then installed (via Dism in CMD because system is back to black screen/locked booting) KB4058258, KB4073290, and KB4057144. And still yet the boot process gets stuck at the spinning dots and/or the black screen w/ cursor. I'm really at a loss because for my specific configuration, something contained within build 1709 is directly causing this. As soon as I revert back to 1607, I can boot normally and the desktop comes up fine. So is the solution really to prevent 1709 from ever installing? At least until the next build is released? And if so, how would I even go about "blocking" a major update like that short of disconnecting the network cable indefinitely?

    Was this answer helpful?

    0 comments