This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](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)
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.
That's what the boot menu idea could do but you also were on that tack via the Power button's Shift-Restart to get into Advanced Boot Options.
Well essentially this would be Safe Mode, yes? Or were you suggesting I try something else from the Advanced Boot Options? I don't think there's much left to try unfortunately. I'll keep at it though.
Another update: So I forgot that in addition to system restore there's another restoration variant available that rolls windows back to a previous version (i.e. major update I assume?). I just tried this option and am now able to get to a fully functional user account desktop. Any suggestions on whether to attempt further Windows Updates at this point? Or should I disable for the time being? Or perhaps, now there an update roll-up which addresses most of the issues AMD users are experiencing and it might be safe to continue with updates accordingly?
If it were my PC I would just allow it to roll through the updates without intervening, as you have managed to debug the problem and can always backout to that point again.
Did you actually run a chkdsk or scan in the end? That problem seemed like it could be corruption of either video management software or video drivers, perhaps one of the patches caused the problem ..it wouldn't hurt running a chkdsk or scan too look for bad disk sectors.
If it were my PC I would just allow it to roll through the updates without intervening, as you have managed to debug the problem and can always backout to that point again.
Did you actually run a chkdsk or scan in the end? That problem seemed like it could be corruption of either video management software or video drivers, perhaps one of the patches caused the problem ..it wouldn't hurt running a chkdsk or scan too look for bad disk sectors.
Agreed. I typically don't like manually disabling specific elements when it comes to Windows Updates.
And thanks for the reminder. I will be sure to run chkdsk as an additional preventative measure. I've also installed and ran CCleaner to help purge any bloat and temp files from the subsequent update cycles.
Thanks again to everyone for all the guidance and suggestions. Much appreciated!
Big thanks to MrCurlyWurly and Blubi who showed the way to un-brick my AMD Athlon 62x2 based computer after the kb4056892 update fiasco.
One thing that really got me was the fact that what Windows command prompt on my screwed up machine told me about the version number of Windows (ver command--winver was not recognized when run from the command prompt in recovery and diagnosis mode!!!) had nothing whatever to do with what the version ID listed in the Microsoft Update Catalogue. I did a google search and found that the version info I was seeing (in this case 10.0.14393) was a build associated with Redstone 1, version 1607. What a maze of gibberish to wade through for a layperson!
Anyway, Thank you gentlemen for stepping into the breach!
Webb
jwmealy
