If you're still on build 1607, then I would now allow Windows Update to update automatically to 1709 . It should (in theory) work for you, because Microsoft have now fixed the AMD CPU bug (as of 31 January). Windows update will install version 1709 and then subsequently install the latest cumulative update from January 31, 2018—KB4058258 (OS Build 16299.214). It should not attempt to install the earlier cumulative update. I think (hope) this should work for you. My HP Pavilion DV7-2110sa (AMD Turion X2) is running fine with KB4058258.
After installation of KB4056892 boot failure, after roll-back error 0x800f0845
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.
494 answers
Sort by: Newest
-
Anonymous
2018-02-03T12:09:33+00:00 -
Anonymous
2018-02-03T03:02:32+00:00 So just for my understanding, you're suggesting that I install KB4057142 while currently using the Win 10 1607 build, then attempt to re-install build 1709 and hopefully that will eliminate the boot failure issue(s)?
yes, that is my idea, I hope it solve the issue for you.
Good to hear you have resolved the boot issue with your machine. But I'm curious, if you had booting troubles, how were you able to install and run the "Show/Hide Updates" utility? I can run this while on build 1607 because the system boots fine. That wouldn't have worked though using build 1709 (non-bootable). But based on earlier discussions above, perhaps I need to find and uninstall KB4056892 since it is not part of build 1709. Then, install patch KB4057142. THEN, attempt to re-install 1709 and hope for the best.
Well I'm waving the white flag I think. I see no record of KB4056892 ever being attempted to be installed. KB4057142 was already recently installed successfully. I'm going to remove all video hardware from device manager and delete the corresponding drivers. Will try 1709 one last time if it is still unsuccessful, then I will need to find a way to block it from installing when I roll back to 1607.
Consequently, I did start another topic since now I believe my direct issue is pertaining to this thread less and less. :(
-
Anonymous
2018-02-02T23:29:26+00:00 Unfortunately, as this is an older (but still perfectly functional laptop) it is no longer supported by HP.
There have been no bios or driver updates for this machine for several years. But it runs Windows 10 fine and runs all the software I need it to. I always allow the O/S to install the latest updates - but of course that was the cause of the problem as Microsoft's update was buggy!
Microsoft should have a system built into the O/S such that if an update fails to install the user can have the option to disable it. They should not send out updates that break machines with no easy option to recover. I may have now got my machine to work, but I suspect many others will have been less fortunate (and I am fairly tech savvy).
-
Anonymous
2018-02-02T22:54:20+00:00 Brian
Having decided to wait for the scheduled update, this post is to document what has happened.
AMD fx-8150 (Bulldozer) Win-10 64 Bit. 02/02/2018
- KB4058258 Installs without problem and with no apparent breakage.
- Windows specifications : Win-10 Pro, Vs. 1709, build 16229.214
- KB4056892 No longer appears in Control Panel --> Programs and Features --> Installed Updates.
- KB4073290 Was never installed. No mention of this update anywhere.
AMD Athlon X2 6000+ (Windsor) Win-10 32 Bit. 02/02/2018
- KB4058258 Installs without problem and with no apparent breakage.
- Windows specifications : Win-10 Home, Vs. 1709, build 16299.214. Previous after KB4073291 install was Vs. 16299.201
- KB4073291 that was installed on 1/18/2018, no longer appears in Control Panel --> Programs and Features --> Installed Updates.
- KB4056892 still shows Failed to install on 1/17/2018. As Expected.
Summary for AMD Athlon X2 6000+ (the real problem child.)
- KB4056892 "Bricks" system
- Attempts at recovery.............. ( I don't want to talk about it )
- Restore from REDO System Image Backup.
- Block KB4056892 using Show / Hide. Timing is critical.
- Manually install KB4073291.
- Wait!
- KB4058258 Installs without problem and with no apparent breakage.
All’s well that ends. At least for now.
-
Anonymous
2018-02-02T22:23:52+00:00 Yes, it does help to check regularly for updates to your device. Not only from Microsoft but also from your computer manufacturer (who will often have BIOS and CPU updates before they are available from Microsoft).