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.
Despite the implementation of blocking of this update to AMD processors.
KB4056892 crashed AMD processor system "AMD Athlon(tm) 64 X2 Dual Core Processor 4400+ 2.30 GHz" and does not seem to be on the new block list for AMD processors as per KB4073707. Could the Moderator please pass this on to your update team as my AMD system has been trashed?
![](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(137.6, 51%, 23%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EM%3C/text%3E%3C/svg%3E)
you can pause Windows Update inside Advanced Options in Windows Update options.
For those looking for the quick (& dangerous) fix for Win10 Pro & older AMD systems see the above fix.
JH
I have been watching this and other threads and in one asked "How will we know when it is safe"?
It appears the 'hold off' is either not implemented as yet or not implemented correctly.
Not knowing when it is "safe" is just wasting our and Microsoft's cycles. That in and of itself is a problem.
If this is still going on tomorrow (1/10/2018) I will probably open yet another tread asking if the hold off is implemented and/or not working. I will append a pointer in the threads I am following.
You know you have been around these things too long when the humor just takes over......
I mean, heck, why don't they just give us a call?
After 20 years of computing Microsoft have managed to do what no hacker or virus have done to my computer - shut it down with a patch that was supposed to aid my computing experience. Is this like the Apple way of getting us older users to purchase a new machine (Apple slowing usage and not allowing updates to older machines)? My laptop was working perfectly until Tuesday 8th Jan 2018 but now it hangs at logo screen. Are Microsoft going to reply to this problem? Are they working on a fix? What are they going to do to compensate me for damaging my previously perfectly working laptop (an Acer Aspire 7520 with Athlon AMD 64 x 2 processor)? This is a massive problem and needs answers not silence.
Mine is a Toshiba Satellite and it started after the stupid update as well. This isn't my first issue with Windows 10 and I am getting so sick of it. They need to fix this and soon, I have work on my laptop I need to get back to. I had to go back to using my old Windows 7 machine, never had an issue like this in 7.
