Following significant community backlash, AMD has confirmed it will reinstate the option for memory encryption on its Ryzen 9000-series desktop processors. The decision reverses a controversial move by the chipmaker to remove the feature, known as Memory Guard or TSME (Transparent Secure Memory Encryption), from a recent BIOS update. The reversal underscores growing tensions between hardware vendors and users over security feature accessibility and corporate transparency.
AMD Confirms BIOS Update to Restore Memory Guard
Over the weekend, AMD announced plans to restore the BIOS toggle for Memory Guard in a firmware update scheduled for July. “Regarding certain non-PRO Ryzen 9000-series desktop processors, a BIOS option to enable Memory Guard was previously available but was removed in a recent update,” AMD stated. “Based on valuable community feedback, we will reinstate this option in an upcoming BIOS release in July.” This effectively confirms that the removal was a deliberate action, not an accidental omission, and that enough users voiced concerns to force a policy reversal.
Why Was TSME Removed in the First Place?
AMD has yet to provide a technical or strategic justification for the initial removal, leaving the community to speculate. The most cynical interpretation is that AMD sought to differentiate its higher-end PRO and Ryzen 9 SKUs, effectively gating a basic security feature behind a price premium. However, other plausible explanations exist.
One technical possibility involves the inherent performance overhead of memory encryption. TSME encrypts all data written to system memory (DRAM) and decrypts it on read, which introduces measurable latency. For gamers—a primary audience for the Ryzen 9000 series—every millisecond counts. It is plausible that AMD removed the toggle to simplify BIOS validation or to prevent users from inadvertently enabling a feature that degrades gaming performance. The core problem, however, was removing the choice from the user entirely without explanation or warning.
What Is AMD Memory Guard (TSME)?
AMD Memory Guard, based on the TSME technology, is a hardware-level encryption feature that encrypts the entire contents of system memory. This protects sensitive data—such as encryption keys, passwords, and application data—from physical attacks like cold boot attacks or malicious hardware probing. While the average home gamer may not face such sophisticated threats, the feature is critical for workstation users, developers, and professionals handling sensitive data on a desktop machine. Removing the option without warning left these users exposed without their consent, effectively weakening the security posture of their systems overnight.
Silence as a Security Flaw
The incident, coupled with AMD’s initial silence, underscores a troubling shift in the tech industry’s relationship with its customers. The unwillingness to acknowledge changes that impact a user’s security posture reflects a diminished sense of accountability among dominant hardware vendors. The fact that community outcry was required to reinstate a fundamental security option, rather than a transparent engineering discussion, is emblematic of this power imbalance. Whether the removal was motivated by commercial segmentation or technical convenience, the lack of communication eroded trust.
What Ryzen 9000 Users Should Do Next
For users currently running a Ryzen 9000-series processor, the immediate course of action is to monitor your motherboard vendor’s support page for the upcoming July BIOS update. Once available, users who prioritize data security over absolute peak gaming performance should navigate to the BIOS menu, locate the “Memory Guard” or “TSME” option, and enable it. Be advised that enabling this feature will introduce a minor performance penalty due to the encryption overhead. Evaluate your own threat model: if you handle sensitive documents, code, or credentials on your desktop, enabling Memory Guard provides a valuable layer of defense against physical memory attacks. For dedicated gamers who do not store sensitive data on their system, leaving it disabled remains a valid but now deliberate choice.
