01What happened

The story, straight

AMD confirmed to Tom's Hardware that it will reinstate Transparent Secure Memory Encryption (TSME) on desktop Ryzen 9000 processors via a BIOS update in July. The firmware-level encryption feature — branded as Memory Guard on Ryzen PRO chips but available on non-PRO CPUs — was quietly removed earlier this year with the AGESA 1.2.7.0 update, which Ars Technica reported on. AMD cited 'valuable community feedback' as the reason for reversing course.

AMD quietly killed a memory encryption feature on Ryzen 9000 desktop chips earlier this year and people noticed. TSME — the firmware-level encryption that protects against cold boot attacks — was stripped out with the AGESA 1.2.7.0 update, Ars Technica flagged it, and now AMD says it's bringing it back in a July BIOS update because of 'valuable community feedback.' Classic move: remove the feature, wait for backlash, restore it and call it listening.

02Spread timeline

Where it actually started

Early 2026Origin
AMD quietly removes TSME from desktop Ryzen 9000 CPUs with the AGESA 1.2.7.0 update.AMD ships AGESA 1.2.7.0 and TSME is just gone, no announcement.
source
Jun 16–18, 2026
Ars Technica reports on the silent removal of TSME from consumer Ryzen chips.Ars Technica flags the missing TSME feature, drawing wider attention.
source
Jun 20, 2026
AMD confirms to Tom's Hardware that TSME will return via a BIOS update in July.AMD tells Tom's Hardware it's restoring TSME in July, blames 'community feedback.'
source

03Source receipts

Every claim, linked

04What's solid, what isn't

What's solid and what isn't

Confirmed
  • AMD will reinstate TSME on desktop Ryzen 9000 processors via a BIOS update in July.
  • TSME was removed earlier in 2026 with the AGESA 1.2.7.0 update.
  • AMD cited 'valuable community feedback' as the reason for bringing TSME back.
Disputed
  • The exact number of Ryzen 9000 users affected by the TSME removal.

05Why it matters

The editorial take

TSME encrypts all data stored in RAM at the hardware level, defending against physical attacks where someone can extract sensitive data from memory after a sudden shutdown. Removing it silently — then reinstating it only after press coverage and user backlash — highlights an accountability gap in how chipmakers handle security features on consumer hardware. The incident echoes similar controversies where manufacturers quietly strip functionality and only reverse course when caught.

the quiet removal → public pressure → reversal pipeline is becoming the standard playbook. users had a security feature yanked without notice and only got it back because journalists and forums made noise. good outcome, but the pattern is exhausting.