MHR (Minimum Hardware Requirements) – Everything Microsoft Authorized Refurbisher Partners Need to Know 

Microsoft continues to strengthen compliance controls for devices refurbished under the Microsoft Authorized Refurbisher (MAR) program. One of the most important aspects of these controls is the Minimum Hardware Requirements (MHR) for Windows. 

Meeting the MHR is not simply a technical recommendation—it is a licensing requirement of the MAR program. Microsoft regularly reviews the reports submitted by partners and may apply Default Charges when non-compliance is identified. 

What are the Minimum Hardware Requirements? 

The Minimum Hardware Requirements define the minimum hardware configuration required for a specific version of Windows. 

These requirements include, among others: 

• supported processor, 

• system memory (RAM), 

• storage capacity, 

• UEFI firmware, 

• TPM 2.0, 

• other technical requirements defined by Microsoft. 

Microsoft may update these requirements as new Windows releases become available. 

How does Microsoft verify compliance? 

Every device prepared under the MAR program is reported to Microsoft through a Computer Build Report (CBR). 

Microsoft regularly validates compliance using information contained in the CBR, including: 

• processor model and generation, 

• TPM configuration, 

• Windows version, 

• hardware configuration, 

• Hardware Hash accuracy, 

• reporting timeliness. 

If a device does not meet the applicable requirements, it may be identified as non-compliant in Microsoft’s compliance reports. 

Windows 11 version 25H2 is mandatory from April 1, 2026 

This is one of the most important recent changes announced by Microsoft. 

According to Microsoft’s communication published on May 8, 2026: 

• through March 31, 2026, Windows 11 Home and Pro version 24H2 was considered compliant; 

• starting April 1, 2026, Windows 11 Home and Pro version 25H2 is required for all applicable Customer Systems. 

Microsoft’s policy requires partners to deploy the latest Windows Home and Pro release within 180 days of its Release to Manufacturing (RTM). 

Deploying an older Windows release after that period may result in non-compliance. 

Important: Any PKID associated with a device running an outdated Windows release may be identified in Microsoft’s compliance reports and may be subject to Default Charges. 

TPM 2.0 and Secure Boot 

An enabled TPM 2.0 is mandatory for Windows devices distributed through the MAR program. 

Having TPM hardware alone is not sufficient. TPM must be enabled and properly configured in the BIOS/UEFI. 

Secure Boot must also be enabled to meet Microsoft’s security requirements. 

Supported processors 

Microsoft validates whether the processor is supported for the installed Windows version. 

Deploying Windows on unsupported processors may result in the device being reported as non-compliant. 

OA3Tool 

Partners must use a current version of OA3Tool to generate the Hardware Hash. 

The minimum compliant version is OA3Tool 10.0.25398 or later. Microsoft also accepts OA3Tool 24H2 (build 26100). 

Using older OA3Tool versions may result in compliance findings. 

Computer Build Report (CBR) 

Every device must have a valid Computer Build Report (CBR). 

The CBR must be submitted: 

• within 24 hours after the device is prepared, or 

• at least 4 hours before the device is made available to the end user. 

Reports must contain complete and accurate hardware information. 

Common causes of non-compliance 

Microsoft may identify non-compliance for reasons including: 

• Windows installed on hardware that does not meet MHR, 

• unsupported processor, 

• TPM 2.0 disabled, 

• deployment of an outdated Windows version, 

• outdated OA3Tool, 

• missing CBR, 

• late CBR submission, 

• incomplete or inaccurate CBR data, 

• Windows activation before CBR submission. 

Default Charges 

Compliance issues identified during Microsoft’s validation process may result in Default Charges. 

Effective January 1, 2024, any OA3 product key activated before Microsoft receives the corresponding CBR—or with a CBR submitted after activation—may be subject to Default Charges under the licensing terms. 

Microsoft continues to require that the CBR be submitted before Windows activation. 

Copilot+ PCs and Enhanced Sign-in Security (ESS) 

Microsoft has also introduced additional requirements for Copilot+ PCs. 

Effective March 1, 2026, Enhanced Sign-in Security (ESS) must be enabled on all Copilot+ PCs before distribution. 

Devices without ESS enabled may be subject to Default Charges. 

Best practices 

Before deploying Windows, verify that: 

• the processor is supported, 

• TPM 2.0 is enabled, 

• Secure Boot is enabled, 

• BIOS/UEFI is up to date, 

• Windows 11 version 25H2 is being deployed, 

• the latest OA3Tool version is used, 

• the CBR is generated correctly, 

• the CBR is submitted before Windows activation. 

How XDE helps 

XDE (eXpress Deployment Environment) automates device preparation while supporting compliance with Microsoft MAR requirements. 

It helps partners by: 

• deploying up-to-date Windows images, 

• automating CBR reporting, 

• integrating with MAR licensing, 

• reducing manual configuration errors, 

• standardizing the refurbishment process. 

This significantly reduces or eliminates (depending on settings) the risk of compliance issues and Default Charges. 

Summary 

Minimum Hardware Requirements have become one of the most important compliance elements of the Microsoft Authorized Refurbisher program. Microsoft validates not only the hardware configuration of refurbished devices but also the Windows release, CBR submission timing, Hardware Hash quality, and overall compliance with current program requirements. 

Keeping deployment environments up to date, using the latest Windows release and OA3Tool, and submitting CBRs on time are essential for maintaining compliance and avoiding Default Charges.