AMD Ryzen Chipset Update Adds CET Compatibility Across AM4 AM5

AMD has quietly pushed a new set of Windows chipset drivers that touch almost the entire modern Ryzen family — from Ryzen 9000 down through 7000, 5000 and 3000 series platforms — and while the headline of broader hardware coverage is welcome, the release brings a mix of meaningful security upgrades, compatibility changes, and user-facing risks that every enthusiast and IT admin should evaluate before clicking Install.

Background / Overview​

AMD’s chipset driver packages are not a single monolithic component but a collection of small kernel and user-mode drivers (PMF/PPKG, PSP, SMBus, GPIO, PPM provisioning, RAID stacks, etc.) that together manage platform features such as power management, platform firmware interaction, and chipset peripherals. Over the past 18 months AMD has released several major and minor chipset packages that introduced Windows 11 24H2 compatibility, broadened motherboard support (including new X870/X870E boards), and — critically — added compatibility flags for Microsoft’s Control-flow Enforcement Technology (CET). These changes are spread across multiple packages (for example, driver builds in the 5.x, 6.x and 7.x families), and the new wave of updates continues that trend while also changing how installs and rollbacks behave.
In plain terms: this is a maintenance-and-security release series with some platform enablement that matters for security-conscious Windows users and enterprises, but it also carries installer behaviors and stack changes that have produced real-world friction for some users. Community reports and forum threads show both successful installs and problems ranging from cosmetic uninstall-log errors to performance regressions and rollback failures — factors that should influence how people approach deployment.

---

What AMD shipped — the technical highlights​

Multiple packages and version lines​

• AMD’s release notes and distribution channels show several chipset-package versions active over the past year: 5.05.16.529, 6.10.17.152, 7.06.02.123 (and other 7.xx and 6.xx builds seen in OEM/third-party channels). Each package is a superset of small drivers and utilities that are selectively installed by AMD’s chipset installer UI.
• Different OEMs and download mirrors (motherboard vendor sites, station-drivers, TechPowerUp mirrors) may list slightly different builds or WHQL-signed variants; the official AMD release notes are the primary source of truth for what changed in a given build.

Security: CET / CETCOMPAT additions​

• One of the consistent, verifiable changes across recent packages is the addition of CET compatibility flags (often noted as CETCOMPAT) for selected low-level drivers such as the AMD PPM provisioning driver and other power-management components. CET is Microsoft’s control-flow enforcement technology intended to make certain classes of control-flow hijacking attacks harder to exploit. AMD’s release notes explicitly list CETCOMPAT entries for several drivers starting with packages in the 6.x and 7.x lines. This is notable because chipset-level drivers can be a vector for kernel-level attacks; enabling CET compatibility is a defensible security hardening step.

Platform enablement and chipset compatibility​

• Several recent packages add explicit support for new AMD chipset families and boards (for example, support entries for X870 and X870E series motherboards appear in the 6.10.17.152 release notes), plus updates intended for Windows 11 24H2 builds. The installer notes in some releases also show updated installer EULAs and small behavioral changes to how components are installed.

RAID and RAIDXpert components​

• AMD’s RAID/RAIDXpert packages have been updated alongside chipset drivers in some releases, and AMD itself and third-party posts have warned administrators to be cautious about upgrading RAIDXpert or RAID stacks on production boxes without testing. RAID stacks are among the riskiest to upgrade in-place for servers or multi-disk arrays; the release notes and community threads suggest administrators treat any RAID component upgrades as a maintenance-window action.

---

Why the CET changes matter — security implications​

Control-flow Enforcement Technology (CET) is a Microsoft kernel-level mitigation that implements features such as shadow stacks and indirect branch tracking to make certain memory- and control-flow hijacking attacks substantially harder. Historically, CET support has required cooperation between Microsoft’s OS toolchain, application/driver build options, and vendor-provided drivers. AMD’s addition of CET compatibility flags in chipset driver packages is an important step because:

• It helps ensure AMD’s chipset drivers can work with Windows’ CET enforcement modes rather than being blocked or causing compatibility concerns. That reduces attack surface at a platform level for systems where CET is enabled.
• It signals AMD’s alignment with Microsoft’s mitigation roadmap, which is relevant for enterprises subject to compliance controls or those running hardened baselines. For teams operating in high-security environments, CET-ready drivers make it easier to adopt OS-level mitigations without breaking platform behavior.

Caveat: while CET compatibility is meaningful, its effective protective value depends on the rest of the stack — firmware, other drivers, and application binaries — being configured correctly. CET is not a panacea and does not eliminate the need for firmware integrity checks, timely microcode/firmware patches, or secure boot/TPM protections.

---

Compatibility and real-world reports — what users are seeing​

Community-reported issues​

Community threads and support forums show a mixture of outcomes. Common themes include:

• Cosmetic or misleading “uninstall summary” messages on non-English operating systems where the uninstaller reports a “fail” status even though components updated correctly. This appears repeatedly in release-note known-issues and user posts and is not necessarily indicative of a broken install, but it has caused confusion.
• Some users reporting performance regressions in certain workloads after updating from one major package to another, especially when moving across a large version jump (for example, older installs to 7.xx). These reports are mixed and highly configuration-dependent; in certain cases fixing the issue required a BIOS update or a clean driver reinstall.
• Instances where installing a 7.xx family installer appears to prevent reinstalling older 6.xx packages, complicating rollback strategies for users that test new builds and then want to revert. That installer policy change warrants caution before wide deployment. Several release notes and forum posts explicitly warn about installer-induced downgrade restrictions.
• RAID stack and RAIDXpert warnings: admins have been explicitly reminded to validate RAID packages in a lab before upgrading production arrays due to the critical nature of those components.

Verifiable facts from official notes​

• AMD’s official release notes for 6.10.17.152 list CETCOMPAT changes and X870/X870E support and flag a set of known issues that include uninstall-log quirks on non-English OSes. Those release notes are the authoritative record for what AMD claimed in that particular build.
• The 7.06.02.123 package and other 7.xx builds are distributed via AMD and mirrored outlets; their notes indicate additional CETCOMPAT entries and targeted fixes, but they also introduced an installer behavior where installing a 7.xx installer could block reinstalling older 6.xx packages without manual cleanup. That behavior is repeated in community threads and mirrored distribution notes.

---

Critical analysis — strengths and risks​

Strengths​

• Security-first changes: Adding CETCOMPAT entries to chipset drivers is a meaningful improvement for mitigations available in Windows. For defenders and enterprises, driver-level alignment with OS mitigations reduces friction when adopting security baselines.
• Broad platform coverage: AMD continues to support a wide range of Ryzen generations, ensuring AM4/AM5 users spanning several CPU families get updated management drivers. That helps keep older but still-popular devices manageable with current OS features.
• Prompt firmware/driver alignment: Pushing RAID and chipset updates alongside Windows feature updates (e.g., Windows 11 24H2 compatibility) is standard good practice for platform vendors, enabling customers to test and validate earlier in their update cycles.

Risks and downsides​

• Installer non-reversibility and rollback friction: The reported inability to downgrade from 7.xx to 6.xx without manual cleanup or OS reinstallation is a significant operational risk for testers and help desks. Environments that rely on the ability to roll back quickly should treat these packages as a one-way move until AMD clarifies or provides downgrade tools.
• RAID/stack sensitivity: RAID and storage stacks are inherently risky to change in production. Combined chipset+RAID updates should be scheduled with standard data-center maintenance windows and backups. Forum posts reiterate that administrators should test in a controlled environment first.
• Mixed field reports on performance and stability: While many users report success, others report regressions or installation anomalies that require manual troubleshooting (BIOS updates, firmware patches, or clean driver installs). That variability means the update is not a “one-size-fits-all” safe patch for every system.
• User confusion from uninstall logs and messages: The frequently-seen “uninstall summary” failing message on non-English OS installations, while cosmetic in many cases, undermines trust and drives unnecessary support tickets. AMD’s release notes acknowledge this, but the messaging gap remains a practical problem.

---

Practical guidance — how to approach this update​

If you manage machines with AMD Ryzen processors or plan to update your personal PC, follow these concrete steps to reduce risk:

• Inventory: Record current chipset driver version, BIOS/UEFI version, RAID firmware, and Windows build (exact build number). On Windows, check Control Panel > Programs & Features for installed AMD-signed packages and use Device Manager to confirm driver versions for PSP/PPKG components. For enterprise fleets, use your management tools to query driver package versions.
• Backup: Before touching RAID or system-critical boxes, take full backups and validate restore. Snapshot VMs where possible. RAID arrays should be validated with fresh backups and spare time window for fallback.
• Read release notes: Always open the AMD release notes for the exact package you plan to install and confirm whether known issues or installer behaviors (like downgrade blocking) apply to your configuration. AMD’s release notes for 6.10.17.152 list CETCOMPAT additions and known issues; other packages have their own caveats.
• Test lab: Deploy the update to a small representative test set first — include desktop builds, gaming rigs, and at least one system with RAID. Validate boot, performance-sensitive workloads, and any third-party software that requires low-level access (hypervisors, monitoring agents, storage utilities).
• BIOS + firmware parity: Ensure the system firmware (UEFI/BIOS) and storage controller firmware are current. Many driver-related problems are resolved by bringing firmware and BIOS into parity with driver expectations. If your board vendor released a UEFI update for an X870/X870E board, install that first.
• Clean install if troubleshooting: If things go wrong, perform a clean driver uninstall via the AMD installer/uninstaller and consider using the AMD Cleanup Utility (or vendor-recommended cleanup) before reinstalling the newer package. If you must revert to an older package, be aware some 7.xx installers prevent reinstalling older 6.xx packages without extra steps; plan accordingly.
• Enterprise rollout strategy: Use phased rollout (pilot → pilot2 → broader) and instrument telemetry (driver version, crash/timeout events) to watch for regressions. For devices under production SLA, schedule updates during maintenance windows with a recovery plan.

---

Step-by-step: safe local update checklist (concise)​

• Note current Windows build and installed AMD driver package versions.
• Create a full system backup or system image.
• Update motherboard BIOS/UEFI to vendor-recommended level.
• Reboot and confirm stable system state.
• Download the AMD package matching your Windows bitness and board family.
• Run the installer as Administrator and select only the components you need (avoid RAID updates on a production machine unless required).
• Reboot and validate stability and performance.
• If you see uninstall-summary “fail” on non-English OS, check Device Manager and driver versions — don’t assume failure without verification.

---

Enterprise considerations​

• For managed fleets, treat chipset driver updates like firmware: they should go through staging, testing, and approval gates. The potential for installer-driven downgrade blocking is especially important for help desks that rely on rapid rollbacks. Consider testing vendor-supplied driver packages (OEM-customized versions) instead of the generic AMD bundle if that’s what your vendor supports.
• If your environment uses image-based provisioning, update and validate your gold image with the new chipset package before broad deployment. Include your endpoint security stack, hypervisor agents, and monitoring agents in your validation matrix because low-level driver behavior can interact with endpoint software in unexpected ways.

---

Unverifiable or ambiguous points — cautionary language​

• Some third-party mirrors and vendor download pages list slightly different build numbers or WHQL tag states (e.g., unofficial 7.xx builds in vendor portals). If you see a build number on a mirror that differs from AMD’s public release notes, treat the mirror as a secondary source and verify against AMD’s official release-note page for that version. Where community posts claim “this driver did X on my machine,” those are configuration-specific anecdotes and cannot be generalized without controlled testing.
• Reports of outright data loss tied to chipset updates are rare in public forums; however, because RAID and storage drivers are involved in some packages, any claim of data corruption deserves careful forensic investigation (and should be reported to AMD and the motherboard vendor). Until vendors publish root causes, treat such claims as anecdotal and test conservatively.

---

Final verdict — practical recommendations​

• For enthusiasts and home users who are comfortable troubleshooting and who run single-drive desktop systems, installing the latest AMD chipset package can yield improved security (CET flags) and platform features — but back up first and test briefly after installation. Consider delaying RAID component updates until you've validated them in a lab or until AMD/OEM clarifies any RAID-specific concerns.
• For IT administrators and production systems, treat these packages as Infrastructure changes: pilot, test, and schedule. The added CET compatibility is valuable, but the installer behaviors and RAID sensitivity mean the update should be deployed conservatively. If your organization runs standardized images or tight compliance policies, coordinate with your OEMs for vendor-verified packages.
• For help desks: prepare rollback instructions and make staff aware of the known uninstall-log cosmetic issues and potential downgrade complications after installing 7.xx installers. Provide a documented recovery path (BIOS recovery, offline driver replacement, or image restore) so technicians can act quickly if a pilot machine misbehaves.

---

Conclusion​

AMD’s recent chipset-driver wave is a mixed bag: it brings real security hardening and necessary platform support (notably CET compatibility and new chipset entries) while also changing installer behavior and exposing edge-case risks around rollback and RAID stacks. These are not reasons to panic, but they are reasons to be deliberate.
If you run mission-critical systems, treat the update as you would a firmware change: inventory, backup, test, and phase. If you are an enthusiast with a single desktop and a reliable backup, the security improvements are worth exploring — but keep clean restore points and vendor notes handy. The devil with driver packages always hides in combinations of OS build, BIOS version, and third-party software; the best defense is methodical testing, not rush installing.
(Verified against AMD’s official release notes and multiple independent community and mirror reports; read the specific release notes for the exact package you plan to install and follow the rollout guidance above.)

---

Source: Neowin AMD releases new Windows 11/10 chipset driver for Ryzen 9000, 7000, 5000, 3000, and more