AMD X2 +4600 has the same issue.
After installation of KB4056892 boot failure, after roll-back error 0x800f0845
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
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?
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-01-08T23:31:56+00:00 -
Anonymous
2018-01-08T23:13:52+00:00 MELERIX
Disabling Virtualization seems reasonable, most reasonable. My AM2 system is currently powered off in a "Not Bricked" or better said "Not Bricked again Yet" state.
I am trying to find a workaround (blowout patch) that is better than the 6 or 35 day thing. It would sure help things out until there is a fix.
This PC doesn't seem to want to do the rollback thing so I appear to be stuck with "Refresh your PC" .
It's about a two and a half hour cycle time. Doing a lot of reading to try to get the most out of each cycle.
I did see that Jaroslav attempted this and it did not help, however it was attempted as recovery from the failed "Bricked" state.
Could you elaborate on the idea of turning off Virtualization and / or HPET or why that may be worth a try and possibly modify the install if turned off in the "Not Bricked again Yet" state.
Thanks
-
Anonymous
2018-01-08T22:33:13+00:00 Anders
Just a caution. On the fx- nnnn systems, if you are using mother board utilities for things like fan control, you may wish to see if those utilities are working and that you are getting sufficient cooling.
See here.........
Like I said, just a word of caution.
-
Anonymous
2018-01-08T22:25:06+00:00 If your motherboard supports it, could you upgrade the microprocessor? Or, if not, upgrade the motherboard and CPU?
I haven't seen this suggested anywhere, but you may then be able to boot into Windows (does anyone know if this will work)?
-
Anonymous
2018-01-08T22:05:52+00:00 Don't hold your breath on Microsoft fixing this. They only have to support Windows 10 on systems that the manufacturer's support it on, and no manufacturer is going to have 10 support for an ancient 939/AM2 machine.
This is wrong assumption. Nobody said that it is not compatible. In fact the upgrade assistant showed that its compatible. If I knew it's not compatible and that the OS would kill my machines few months later, I wouldn't' buy the licenses. It's simple.
Unfortunately what I said is truth. Microsoft has said it themselves; they only need to make sure Windows 10 works on machines that the manufacturer's support 10 natively on.