AMD will restore Transparent Secure Memory Encryption (TSME) on its Ryzen 9000 consumer desktop processors through a BIOS update coming in July, the company confirmed, citing community feedback as the reason for the reversal. Tom's Hardware

TSME — sold under the Memory Guard brand in AMD's PRO product line — encrypts all system RAM at the memory controller level using AES-128 encryption, without requiring any changes to the operating system or applications. This hardware-level feature defends against cold-boot attacks, where someone with physical access to a powered-down or rebooted system can extract unencrypted data directly from memory. For typical consumer workloads, the feature runs invisibly with negligible performance impact.

AMD had quietly disabled TSME on consumer Ryzen CPUs before the backlash, a decision that drew sharp criticism once discovered. The feature had been present on earlier consumer Ryzen generations, so its removal on Ryzen 9000 represented a step backward rather than an intentional omission from a new baseline.

The consumer versus PRO product distinction matters here. AMD's PRO line, built for enterprise and commercial environments, has long advertised Memory Guard as a core capability because enterprise procurement teams explicitly evaluate such security features. Removing an equivalent feature from the consumer desktop line without announcing it suggested AMD might have been deliberately creating a sharper separation between product tiers. Whether that was the original strategy, the company has reversed course now that the community response made its position clear.

AMD's language—"valuable community feedback"—is what you hear from a company that misread the room. It is diplomatic and explains almost nothing about why the feature was disabled initially. No technical reason for the original removal has been made public, and that absence is worth examining. Without knowing whether this was a power-consumption, thermal, firmware complexity, or purely product-segmentation decision, it is difficult to judge whether the July update fully resolves the issue or simply postpones the underlying question.

Once the BIOS update rolls out, users will be able to toggle TSME on or off from their BIOS settings—no reinstalling the operating system, no software changes, and no performance penalty for standard workloads. Anyone running sensitive applications or data on consumer hardware, including developers, security researchers, and users whose machines might be physically transported or accessed, regains a meaningful layer of protection.

This episode reflects a broader shift: AMD's consumer base is beginning to push back on feature decisions in ways that actually change outcomes. Physical memory encryption has not typically been a focal point in the desktop CPU market; it is the kind of capability that enterprise security teams check for and most consumers never notice. That removing it prompted enough community pressure to reverse an AMD firmware decision suggests a meaningful segment of Ryzen's non-PRO audience—system builders, security-conscious developers, enthusiasts running home labs with sensitive data—regards TSME as functionally important rather than a nice-to-have.

One practical consideration: the July timeline creates a tight window for motherboard manufacturers. TSME support requires AGESA microcode updates from AMD, which motherboard makers then integrate into their own BIOS releases and validate. The rollout will therefore be uneven across different boards and manufacturers rather than happening simultaneously for all Ryzen 9000 systems. Users should track their motherboard vendor's support pages rather than expecting a coordinated release date.

The broader lesson is quieter but worth keeping in mind. Firmware-level security features can be turned off as easily as they are activated, and absent clear communication, users typically have no way of knowing those changes have happened until third parties uncover them. AMD's decision to restore TSME is the right call. The circumstances that forced it to do so are not.