AMD has quietly rolled out a new universal chipset package — revision 8.01.20.513 — that updates dozens of small but important platform drivers, adds explicit Windows 11 25H2 support for multiple components, and expands official compatibility for AMD’s growing lineup (including Ryzen AI 300 Series and Threadripper families). The package appeared on AMD’s official driver pages with a release date of February 16, 2026, and AMD’s published release notes enumerate per-driver version bumps, bug fixes, and a handful of known-installation caveats that users and system builders should read before updating. (amd.com) (amd.com)
AMD distributes Ryzen chipset support as a single installer that bundles many discrete kernel-mode and user-mode drivers — UART, GPIO, PSP, PMF/PMF-series power management drivers, USB4, and platform-specific provisioning drivers among others. That bundle is updated frequently to add OS validation, close bugs, and support new processor/platform families. Historically, AMD has used this installer to roll out Windows feature-update compatibility (for example when Windows 11 24H2 and prior minor releases arrived), and chipset packaging changes often include both small fixes and changes that affect system stability during upgrades. The company’s official download pages now list revision 8.01.20.513 (63 MB) for multiple chipset pages (A520, B450 and others) with the Feb 16, 2026 timestamp. (amd.com)
AMD’s release notes associated with the chipset family also include a clearly-stated headline: Windows® 11 25H2 OS support added — and then break down changes on a per-driver basis, including specific drivers that show explicit 25H2 support entries. The release notes document several known issues (notably: inability to reinstall older 6.x installers after a 7.x+ install; occasional PPKG installation failures; and some non-English OS text quirks) that you should treat as genuine caveats when planning upgrades. (amd.com)
A separate vendor and forum roundup highlights that AMD also published updated RAID drivers and RAIDxpert utilities around the 25H2 timeframe, and those updates carry their own caveats for RAID array migrations and OS installs; if your system uses AMD software RAID, treat updates more cautiously and test thoroughly.
AMD’s chipset driver cadence is a steady drumbeat of fixes, OS validation, and incremental platform enablement. Revision 8.01.20.513 is consistent with that pattern: it smooths the path to Windows 11 25H2 for many AMD platforms, brings explicit support to Ryzen AI 300 Series platform components, and — as always — asks administrators and savvy users to exercise caution when rolling out kernel-level updates at scale. Monitor vendor notes and community feedback during the first few weeks after installation, and document your rollback steps before making any mass updates. (amd.com)
Source: Neowin AMD releases new chipset drivers with Windows 11 25H2 support and more
Background / Overview
AMD distributes Ryzen chipset support as a single installer that bundles many discrete kernel-mode and user-mode drivers — UART, GPIO, PSP, PMF/PMF-series power management drivers, USB4, and platform-specific provisioning drivers among others. That bundle is updated frequently to add OS validation, close bugs, and support new processor/platform families. Historically, AMD has used this installer to roll out Windows feature-update compatibility (for example when Windows 11 24H2 and prior minor releases arrived), and chipset packaging changes often include both small fixes and changes that affect system stability during upgrades. The company’s official download pages now list revision 8.01.20.513 (63 MB) for multiple chipset pages (A520, B450 and others) with the Feb 16, 2026 timestamp. (amd.com)AMD’s release notes associated with the chipset family also include a clearly-stated headline: Windows® 11 25H2 OS support added — and then break down changes on a per-driver basis, including specific drivers that show explicit 25H2 support entries. The release notes document several known issues (notably: inability to reinstall older 6.x installers after a 7.x+ install; occasional PPKG installation failures; and some non-English OS text quirks) that you should treat as genuine caveats when planning upgrades. (amd.com)
What’s new in revision 8.01.20.513 — highlights
The release is not a single-driver overhaul but a broad, incremental update across the chipset package. The most consequential items:- Windows 11 25H2 validation / support — multiple drivers were explicitly marked as validated for Windows 11 25H2 (PMF-6000, PMF-7040, PMF-8000, 3D V-Cache Performance Optimizer, PMF Ryzen AI 300 Series and others). This is the headline AMD is promoting. (amd.com)
- Ryzen AI 300 Series & Ryzen AI MAX entries — the package expands explicit support for AMD’s Ryzen AI 300 Series drivers, adding PMF Ryzen AI 300 Series and PMF Ryzen AI MAX 300 Series driver entries. If you own or manage systems with Ryzen AI silicon, this is material. (amd.com)
- New/updated small drivers — revisions for UART, GPIO, PSP, MicroPEP, SFH, USB4 CM, and more. Several entries are marked as Bug Fixes rather than functional new features — typical of chipset rollups. (amd.com)
- Installer and packaging changes — the installer EULA was updated and AMD updated the embedded InstallShield version, which sometimes affects how setups behave in enterprise imaging or scripted deployments. ([amd.om/en/resources/support-articles/release-notes/RN-RYZEN-CHIPSET-7-11-26-2142.html))
- Known-installation caveats — after installing a 7.x or later AMD Chipset Installer, users cannot directly install a 6.x (or earlier) package unless specific cleanup steps are taken (uninstall latest, delete Qt_Dependencies folder, then install older package). AMD documents this explicitly. (amd.com)
Per-driver callouts (not exhaustive, but important)
- AMD PMF-6000 / PMF-7040 / PMF-8000 series drivers — these power-management family drivers show explicit entries for Windows 11 25H2 support in the release notes. These components are central to power policies and thermal/power telemetry on modern Ryzen platforms. (amd.com)
- AMD 3D V-Cache Performance Optimizer Driver — updated and marked for 25H2 support; relevant to users running X3D/V-Cache parts where platform-level helpers can impact latency and performance heuristics. (amd.com)
- AMD PMF Ryzen AI 300 Series Drivers (1 & 2), and PMF Ryzen AI MAX 300 Series — new entries and updates that signal growing attention to the Ryzen AI stack on Windows. If you’re evaluating Ryzen AI laptops or desktops, these drivers are part of platform enablement. (amd.com)
- AMD USB4 CM Driver — updated with bug fixes listed; USB4 remains a major interface on AM5 laptops and motherboards, so stability here is notable. (amd.com)
- AMS Mailbox / S0i3 Filter — the release notes list these drivers and mark some as bug-fix items; note that some third-party reports have claimed omission or different behavior, which I discuss below under 'Discrepancies & caution.' (amd.com)
Why this matters: compatibility, stability, and platform enablement
- Windows 11 25H2 readiness — vendors typically validate drivers for new Windows feature updates ahead of broad OS availability to avoid mass incompatibilities. AMD’s explicit 25H2 entries mean OEMs and end users who plan to upgrade should see fewer driver-blocker issues if they use the updated chipset package. That matters most for newer hardware (X870/X670 families, B650/B650E, A620, etc.). (amd.com)
- Ryzen AI & platform enablement — as AMD ships more consumer and mobile AI-capable silicon (Ryzen AI 300 Series), chipset drivers that expose power management and platform features to the OS become part of the overall user experience. These updates indicate AMD’s focus on ensuring power-policy and provisioning files play nicely with AI workloads. (amd.com)
- Incremental bug remediation — the bulk of the update is small bug fixes across many kernel drivers. Those won’t be exciting individually but collectively reduce long-tail issues: failing installs, intermittent device drops, or power-state oddities that users sometimes see after Windows updates. (amd.com)
- Installer/packaging friction — the documented issue about not being able to roll a package back to 6.x unless you remove Qt_Dependencies is important for imaging teams and anyone who needs to maintain older drivers. Large deployments should test this behavior carefully in lab images. (amd.com)
Known issues and community reports — what to watch for
AMD’s release notes list a handful of known issues you should consider before installing:- After installing an AMD Chipset Installer version 7.x or later, older 6.x installers will not install unless you uninstall and delete the Qt_Dependencies folder. AMD documents a specific workaround. (amd.com)
- On non-English OS installations, some driver names may show in English; uninstall logs may display incorrect uninstall status on non-English builds. (amd.com)
- Occasionally Ryzen PPKG (power provisioning package) may not install or upgrade automatically; manual intervention could be required. (amd.com)
A separate vendor and forum roundup highlights that AMD also published updated RAID drivers and RAIDxpert utilities around the 25H2 timeframe, and those updates carry their own caveats for RAID array migrations and OS installs; if your system uses AMD software RAID, treat updates more cautiously and test thoroughly.
Discrepancies & cautionary notes
You may encounter conflicting third-party writeups or forum posts that claim certain drivers are omitted from this package (for example, assertions that the AMS Mailbox driver or the S0i3 filter driver were excluded). AMD’s official release notes and the chipset download pages explicitly list AMS Mailbox and S0i3 entries and mark their versions and change status. When vendor documentation and third-party reports disagree, the vendor’s release notes and download manifest should be treated as the definitive record — but also as a reason to test: community-reported behavior can indicate transient packaging or localization issues not captured at the time of publication. In short: trust AMD’s official manifest for what is included, but rely on community QA for how those drivers behave in the wild. (amd.com)Recommended upgrade strategy — practical steps
If you manage or use an AMD system (Ryzen desktop/mobile, Threadripper, Ryzen AI), follow an intentional plan:- Identify your platform — confirm motherboard model, BIOS/UEFI revision, and whether you use factory OEM chipset packages or AMD’s generic installer. OEM-supplied drivers from vendors like ASUS, MSI, Gigabyte, ASRock can sometimes be customized; if you rely on OEM customizations, check the motherboard vendor first. (amd.com)
- Create a recovery point + full backup — always take a full system image or at minimum a restore point and file backup before kernel-mode driver updates. This is non-negotiable for machines you depend on. Do not skip this step.
- Check known issues & read the release notes — AMD lists the Qt_Dependencies rollback caveat and non-English issues; confirm whether your system’s language or deployment pipeline might be affected. (amd.com)
- Install the chipset driver only (standalone) first — if you also expect to update Radeon (Adrenalin) or RAID drivers, do chipset first. This reduces interdependent upgrade risks. If your OEM provides a BIOS/UEFI update that mentions chipset driver alignment, install the BIOS update beforehand where recommended by the vendor. (amd.com)
- Reboot twice if requested — some AMD components, notably RAID and PMF variations, may require sequential reboots for proper activation. The release notes and related RAID advisories mention reboot sequences.
- Validate device manager and event logs — after install and reboot, confirm drivers show expected versions in Device Manager and check the system Event Log for warnings or install-time errors.
- If you need to rollback — use the AMD Chipset uninstaller, then remove the Qt_Dependencies folder in "C:\Program Files (x86)\AMD\Chipset_Software\" if you must revert to a 6.x package (AMD’s published workaround). For OEM images, re-flash your known-good system image if you encounter a seminar system failure. (amd.com)
Enterprise / imaging notes
- For enterprise imaging and SCCM/Intune distribution, extract and test the MSI and its silent installation switches in a lab image first. The change to the installer EULA and InstallShield version could break scripted installs that rely on previous MSI behaviors. (amd.com)
- If you maintain driver baselines across a fleet, avoid adopting 8.01.20.513 immediately in production until you validate imaging rollback procedures — especially given the documented inability to directly install 6.x after a 7.x+ install without cleanup. (amd.com)
OEMs, motherboard vendors, and the distribution path
Practical reality: many users obtain chipset drivers either from motherboard vendor support pages or directly from AMD. OEMs often curate drivers — sometimes lagging behind AMD’s site — because they test platform firmware interactions, bundled utilities, and vendor-specific vendor components (e.g., custom SMBus implementations, vendor power profiles). If you rely on an OEM-managed machine (pre-built or laptop), check the vendor support page first; otherwise AMD’s generic package is usually the fastest route for up-to-date fixes. The AMD download pages show the 8.01.20.513 revision available under chipset downloads for many board families, meaning the official package is published and ready for manual download. (amd.com)Community reaction so far (early signals)
After the Windows 11 25H2 wave began circulating in previews and release channels, AMD and other vendors started pushing validated drivers; community forums and subreddits picked up early reports of unusual behavior tied to 25H2 plus the latest drivers (for example, some OpenGL recognition problems on certain GPU-driver combos under 25H2). These threads are mixed in severity and reproducibility; some users report complete stability while others document intermittent regressions that required DDU clean installs and manual driver reinstalls. These conversations are an early-warning system: they argue for a cautious, staged rollout to production machines rather than immediate mass adoption.Strengths, limitations, and risk assessment
- Strengths
- Official 25H2 validation reduces the risk of a broad compatibility mismatch during OS upgrades.
- Support for modern AMD silicon (Ryzen AI 300 Series and Threadripper families) shows AMD’s continued investment in platform enablement.
- Incremental bug fixes across many components should improve stability for a wide range of end-user scenarios. (amd.com)
- Limitations and risks
- Installer rollback friction: the Qt_Dependencies lock makes downgrading non-trivial and can interfere with imaging workflows if you need to revert drivers. (amd.com)
- Localized UI / non-English quirks: admin-level scripts and logs may misreport driver names or uninstall statuses on non-English OS builds. (amd.com)
- Early-adopter community reports: anecdotal problems after 25H2 adoption (e.g., OpenGL detection) suggest testing before wide deployments.
Verdict and practical recommendation
Revision 8.01.20.513 is a routine but important chipset-rollup from AMD: it’s not a sweeping architectural change, but it provides explicit Windows 11 25H2 support across several platform drivers and brings Ryzen AI platform drivers further into AMD’s validated stack. For power users and IT admins, the sensible path is:- Test the package in a lab image that mirrors production.
- Validate key workflows (imaging, virtualization, RAID arrays, GPU workloads) before rollout.
- Back up and ensure rollback processes are documented — especially the Qt_Dependencies cleanup step if you need to revert to a 6.x installer. (amd.com)
Quick install checklist (summary)
- Confirm motherboard BIOS/UEFI is up to date with vendor-recommended builds.
- Back up your system image or create a restore point.
- Download AMD Chipset Drivers revision 8.01.20.513 from AMD’s chipset download page and read the release notes. (amd.com)
- Install the chipset package (standalone), reboot as required.
- Validate devices in Device Manager and check Event Viewer for unexpected warnings.
- If rollback is necessary, use the AMD uninstaller and follow AMD’s published Qt_Dependencies cleanup steps before installing older packages. (amd.com)
AMD’s chipset driver cadence is a steady drumbeat of fixes, OS validation, and incremental platform enablement. Revision 8.01.20.513 is consistent with that pattern: it smooths the path to Windows 11 25H2 for many AMD platforms, brings explicit support to Ryzen AI 300 Series platform components, and — as always — asks administrators and savvy users to exercise caution when rolling out kernel-level updates at scale. Monitor vendor notes and community feedback during the first few weeks after installation, and document your rollback steps before making any mass updates. (amd.com)
Source: Neowin AMD releases new chipset drivers with Windows 11 25H2 support and more
