AMD Ryzen Chipset Update Adds CET Compatibility Across AM4 AM5

AMD has quietly pushed a new universal chipset package that expands official support across its Ryzen generations and — critically for security-minded Windows users — adds explicit CET compatibility for several chipset components, while a follow-up release tightens device support and fixes long-standing stability and RAID issues for AM4/AM5 platforms.

Background​

AMD’s chipset driver packages are not a single driver but a bundled installer that deploys a set of independent, platform-specific drivers (SMBus, GPIO, PCI device, CPI, PSP/PSP/PSP drivers, RAID binaries, and more) tailored to each motherboard and CPU family. These packages affect low-level interactions between Windows and the platform firmware, touching security features, power-management primitives, and IO stacks that influence stability and performance.
The most notable recent package identified in manufacturer notes is Revision 6.10.17.152, which AMD published with a release focus on Windows 10 and Windows 11 compatibility and the addition of CETCOMPAT support for certain components. That same era saw later chipset revisions (for example, 7.04.09.545) appear in AMD’s distribution stream to add device IDs, bug fixes, and incremental compatibility imp00 and earlier families.

---

What changed — the headlines​

• AMD’s chipset package revision 6.10.17.152 formally added CET compatibility flags to a subset of chipset drivers, marking a security-first update for Windows 11 systems that support Control-flow Enforcement Technology. This is important for enabling Microsoft’s CET enforcement on AMD systems where the chipset driver stack may otherwise block or degrade CET operation.
• Subsequent driver packages in th7.02.x and 7.04.09.545) continued to expand chipset device support, include bug fixes (including installation and language-string issues), and update RAID driver binaries for modern Windows 11 branches. These updates explicitly list support for Ryzen 9000, 8000, 7000, and earlier families across AM5 and AM4 ecosystems. ([techpowerup.com](AMD Releases Ryzen Chipset Software 7.04.09.545 and forum threads show a mixed rollout experience: some users report smooth installs and CET recognition, while others encounter partial installs, cosmetic “install summary failed” messages, or driver version reporting discrepancies in Device Manager after running the AMD installer. These are not universal, but they are sufficiently frequent to require attention before wide deployment.

---

Why CET support matters (and what CETCOMPAT is)​

Control-flow Enforcement Technology (CET) is a CPU- and OS-level mitigation introduced by CPU vendors and Microsoft to make certain classes of memory corruption attacks (notably return-oriented programming and other control-flow hijacks) harder to exploit.

• CET requires both CPU/firmware cooperation and compatible low-level platform drivers so that kernel-mode trampolines, exception dispatching, and context switches do not break CET guarantees.
• The CETCOMPAT marker in AMD’s release notes indicates the vendor has marked certain chipset drivers as compatible with CET-aware Windows kernels; this helps Windows enable CET-based protections without being blocked by driver behavior that might violate CET assumptions.

For enterprises and security-conscious users, the addition of CETCOMPAT to AMD’s chipset suite is meaningful: it reduces the risk that low-level platform drivers will inadvertently disable or weaken CET protections, and it paves the way for Microsoft to more broadly enable these mitigations on AMD machines running Windows 11 and Windows 10 (where supported).

---

Supported platforms and compatibility notes​

AMD’s release notes for the 6.x and 7.x packages enumerate chipset and socket support across multiple product families. Key takeaways:

• Formal support now covers the AM5 ecosystem (Ryzen 7000 and Ryzen 9000 families) and extends back to AM4 lines where appropriate, including widely used chipsets such as X670/X670E, B650/B650E, X570, and others. Enterprise-grade and high-end workstation chipsets (WRX90/TRX50) are support matrix.
• RAID driver updates were published in parallel (versions in the 9.x series), and AMD explicitly called out Windows 11 compatibility, including newer feature updates/enablement scenarios. If you use onboard RAID or software-assisted RAID, the updated RAID binaries are a reason to consider the new package.
• AMD’s installer is a packaging layer that allows selection of only the drivers you need; many motherboard vendors still publish OEM-wrapped versions on their support pages, and some users prefer vendor packages to AMD’s standalone bundle for maximum board-specific compatibility.

---

What to expect during installation​

When you run the AMD Ryzen Chipset installer you’ll see an organized selection UI listing components such as:

• AMD Interface)
• AMD SMBus Driver
• AMD GPIO Driver
• AMD PCI Device Driver
• AMD PSP / AMD Secure Processor drivers
• RAID driver binary (where applicable)
• Optional power plans and platform utilities

The installer writes an installation summary text file. A recurring community observation from the 6.10.17.152 rollout: some users see the installer report a cosmetic “failed” line in the uninstall/installation summary even though the drivers actually installed and devices show updated versions. That oddity seems primarily cosmetic but is worth checking in the Device Manager after any install.
Common installation pitfalls to be aware of:

• Non-English Windows localizations can show mixed-language driver names in the summary or UI. AMD has acknowledged this in release notes as a cosmetic bug.
• The AMD Installer or bundled AMD Manager may not always reflect the same installed revision that Device Manager reports — users have reported the UI offering a newer revision that fails to materialize after installation, likely due to package-layering or leftover older INF entries.
• Some RAID and device-id additions require a firmware (UEFI/BIOS) update on the motherboard to be fully recognized; always check your board manufacturer’s advisories if you rely on vendor RAID.

---

Step-by-step: recommended upgrade path (practical install guide)​

• Identify your motherboard model and BIOS/UEFI revision. Recorsion and driver versions (Device Manager → view driver details for key components).
• Visit your motherboard vendor’s support page and compare the chipset package listed there to AMD’s standalone package. Use the vendor package if it explicitly bundles vendor-specific INF or firmware patches for that board.
• If using AMD’s standalone package: download the proper revision for your OS (Windows 10 or Windows 11) and extract/install choosing only the drivers you require (for many users this will exclude RAID if unused).
• Reboot and verify Device Manager driver versions. Check installation summary logs for errors but prioritize Device Manager and driver file versions as the authoritative state.
• If something fails or device versions are inconsistent, obtain the driver package’s MSI from the temporary installer folder and try manual install of the specific INF that failed. If that still fails, rollback using Windows System Restroll-back and open a vendor support ticket.

---

Benefits — what users stand to gain​

• Improved security posture: CETCOMPAT means fewer platform-level barriers when enabling Windows CET-based protections. For enterprise defenders and users running hardened policies, this is a clear gain.
• Wider device support: newer revisions add device IDs and explicit compatibility for Ryzen 9000/7000 series, reducing the need for unofficial drivers andte or OEM tools can identify devices correctly.
• Stability and RAID fixes: updated RAID binaries and bug fixes in the 7.x line address known causes of BSODs and RAID init failures on some builds, improving reliability for storage-heavy users.
• Cleaner vendor matrix: AMD’s iterative releases bring the public support matrix up to date so system builders can better plan OS builds, driver deployment, and security baselines.

---

Risks and limitations — where to be cautious​

• Installer inconsistencies and cosmetic “fail” messages: A subset of installs report a summary failure even when the devices update. This can be confusing and may hide real failures for less technical users; confirm results in Device Manager.
• Edge cases with OEM-packaged boards: Vendor-wrapped packages sometimes include board-specific INF changes; using AMD’s generic package on a heavily customized OEM board can produce unexpected behavior. Prefer vendor packages for laptops and OEM desktops.
• Rollback complexity: If a low-level driver interacts badly with a particular BIOS revision, rolling back can be more cumbersome than a typical driver rollback. Keep current backups, create a restore point before installing, and ensure you have a fallback method to access the system (safe mode or recovery USB).
• Windows version interactions: Microsoft’s CET and mitigation behaviors are evolving across Windows 10 and Windows 11 feature updates; AMD’s CETCOMPAT flags reduce friction, but full CET-based protection still depends on the OS build and other kernel-mode drivers. Administrators should validate on representative systems before mass rollout.

---

Real-world reports — community feedback and troubleshooting patterns​

Community threads and forum posts provide a live lens into deployment realities:

• Some users report the new drivers resolve previously encountered BSODs and RAID initialization problems after Windows feature updates; for these users, the update was stabilizing.
• Other users saw confusion when the AMD Installer advertised a new revision but Device Manager still displayed an older sub-driver — this typically results from older INF entries or the need for a manual uninstall of previous chipset packages before reapplying the new one.
• Language-string issues and cosmetic uninstall summary anomalies have been repeatedly called out; AMD has acknowledged some of these as known issues in release notes. These are largely cosmetic but diminish user confidence and complicate support workflows.

---

Enterprise guidance — how to approach deployment at scale​

• Create a test matrix: include representative hardware (AM5/AM4 boards, differing BIOS versions, RAID vs. non-RAID systems).
• Validate security telemetry: measure CET enablement and any changes to mitigation status before and after the chipset update.
• Stage rollout: deploy to non-critical systems first, then escalate to broader populations after 48–72 hours of monitoring.
• Maintain vendor fallback: ensure that vendor-specific drivers are available in your management catalog (SCCM/Intune/WSUS) to support rollback if vendor builds are preferred.
• Document known cosmetic quirks (install summary messages, mixed-language strings) so frontline support doesn’t misinterpret benign logs as failures.

---

Troubleshooting quick reference​

• fails:
• Reboot and disable any third-party security software temporarily.
• Run the installer as Administrator.
• If sections fail, extract the MSI from the package and install INF-by-INF in Device Manager.
• Device Manager shows old versions:
• Uet driver package via Apps & Features, reboot, then run a clean install.
• Use vendor-provided driver packages if the generic installer doesn’t update vendor-customized INF entries.
• RAID issues after update:
• Check for a firmware/UEFI update for the motherboard.
• Verify RAID driver binaries included with the package and match to the RAID version recommended by the OEM.

---

Critical analysis — strengths, oversights, and what this rollout signals​

Strengths

• AMD is addressing a clear security vector by marking chipset drivers as CET-compatible. This shows coordination with Microsoft’s mitigation roadmap and benefits users seeking stronger control-flow protections. The release also brings wider chipset coverage for the company’s newest Ryproves platform readiness for Windows feature updates.

Oversights and friction points

• The installer’s cosmetic failures, mixed-language driver name behavior, and inconsistent reporting between the AMD Manager UI and Device Manager reveal a packaging maturity gap. While the functional drivers are often updated correctly, these UX issues can increase help-desk workload and risk misdiagnosis.
• Distribution fragmentation remains a challenge. OEM-packaged drivers, vendor INF customizations, and AMD’s generic bundle may not always align; enterprises and enthusiasts must choose carefully between vendor-tested packages and AMD’s upstream releases.

What it signals

• The addition of CETCOMPAT suggests AMD sees CET as lasting OS-level mitigation and is aligning its platform software accordingly. That’s a positive sign for long-term security integration — but it places responsibility on system administrators to validate CET activation across diverse device fleets before assuming protective parity with Intel-based systems.

---

Recommendations — practical takeaways for users and IT pros​

• Individual users (enthusiasts and home builders):
• If you care about CET and run Windows 11, consider installing the updated chipset package after backing up and creating a system restore point. Verify driver versions in Device Manager and keep your motherboard BIOS current.
• If you’re uncomfortable with low-level upgrades, stick with the chipset driver provided on your motherboard maker’s support page — those packages are often tested against the vendor’s BIOS and board firmware.
• IT administrators (small business to enterprise):
• Test the new packages in a lab, validate CET enablement telemetry, and stage the rollout. Include rollback plans and vendor fallbacks in your update playbook.
• Document cosmetic installer anomalies for helpdesk staff so that benign summary messages don’t trigger unnecessary escalations.
• Enthusiast power users:
• If you run RAID or custom storage setups, check the RAID driver version in the new package and match it to your board vendor recommendations. Consider manual deployment of the RAID binary if you use pre-boot RAID frequently.

---

Final verdict​

AMD’s recent chipset revisions represent a pragmatic and security-forward step: marking drivers as CET-compatible and expanding device support for Ryzen 9000 and earlier processors brings measurable benefit to Windows 10/11 users who prioritize mitigations and system robustness. However, the rollout is not flawless — installer UX quirks and packaging inconsistencies mean the update is best handled with a disciplined rollout and verification process. For most users who keep vendor BIOS and drivers reasonably current, the update is a net positive; for environments that require absolute stability and predictability, take a staged approach and prefer OEM-tested distributions where available.
In short: this is the kind of platform-level housekeeping that matters — not flashy, but essential. Apply it carefully, verify thoroughly, and you’ll gain broader CET alignment and improved chipset support across AMD’s Ryzen families.

---

Source: Windows Report https://windowsreport.com/amd-rolls...pset-drivers-for-ryzen-9000-and-older-series/

 

[ChatGPT]

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