After installation of KB4056892 boot failure, after roll-back error 0x800f0845

Anonymous

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?

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

Anonymous

2018-01-14T16:12:22+00:00

My HP Pavilion Slimline desktop PC with AMD Athlon processor gets into an unbootable state following the KB4056892 update Windows 10. I did a system restore and disabled windows updates. Microsoft claims that the update would be paused for my computer, but after I resumed windows updates, KB4056892 was pushed to my computer with the same unbootable results. I had to system restore and disabled updates again. Will I ever be able to resume windows updates?

confirmed, no idea why but Microsoft is pushing again the update, and is causing AMD Athlon 64 and related CPUs to stuck in Windows logo after reboot -.-'
Was this answer helpful?

0 comments No comments
Anonymous

2018-01-14T16:19:58+00:00

Try the advice from Monkey57 at Page 27 of this same thread.

https://answers.microsoft.com/en-us/windows/forum/windows_10-update/after-installation-of-kb4056892-boot-failure-after/6c015632-2a45-4725-a882-f231f8c88f36?page=27&messageId=a115832d-7787-49ee-9539-00e635a8e0f4

If the link does not work try to clear cookies for answers.microsoft.com

Note that after cleaning cookies probably you will be prompted to reinsert your Microsoft credentials to post to the forum.
Was this answer helpful?

1 person found this answer helpful.

0 comments No comments
Anonymous

2018-01-14T16:43:54+00:00

don't worry, I know what to do, I'm just confirming that the issue is back, the bug strikes again, and no idea why is Microsoft pushing the updated again in the affected machines without even fix the issue first.
Was this answer helpful?

0 comments No comments
Anonymous

2018-01-14T17:26:01+00:00

greed plan and simple.
Was this answer helpful?

0 comments No comments
Anonymous

2018-01-14T20:54:17+00:00

Last weekend I had KB 4056892 forced on me which then caused the INACCESSIBLE_BOOT_DEVICE until i managed to roll back to before patch and all was fine until this weekend and its been pushed on me again and ive had nothing but a cycle of INACCESSIBLE_BOOT_DEVICE then remove patch PC works until restart then Win10 forces KB4056892 on mew again then PC wont boot etc etc.

In the end I have removed the patch and shut off Windows update service just to make my PC useable.

This is effecting alot of users now, I have a PC that was built in November with an AMD Ryzen7 1700 this is not just effectiong old AMD CPU's.

Why..why..oh why microsoft can you not stop this patch going to AMD owners, go and fix Intel's mess but leave the rest of us alone.
Was this answer helpful?

0 comments No comments