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: Most helpful
  1. Anonymous
    2018-01-27T03:27:10+00:00

    Brian

    Oh, darn, I don't know.  MELERIX's response (see above) makes sense.  Then again waiting until Tuesday would be prudent.  The problem is that I feel like that cat who was curious about what was in that walled off hole people kept  getting buckets from.  We all know what curiosity did to the cat.

    When you think about it only one of four things can happen.........

    KB4073290 will not install.

    KB4073290 installs and replaces KB4056892.

    KB4073290 installs and co exists with KB4056892.

    or.......................

    I will post the results after I restore from system image backup.

    Faint heart doesn't win fair princess.

    Faint heart is less likely to be eaten by dragon.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2018-01-26T23:10:22+00:00

    On the newer  machine "check for updates"  does not offer KB4073290.

    I may not be interested in restoring AI Suite (I like the workaround) ,  still the question remains.

    Does KB4073290 fix other ( as yet not noticed) breakage caused by KB4056892?

    I don't think I am willing to risk possible damage by manually installing KB4073290.

    Like you said, we will probably have to wait until February to find out if KB4073290 is a companion or a replacement.

    Wandy_a

    I don't think you need to do anything, it seems as though your 32-bit machine is fixed by 4073291 and your newer 64-bit kit accepted 4056892 with minor "damage". Therefore you don't need 4073290 and that's why it's not shown as available in updates.

    I've had to do three resets after previous "updates" in the past year so I'm not too hopeful we're out of the woods yet. Tuesday, Tuesday...........

    Brian

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2018-01-26T22:51:32+00:00

    MELERIX

    Short, concise and probably oversimplified.

    If a somewhat newer AMD system (Bulldozer series) was NOT  "stuck in Windows logo after first reboot",  then KB4056892 is the correct update?

    Thanks, it would help to know for sure.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2018-01-26T21:14:25+00:00

    you are confusing things xD

    KB4073290 & KB4073291 both updates are cumulatives and do the same, these updates fix the bug that was causing some AMD CPUs stuck in Windows logo after first reboot.

    the main difference is that KB4073290 is for x64/64bits and KB4073291 is for x86/32bits.

    thats all.

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2018-01-26T20:22:10+00:00

    Brian

    I am also trying to understand what Microsoft is doing here.

     I can add some information as to KB4073291 for older AMD devices and  Win-10 32 Bit.

    With KB4056892 showing as Blocked I installed KB4073291 (The file size was app 330MB).

    After the Install  ...........

    KB4073291, (AMD Athlon X2 6000+ 32 Bit) results in Windows 10 build 1709 version 16299.201.

    I checked with Show/Hide and KB4056892 did not show as blocked any longer.  It was just plain gone!

    Checking for updates KB4056892 is NOT offered.  Good, it was a bad thing.

    On a newer machine, ( AMD fx-8150,  ASUS M5A97, Win-10 64 Bit) , KB4056892 only apparent  breakage is ASUS AI Suite 2.  There are folk with different ASUS MBs where KB4073290 resolves the problem with  ASUS AI Suite 2 and ASUS AI Suite 3.

    On the newer  machine "check for updates"  does not offer KB4073290.

    I may not be interested in restoring AI Suite (I like the workaround) ,  still the question remains.

    Does KB4073290 fix other ( as yet not noticed) breakage caused by KB4056892?

    I don't think I am willing to risk possible damage by manually installing KB4073290.

    Like you said, we will probably have to wait until February to find out if KB4073290 is a companion or a replacement.

    Was this answer helpful?

    0 comments No comments