AMD’s comments — surfaced in a recent interview — suggest the company is working with Microsoft to ensure
Ryzen processors will be treated favorably as Windows hard‑requirements evolve, but the practical implications for OEMs, system builders and end users hinge on nuanced distinctions between Microsoft’s OEM‑facing processor lists, driver baselines, and marketing claims from silicon vendors.
Background / Overview
Microsoft publishes explicit processor lists that OEMs must use when building
new Windows 11 devices; those lists are updated with each Windows feature release and effectively set the baseline for what Microsoft will certify in factory‑shipped systems. The Windows 11, version 24H2 processor lists published by Microsoft are the clearest example of this policy in action: they spell out which CPU models meet the minimum design principles (security, reliability, driver model) for new devices. That OEM‑targeted list is not the same thing as a consumer compatibility guarantee. Microsoft has repeatedly stressed that changes to the OEM lists do not erase support for existing devices — they inform OEMs which CPUs they should use when building new PCs to receive Windows 11 certifications and logos. Multiple reporting outlets have explained this distinction after the 24H2 lists were published, which caused confusion when older Intel mobile and desktop families were not included for new systems. Into this space comes AMD’s messaging: executives in the company told interviewers they’ve been collaborating with Microsoft on the next major Windows cadence to ensure
modern Ryzen families — including parts with on‑device AI — align with Microsoft’s evolving requirements, and that many Ryzen systems already meet Windows 11 eligibility. Those comments were framed as forward‑looking reassurance to OEM partners and customers while also positioning AMD silicon as the natural target for “AI‑aware” Windows experiences.
What AMD actually said (and what the Neowin interview reported)
The interview in plain terms
- AMD told the interviewer that it expects many Ryzen platforms to be compatible with upcoming Windows requirements and that AMD is working with Microsoft and OEM partners to minimize friction for customers.
- AMD emphasized that the most pressing compatibility issues for customers are not CPU microarchitecture per se, but the ancillary requirements that prevent older PCs from being eligible for Windows 11 — chiefly TPM 2.0, Secure Boot configuration, and modern driver models.
- AMD also highlighted its Ryzen AI and Zen 5 families as being a strategic match for Windows features that rely on local NPU/AI acceleration, and reiterated marketing metrics such as NPU TOPS figures for Ryzen AI SKUs while urging OEMs to adopt silicon with integrated NPUs to unlock future Copilot+ features.
How to read the tone
AMD’s comments are pragmatic and commercially aligned: they reassure customers that AMD silicon will remain usable and competitive in Windows‑centric devices, while simultaneously nudging OEMs and buyers toward newer Ryzen SKUs that include on‑device AI blocks. That is both a technical roadmap and a marketing posture — credible as far as co‑engineering between CPU vendors and OS partners goes, but not a Microsoft certification or an unconditional guarantee for every Ryzen SKU.
Microsoft’s position: OEM lists, consumer support, and semantics
OEM lists vs. consumer support
Microsoft’s “supported processors” documentation is explicitly
OEM‑facing: it tells manufacturers which CPUs are appropriate for new Windows 11 devices and which device drivers must meet modern DCH/DCH‑compliant design principles. The document language repeatedly clarifies that changes to these lists are
not intended to change the support status of existing devices. That is the core reason many media outlets called the 24H2 processor lists confusing: a processor’s absence means OEMs shouldn’t use it for
new PCs seeking Windows 11 certification, not that Windows 11 will stop working on older machines immediately.
Practical consequences of the OEM lists
- New PCs built after the publication of a given processor list may be ineligible for Windows 11 certification if they use processors omitted from that edition’s OEM guidance.
- Existing PCs generally remain supported for updates and patches until Microsoft’s lifecycle policy says otherwise — Microsoft asserts this explicitly in its guidance.
- The lists are updated periodically; omission from one list does not mean permanent exclusion, and newly released processors may be added in subsequent list updates.
Independent verification: what reporting and Microsoft docs show
Multiple independent technology outlets and Microsoft’s own documentation confirm the split between OEM guidance and existing device support, and they document the tangible outcomes of the 24H2 (and later) list changes.
- Microsoft’s processor lists for Windows 11 24H2 are official and publicly accessible; they show which CPU families and models Microsoft expects OEMs to use for new validated devices. These lists were updated in early 2025.
- Tom’s Hardware and Born’s Tech documented which Intel generations were left out of the OEM lists for 24H2 and noted that AMD’s Ryzen 8000 family was added, while some Ryzen 9000 and specialized AI parts were missing from the published roster. That independent reporting shows the lists matter in practice and explains why vendors and media reacted strongly.
- WindowsLatest and Microsoft‑facing coverage reached back to Microsoft for clarity and reported Microsoft’s explicit position: the OEM lists don’t change consumer support or update eligibility for existing hardware. That clarification reduced some of the initial alarm in the market.
These multiple viewpoints confirm the interview’s tenor — AMD is collaborating with Microsoft — while also underlining why messaging from vendors, Microsoft’s technical documents, and media reports can be read differently by different audiences.
Technical realities: drivers, device drivers baseline and vendor practices
Driver model and “modern drivers”
Microsoft now expects new OEM devices to ship with modern DCH drivers and to participate in the Windows Hardware Compatibility Program; that effectively raises the bar for driver packaging and distribution. Vendors are increasingly packaging drivers and support for Windows 11 as the baseline, and some driver releases have shifted their recommended OS baseline to Windows 11 only. That trend was visible in some AMD driver shipping notes in 2025.
This matters because:
- Even if a CPU is theoretically capable of running a future Windows build, lack of modern OEM drivers for associated platform components (chipset, integrated GPU, NPU) can make certified installation or feature support problematic.
- Vendors can choose to ship legacy drivers for older OS builds, but sustainable QA and support investment is usually focused on modern driver models and the most widely used OS baseline.
The NPU and AI angle
AMD’s push for Ryzen AI and silicon with integrated NPUs is a response to Microsoft’s growing emphasis on device‑level AI features (Copilot+, local inference). Vendors that want
guaranteed access to those features will need not just CPU IPC, but also a validated AI runtime, firmware support, and drivers that integrate with Windows ML and other Windows AI stacks. AMD’s claims about NPU throughput and capability are vendor data points that need to be interpreted in the context of software maturity and real‑world model characteristics.
What’s strong about AMD’s message — and what to be cautious about
Notable strengths
- Proactive co‑engineering: AMD is signaling real coordination with Microsoft and OEMs to make sure its newer chips get the attention they need to enable future Windows features. That reduces the risk of feature mismatch when Windows adds AI features that rely on on‑device accelerators.
- Clear product positioning: AMD is positioning Ryzen AI and Zen 5 CPUs as attractive platforms for AI‑enhanced Windows experiences; that improves OEM clarity when planning device SKUs and messaging to customers.
- Practical advice on upgrade drivers: The company reiterated the importance of TPM, Secure Boot and updated firmware/driver stacks — the components that most often block a clean Windows 11 upgrade.
Risks and caveats
- Marketing vs. certification: An AMD executive’s assurance is not a Microsoft certification. The official status of a given Ryzen SKU for new Windows device certifications remains the purview of Microsoft’s published lists. Readers should treat vendor assurances as helpful context but not as a substitute for Microsoft’s official documentation.
- Omissions in official lists: The OEM lists for 24H2 omitted some high‑profile AMD parts (for example, certain Ryzen 9000 and AI Max+ SKUs were not explicitly listed when Microsoft published the lists), which creates gaps between marketing statements and certification status. Those omissions can be due to timing, naming conventions, or certification cadence — but they are real and meaningful for OEM planning.
- Driver and software dependencies: Real‑world Windows experiences depend on chipset firmware, DCH drivers, and OEM BIOS/UEFI updates — not just the CPU. If vendors don’t ship modern drivers for older Windows releases, users may be compelled to upgrade the OS baseline sooner than they expected.
- Messaging confusion for consumers: The difference between “supported for new OEM devices” and “supported on existing devices” has repeatedly caused consumer confusion; AMD’s reassurances may calm OEMs but won’t necessarily resolve consumer uncertainty.
Practical guidance for OEMs, system builders and consumers
For OEMs and system integrators
- Treat Microsoft’s supported processor lists as prescriptive for new Windows 11 certified SKUs; validate each SKU against the current Windows documentation.
- If you intend to market devices with on‑device AI features (Copilot+, local inference), prioritize silicon with validated NPUs and a proven driver stack from the silicon vendor.
- Maintain a clear driver baseline: package DCH drivers and ensure your imaging process includes updated UEFI/BIOS that enable TPM and Secure Boot by default.
For system builders and enthusiasts
- Before buying a new machine, consult both Microsoft’s current processor lists and the OEM’s hardware support statements. The former tells you what OEMs should be using; the latter tells you what you’ll actually get installed and supported.
- If your machine is older and you rely on it staying on Windows 11, check whether the CPU and platform components have vendor‑supplied modern drivers and OEM firmware updates that enable TPM and Secure Boot properly.
For consumers still on Windows 10
- Windows 10 reached end of mainstream support on Microsoft’s lifecycle timeline; Microsoft offered Extended Security Updates and other transition options around October 14, 2025, and third‑party reporting covered enrollment specifics and caveats. If staying on Windows 10 is necessary, explore ESU options and understand their limitations — they usually cover security patches and not feature updates.
Deeper analysis: strategic implications and long‑term outlook
Market consequences
- Microsoft’s OEM lists create a tight coupling between the Windows certification ecosystem and vendor product cycles. When Microsoft elevates the baseline (e.g., expecting DCH drivers and modern security primitives), it accelerates OEM refresh cycles. That tends to favor silicon vendors who can rapidly certify new SKUs and work closely with MS — a competitive advantage AMD is explicitly trying to exploit via public collaboration claims.
- Conversely, slower or smaller OEMs that want to ship budget devices might lean on older CPU generations and then be limited in receiving the newest Windows certification branding, which can have marketing consequences.
Environmental and sustainability dimension
- Any policy that nudges customers toward buying new hardware raises valid questions about e‑waste. AMD’s public stance, as reported in its executive comments, emphasizes designing long‑lived parts, encouraging OEM trade‑in programs, and prioritizing energy efficiency — useful steps, but they do not eliminate the inherent churn created when OS baselines shift. Readers and procurement teams should weigh this when planning refresh cycles.
Technical divergence risks
- The divergence between vendor APIs, driver packaging and Microsoft’s expectations can create two speed lanes: “modern” Windows devices that get the feature‑rich, AI‑accelerated experience, and older but usable devices that may lack the integrated experience. That divergence can fragment the ecosystem from a developer and support standpoint unless Microsoft and vendors sustain strong backward‑compatibility tooling.
How to verify Ryzen compatibility for your exact system (step‑by‑step)
- Identify your exact CPU model (Windows System Information, CPU‑Z or vendor documentation).
- Check Microsoft’s “Windows 11, version X supported processors” page for the exact model name or family to see if the CPU appears on the OEM list. If it is listed, OEM certification for new devices is established for that SKU.
- Consult your PC manufacturer (or motherboard vendor) for BIOS/UEFI updates that enable TPM 2.0 and Secure Boot and for a vendor‑supplied chipset driver package that is DCH‑compliant.
- Confirm the vendor provides modern DCH drivers for the OS baseline you plan to run (Windows 11 21H2/23H2/24H2 as applicable). If the latest drivers are Windows‑11‑only, expect less QA for older Windows versions.
- If you need long‑term Windows 10 support, investigate Microsoft’s ESU routes and vendor support timelines; the guarantee to continue receiving security updates may require enrollment or a migration plan.
Conclusion — measured optimism, defined steps
AMD’s interview signals sensible, practical collaboration with Microsoft and gives OEMs and buyers some reassurance that Ryzen families — particularly those designed with on‑device AI in mind — are intended to remain relevant for upcoming Windows feature releases. That message is technically credible: platform vendors and OS teams commonly co‑engineer optimizations and driver support to enable new OS features.
However, the real world is governed by three separate but overlapping authorities: (1) Microsoft’s formal OEM processor lists and driver requirements, (2) OEMs’ shipping firmware/driver support, and (3) silicon vendors’ marketing and technical claims. Buyers and IT planners should treat AMD’s statements as constructive and directional, but verify compatibility for their
specific SKU against Microsoft’s published lists and their OEM’s support matrices before assuming automatic eligibility for future Windows certifications or AI‑first features. Practical steps are straightforward: confirm the CPU model, check Microsoft’s supported processor documents, get the latest firmware and DCH drivers from your OEM, and if you must remain on Windows 10, plan for ESU or migration. With those checks in place, AMD’s assurances are useful context — and potentially a sign that Ryzen owners will see solid support as Windows continues its AI‑heavy evolution.
Source: Neowin
Interview: AMD hints at Ryzen compatibility with next major Windows version requirements