Update KB4056892 released by Microsoft in a hurry to mitigate the Meltdown/Spectre vulnerability seems to come with unpleasant side effects. Computers with AMD CPUs refuse to start with error code 0x800f0845.
Advertising
Within my blog post Windows 10: Critical Updates (01/03/2018) I reported a few days ago about the cumulative update KB4056892 for Windows 10 version 1709. In the introduction to the blog article I wrote:
First: Wait until these updates are offered via Windows Update. Do not try to download those updates from the Microsoft Update Catalog. Currently, Microsoft seems to be distributing the updates only on certain machines (where telemetry signals that this is okay). If you install an update manually, it could kill the system or software (e. g. virus scanners from third-party vendors).
Many forum threads reporting issues
I received the first comments within my German blog on January 5, 2018. A user reported strange issues with Update KB4056892 on his AMD system.
At least on older AMD CPUs and/or graphics, the update seems to hang after the second reboot (after 30% at the first reboot) of the Windows logo with a black background. It simply doesn't work, to install this update.
He then also referred to corresponding threads within the German-speaking Microsoft Answers forum and in the Windows 10 forum. People reported that Windows fails to install the update with error code 0x800f0845.
Also in the US Microsoft Answers forums like this one, users reported that Windows 10 doesn't work after restarting during the update installation. Further MS-Answers forum posts can be found here and here, Within the latter forum post, the user reported, Windows made a rollback and error code 0x800f0845 has been issued. Some users has been able to bring their Windows 10 systems back to life, using system restore. Other users ends re-installing a system backup.
Only AMD systems affected
Browsing German forums, I found that only AMD CPUs are affected. Here is a list of AMD processors mentioned:
Advertising
- AMD Athlon 64 X2
- Athlon 64 X2 4200+
- AMD Athlon ™ 64 3800+
- AMD Athlon 64×2 Dual Core 4400+
- AMD Athlon Dual Core 4850e
- AMD 4850e
- AMD-Athlon 64×2 5200+
- HexaCore AMD Phenom II X6 Black Edition 1090T
- DualCore AMD Athlon 64 X2, 2000 MHz (10 x 200) 3800+
- AMD Athlon(tm) 64 X2 Dual Core Processor 6000+
Some workarounds
If System Restore is still working and you are able to go back to a previous restore point, it is recommended that you disconnect from the Internet. This prevents the package from being downloaded again. In this forum thread someone stopped the services for BITS, Windows Update etc.
If the update package is pending in the installation, the note given within this forum thread may help. Enter the following command in the command prompt (if necessary, under Windows PE):
DISM /Image:D:\ /Cleanup-Image /RevertPendingActions
Adjust the drive letter D: to your environment. Within this blog post a similar issue with non bootable VM are reported.
You can then try to delay the update installation in Windows 10 Pro/Enterprise by 35 days. On Windows 10 Home systems, it may help to block the KB4056892 update with the wizard, discussed within my blog post How to block Windows 10 updates.
