Technology

AMD to Restore TSME on Ryzen 9000 Desktop CPUs via July BIOS Update

Martin HollowayPublished 12h ago3 min readBased on 2 sources
Reading level
AMD to Restore TSME on Ryzen 9000 Desktop CPUs via July BIOS Update

AMD to Restore TSME on Ryzen 9000 Desktop CPUs via July BIOS Update

AMD will reinstate Transparent Secure Memory Encryption (TSME) on non-PRO Ryzen 9000 desktop processors through a BIOS update scheduled for July, the company confirmed, citing community feedback as the driver for the reversal. Tom's Hardware

TSME — marketed by AMD under the Memory Guard branding in its PRO product line — encrypts all DRAM contents transparently at the memory controller using AES-128, requiring no OS or application changes. It is a hardware-level mitigation against cold-boot attacks and physical memory extraction, where an adversary with direct hardware access can read unencrypted memory contents after a system is powered off or rebooted. For most consumer workloads the feature is invisible; it asks nothing of software and exacts a negligible performance overhead under typical conditions.

AMD had quietly disabled TSME on consumer Ryzen CPUs prior to the community's response, a decision that drew pointed criticism once it became widely known. The feature had been available on earlier consumer Ryzen generations, making its removal on the Ryzen 9000 family a step backward rather than a deliberate omission from a new baseline.

The distinction between consumer and PRO SKUs is worth holding in mind here. AMD's PRO line — targeting managed enterprise and commercial deployments — has long carried Memory Guard as a selling point, partly because enterprise buyers explicitly check for such capabilities during procurement. Stripping an analogous feature from the consumer desktop line, without announcement, suggested AMD may have been drawing a sharper product-tier boundary. Whether that was the original intent, the company moved to undo it once the community registered its objection clearly enough.

AMD's phrasing — "valuable community feedback" — is the language of a vendor who got the temperature reading wrong. It is polite, and it tells you almost nothing about why the feature was removed in the first place. No technical justification for the original disablement has been published. That gap matters: without knowing whether this was a power or thermals decision, a firmware complexity issue, or simply a product-segmentation call, it is difficult to assess whether the July BIOS update fully closes the question or defers it.

The practical impact on Ryzen 9000 owners is straightforward. Once the update ships, enabling TSME will be a BIOS toggle — no OS reinstall, no application changes, no performance cliff to worry about for standard workloads. Users handling sensitive data on consumer hardware, including developers, researchers, and anyone whose machine might be physically accessed or transported, get a meaningful security layer back.

The broader context is a small but real shift in how AMD's consumer base is pushing back on feature decisions. Physical memory encryption has not historically been a flashpoint in the desktop CPU market; it is the kind of capability that enterprise security teams enumerate and consumers seldom notice. The fact that its removal generated enough noise to reverse an AMD firmware decision suggests that at least a meaningful slice of Ryzen's non-PRO audience — system builders, security-aware developers, enthusiasts running home labs with sensitive workloads — treats it as load-bearing rather than decorative.

Worth noting: the July timeline gives board partners a narrow window. TSME enablement is gated on AGESA microcode updates that AMD provides to motherboard OEMs, who then build and validate their own BIOS releases. The rollout will therefore be staggered across the ecosystem rather than arriving simultaneously for all Ryzen 9000 platforms. Users should watch their board vendor's support pages rather than expecting a single coordinated drop.

The episode also serves as a quiet reminder that firmware-level security features can be removed as easily as they are added — and that, absent proactive disclosure, users generally have no visibility into those changes until a third party documents them. AMD's reversal is welcome. The circumstances that made it necessary are less so.