Electronics

AMD to Restore TSME (Memory Encryption) on Consumer Ryzen Processors After Backlash

AMD to Restore TSME (Memory Encryption) on Consumer Ryzen Processors After Backlash

AMD backpedaled on its recent decision to remove Transparent Secure Memory Encryption (TSME) feature on its consumer Ryzen processors. The company had, in April, quietly disabled the feature for Ryzen consumer processors through an AGESA update encapsulated into motherboard firmware updates. The idea probably was to restrict TSME to Ryzen commercial-segment processors, sold under the Ryzen PRO brand, besides Ryzen Threadripper WX workstation processors, and EPYC server processors. For reference, Intel offers a similar feature, TME-MK (Total Memory Encryption-Multi-Key) on even its consumer Core processors, and not just its commercial Core vPro processors.

AMD said that it has decided to restore TSME “based on valuable community feedback,” and end-users should expect UEFI firmware updates that restore the feature starting next month (July 2026). TSME is a hardware-based feature that leverages fixed-function hardware on the silicon to encrypt the contents of the memory, providing an additional layer of security. Since AMD shares a common IOD design across its Ryzen consumer and Ryzen PRO commercial product lines, the feature is physically present.

In a statement to Tom’s Hardware, AMD said:

AMD Memory Guard (Transparent Secure Memory Encryption, or TSME) is a hardware-based memory encryption technology available on our Ryzen PRO desktop and mobile processors where supported in silicon. It is a foundational security feature, and we have no plans to remove support from our Ryzen PRO lineup. This commitment holds now and in the future.

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. Based on valuable community feedback, we will reinstate this option in an upcoming BIOS release in July.”

Leave a Reply

Your email address will not be published. Required fields are marked *