Windows 10 Updates Are Bricking Systems With Older AMD CPUs

AMD processors aren’t affected by the Meltdown Speculative Execution CPU issue, but the quick fix for Meltdown and Spectre by AMD is apparently causing issues with a number of AMD processors from before 2009. The problem is large enough that Microsoft has stopped offering the Windows security patch due to so many reports of PCs not booting.

“After investigating, Microsoft has determined that some AMD chipsets do not conform to the documentation previously provided to Microsoft to develop the Windows operating system mitigations to protect against the chipset vulnerabilities known as Spectre and Meltdown,” Microsoft’s security advisory reads. “To prevent AMD customers from getting into an unbootable state, Microsoft will temporarily pause sending the following Windows operating system updates to devices with impacted AMD processors at this time.”

AMD Ryzen 7 1700X Processor

Ryzen Processors Aren’t Having Issues It Appears

Legit Reviews reached out to AMD for comment and was sent the following statement.

“AMD is aware of an issue with some older generation processors following installation of a Microsoft security update that was published over the weekend. AMD and Microsoft have been working on an update to resolve the issue and expect it to begin rolling out again for those impacted shortly.”

To prevent AMD customers from getting into an unbootable state, Microsoft has temporarily paused sending the following Windows operating system updates to devices that have impacted AMD processors:

 

Print
  • albert89

    Unfortunately we are seeing more and more M$ updates bricking not only Win 10 OS but all manner of hardware connected to it. This never used to happen with Window OS in the recent past. I’m using Win7 and seem to be missing out in all this grief. I learnt my lesson as a Windows insider for Win10 and rolled everything back to Win7. But I never expected ongoing problems to occur in their latest OS. After I left I just assumed they would be fixed 6 months after leaving. That was a few years ago !