{"id":1324,"date":"2026-07-01T19:17:43","date_gmt":"2026-07-01T17:17:43","guid":{"rendered":"https:\/\/mar.netland.pl\/?p=1324"},"modified":"2026-07-01T19:17:44","modified_gmt":"2026-07-01T17:17:44","slug":"mhr-minimum-hardware-requirements-update","status":"publish","type":"post","link":"https:\/\/mar.netland.pl\/en\/licensing\/mhr-minimum-hardware-requirements-update\/","title":{"rendered":"MHR (Minimum Hardware Requirements) &#8211; update"},"content":{"rendered":"\n<p><strong>MHR (Minimum Hardware Requirements) \u2013 Everything Microsoft Authorized&nbsp;Refurbisher&nbsp;Partners Need to Know<\/strong>&nbsp;<\/p>\n\n\n\n<p>Microsoft continues to strengthen compliance controls for devices refurbished under the&nbsp;<strong>Microsoft Authorized&nbsp;Refurbisher&nbsp;(MAR)<\/strong>&nbsp;program. One of the most important aspects of these controls is&nbsp;the&nbsp;<strong>Minimum&nbsp;Hardware Requirements (MHR)<\/strong>&nbsp;for Windows.&nbsp;<\/p>\n\n\n\n<p>Meeting the MHR is not simply a technical&nbsp;recommendation\u2014it is a licensing requirement&nbsp;of&nbsp;the MAR program. Microsoft regularly reviews the reports&nbsp;submitted&nbsp;by partners and may apply&nbsp;<strong>Default Charges<\/strong>&nbsp;when non-compliance is&nbsp;identified.&nbsp;<\/p>\n\n\n\n<p><strong>What are the Minimum Hardware Requirements?<\/strong>&nbsp;<\/p>\n\n\n\n<p>The Minimum Hardware Requirements define the minimum hardware configuration&nbsp;required&nbsp;for a specific version of Windows.&nbsp;<\/p>\n\n\n\n<p>These requirements include, among others:&nbsp;<\/p>\n\n\n\n<ul>\n<li>supported&nbsp;processor,&nbsp;<\/li>\n<\/ul>\n\n\n\n<ul>\n<li>system&nbsp;memory&nbsp;(RAM),&nbsp;<\/li>\n<\/ul>\n\n\n\n<ul>\n<li>storage&nbsp;capacity,&nbsp;<\/li>\n<\/ul>\n\n\n\n<ul>\n<li>UEFI&nbsp;firmware,&nbsp;<\/li>\n<\/ul>\n\n\n\n<ul>\n<li>TPM 2.0,&nbsp;<\/li>\n<\/ul>\n\n\n\n<ul>\n<li><\/li>\n<\/ul>\n\n\n\n<ul>\n<li>other technical requirements defined by Microsoft.&nbsp;<\/li>\n<\/ul>\n\n\n\n<p>Microsoft may update these requirements as new Windows releases become available.&nbsp;<\/p>\n\n\n\n<p><strong>How does Microsoft verify compliance?<\/strong>&nbsp;<\/p>\n\n\n\n<p>Every device prepared under the MAR program is reported to Microsoft through a&nbsp;<strong>Computer Build Report (CBR)<\/strong>.&nbsp;<\/p>\n\n\n\n<p>Microsoft regularly&nbsp;validates&nbsp;compliance using information contained in the CBR, including:&nbsp;<\/p>\n\n\n\n<ul>\n<li>processor&nbsp;model and&nbsp;generation,&nbsp;<\/li>\n<\/ul>\n\n\n\n<ul>\n<li>TPM&nbsp;configuration,&nbsp;<\/li>\n<\/ul>\n\n\n\n<ul><\/ul>\n\n\n\n<ul>\n<li>Windows version,&nbsp;<\/li>\n<\/ul>\n\n\n\n<ul>\n<li>hardware&nbsp;configuration,&nbsp;<\/li>\n<\/ul>\n\n\n\n<ul>\n<li>Hardware&nbsp;Hash&nbsp;accuracy,&nbsp;<\/li>\n<\/ul>\n\n\n\n<ul>\n<li>reporting&nbsp;timeliness.&nbsp;<\/li>\n<\/ul>\n\n\n\n<p>If a device does not meet the applicable requirements, it may be identified as non-compliant in Microsoft&#8217;s compliance reports.&nbsp;<\/p>\n\n\n\n<p><strong>Windows 11 version 25H2 is mandatory from April 1, 2026<\/strong>&nbsp;<\/p>\n\n\n\n<p>This is one of the most important recent changes announced by Microsoft.&nbsp;<\/p>\n\n\n\n<p>According to Microsoft&#8217;s communication published on&nbsp;<strong>May 8, 2026<\/strong>:&nbsp;<\/p>\n\n\n\n<ul>\n<li><strong>through March 31, 2026<\/strong>,&nbsp;<strong>Windows 11 Home and Pro version 24H2<\/strong>&nbsp;was considered compliant;&nbsp;<\/li>\n<\/ul>\n\n\n\n<ul>\n<li><strong>starting&nbsp;April 1, 2026<\/strong>,&nbsp;<strong>Windows 11 Home and Pro version 25H2<\/strong>&nbsp;is&nbsp;required&nbsp;for all applicable Customer Systems.&nbsp;<\/li>\n<\/ul>\n\n\n\n<p>Microsoft&#8217;s policy requires partners to deploy the latest Windows Home and Pro release within&nbsp;<strong>180 days of its Release to Manufacturing (RTM)<\/strong>.&nbsp;<\/p>\n\n\n\n<p>Deploying an older Windows release after that period may result in non-compliance.&nbsp;<\/p>\n\n\n\n<p><strong>Important:<\/strong>&nbsp;Any PKID associated with a device running an outdated Windows release may be&nbsp;identified&nbsp;in Microsoft&#8217;s compliance reports and may be subject to&nbsp;<strong>Default Charges<\/strong>.&nbsp;<\/p>\n\n\n\n<p><strong>TPM 2.0 and Secure Boot<\/strong>&nbsp;<\/p>\n\n\n\n<p>An enabled&nbsp;<strong>TPM 2.0<\/strong>&nbsp;is mandatory for Windows devices distributed through the MAR program.&nbsp;<\/p>\n\n\n\n<p>Having TPM hardware alone is not sufficient. TPM must be enabled and properly configured in the BIOS\/UEFI.&nbsp;<\/p>\n\n\n\n<p>Secure Boot must also be enabled to meet Microsoft&#8217;s security requirements.&nbsp;<\/p>\n\n\n\n<p><strong>Supported processors<\/strong>&nbsp;<\/p>\n\n\n\n<p>Microsoft&nbsp;validates&nbsp;whether the processor is supported for the installed Windows version.&nbsp;<\/p>\n\n\n\n<p>Deploying Windows on unsupported processors may result in the device being reported as non-compliant.&nbsp;<\/p>\n\n\n\n<p><strong>OA3Tool<\/strong>&nbsp;<\/p>\n\n\n\n<p>Partners must use a current version of&nbsp;<strong>OA3Tool<\/strong>&nbsp;to generate the Hardware Hash.&nbsp;<\/p>\n\n\n\n<p>The&nbsp;minimum&nbsp;compliant version is&nbsp;<strong>OA3Tool 10.0.25398<\/strong>&nbsp;or later. Microsoft also accepts&nbsp;<strong>OA3Tool 24H2 (build 26100)<\/strong>.&nbsp;<\/p>\n\n\n\n<p>Using older OA3Tool versions may result in compliance findings.&nbsp;<\/p>\n\n\n\n<p><strong>Computer Build Report (CBR)<\/strong>&nbsp;<\/p>\n\n\n\n<p>Every device must have a valid&nbsp;<strong>Computer Build Report (CBR)<\/strong>.&nbsp;<\/p>\n\n\n\n<p>The CBR must be&nbsp;submitted:&nbsp;<\/p>\n\n\n\n<ul>\n<li>within&nbsp;<strong>24 hours<\/strong>&nbsp;after the device is prepared, or&nbsp;<\/li>\n<\/ul>\n\n\n\n<ul>\n<li>at least&nbsp;<strong>4 hours before<\/strong>&nbsp;the device is made available to the end user.&nbsp;<\/li>\n<\/ul>\n\n\n\n<p>Reports must&nbsp;contain&nbsp;complete and&nbsp;accurate&nbsp;hardware information.&nbsp;<\/p>\n\n\n\n<p><strong>Common causes of non-compliance<\/strong>&nbsp;<\/p>\n\n\n\n<p>Microsoft may&nbsp;identify&nbsp;non-compliance for reasons including:&nbsp;<\/p>\n\n\n\n<ul>\n<li>Windows installed on hardware that does not meet MHR,&nbsp;<\/li>\n<\/ul>\n\n\n\n<ul>\n<li>unsupported&nbsp;processor,&nbsp;<\/li>\n<\/ul>\n\n\n\n<ul>\n<li>TPM 2.0&nbsp;disabled,&nbsp;<\/li>\n<\/ul>\n\n\n\n<ul>\n<li>deployment of an outdated Windows version,&nbsp;<\/li>\n<\/ul>\n\n\n\n<ul>\n<li>outdated&nbsp;OA3Tool,&nbsp;<\/li>\n<\/ul>\n\n\n\n<ul>\n<li>missing CBR,&nbsp;<\/li>\n<\/ul>\n\n\n\n<ul>\n<li>late&nbsp;CBR&nbsp;submission,&nbsp;<\/li>\n<\/ul>\n\n\n\n<ul>\n<li>incomplete or inaccurate CBR data,&nbsp;<\/li>\n<\/ul>\n\n\n\n<ul>\n<li>Windows activation before CBR submission.&nbsp;<\/li>\n<\/ul>\n\n\n\n<p><strong>Default Charges<\/strong>&nbsp;<\/p>\n\n\n\n<p>Compliance issues&nbsp;identified&nbsp;during Microsoft&#8217;s validation process may result in&nbsp;<strong>Default Charges<\/strong>.&nbsp;<\/p>\n\n\n\n<p>Effective&nbsp;<strong>January 1, 2024<\/strong>, any OA3 product key activated before Microsoft receives the corresponding CBR\u2014or with a CBR submitted after activation\u2014may be subject to Default Charges under the licensing terms.&nbsp;<\/p>\n\n\n\n<p>Microsoft continues to require that the CBR be&nbsp;submitted&nbsp;<strong>before Windows activation<\/strong>.&nbsp;<\/p>\n\n\n\n<p><strong>Copilot+ PCs and Enhanced Sign-in Security (ESS)<\/strong>&nbsp;<\/p>\n\n\n\n<p>Microsoft has also introduced&nbsp;additional&nbsp;requirements for&nbsp;<strong>Copilot+ PCs<\/strong>.&nbsp;<\/p>\n\n\n\n<p>Effective&nbsp;<strong>March 1, 2026<\/strong>,&nbsp;<strong>Enhanced Sign-in Security (ESS)<\/strong>&nbsp;must be enabled on all Copilot+ PCs before distribution.&nbsp;<\/p>\n\n\n\n<p>Devices without ESS enabled may be subject to Default Charges.&nbsp;<\/p>\n\n\n\n<p><strong>Best practices<\/strong>&nbsp;<\/p>\n\n\n\n<p>Before deploying Windows, verify that:&nbsp;<\/p>\n\n\n\n<ul>\n<li>the&nbsp;processor&nbsp;is&nbsp;supported,&nbsp;<\/li>\n<\/ul>\n\n\n\n<ul>\n<li>TPM 2.0&nbsp;is&nbsp;enabled,&nbsp;<\/li>\n<\/ul>\n\n\n\n<ul>\n<li>Secure&nbsp;Boot&nbsp;is&nbsp;enabled,&nbsp;<\/li>\n<\/ul>\n\n\n\n<ul>\n<li>BIOS\/UEFI is up to date,&nbsp;<\/li>\n<\/ul>\n\n\n\n<ul>\n<li>Windows 11 version 25H2 is being deployed,&nbsp;<\/li>\n<\/ul>\n\n\n\n<ul>\n<li>the latest OA3Tool version is used,&nbsp;<\/li>\n<\/ul>\n\n\n\n<ul>\n<li>the CBR is generated correctly,&nbsp;<\/li>\n<\/ul>\n\n\n\n<ul>\n<li>the&nbsp;CBR is&nbsp;submitted&nbsp;before Windows activation.&nbsp;<\/li>\n<\/ul>\n\n\n\n<p><strong>How XDE helps<\/strong>&nbsp;<\/p>\n\n\n\n<p>XDE (eXpress&nbsp;Deployment Environment) automates device preparation while supporting compliance with Microsoft MAR requirements.&nbsp;<\/p>\n\n\n\n<p>It&nbsp;helps&nbsp;partners&nbsp;by:&nbsp;<\/p>\n\n\n\n<ul>\n<li>deploying up-to-date Windows images,&nbsp;<\/li>\n<\/ul>\n\n\n\n<ul>\n<li>automating&nbsp;CBR&nbsp;reporting,&nbsp;<\/li>\n<\/ul>\n\n\n\n<ul>\n<li>integrating&nbsp;with MAR&nbsp;licensing,&nbsp;<\/li>\n<\/ul>\n\n\n\n<ul>\n<li>reducing&nbsp;manual&nbsp;configuration&nbsp;errors,&nbsp;<\/li>\n<\/ul>\n\n\n\n<ul>\n<li>standardizing&nbsp;the&nbsp;refurbishment&nbsp;process.&nbsp;<\/li>\n<\/ul>\n\n\n\n<p>This significantly reduces or eliminates (depending on settings) the risk of compliance issues and Default Charges.\u00a0<\/p>\n\n\n\n<p><strong>Summary<\/strong>&nbsp;<\/p>\n\n\n\n<p>Minimum Hardware Requirements have become one of the most important compliance elements of the Microsoft Authorized&nbsp;Refurbisher&nbsp;program. Microsoft&nbsp;validates&nbsp;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.&nbsp;<\/p>\n\n\n\n<p>Keeping deployment environments up to date, using the latest Windows release and OA3Tool, and submitting CBRs on time are essential for&nbsp;maintaining&nbsp;compliance and avoiding Default Charges.&nbsp;<\/p>\n","protected":false},"excerpt":{"rendered":"MHR (Minimum Hardware Requirements) \u2013 Everything Microsoft Authorized&nbsp;Refurbisher&nbsp;Partners Need to Know&nbsp; Microsoft continues to strengthen compliance controls for devices refurbished under the&nbsp;Microsoft Authorized&nbsp;Refurbisher&nbsp;(MAR)&nbsp;program. One of ","protected":false},"author":113,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":[],"categories":[37],"tags":[],"_links":{"self":[{"href":"https:\/\/mar.netland.pl\/en\/wp-json\/wp\/v2\/posts\/1324"}],"collection":[{"href":"https:\/\/mar.netland.pl\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/mar.netland.pl\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/mar.netland.pl\/en\/wp-json\/wp\/v2\/users\/113"}],"replies":[{"embeddable":true,"href":"https:\/\/mar.netland.pl\/en\/wp-json\/wp\/v2\/comments?post=1324"}],"version-history":[{"count":1,"href":"https:\/\/mar.netland.pl\/en\/wp-json\/wp\/v2\/posts\/1324\/revisions"}],"predecessor-version":[{"id":1325,"href":"https:\/\/mar.netland.pl\/en\/wp-json\/wp\/v2\/posts\/1324\/revisions\/1325"}],"wp:attachment":[{"href":"https:\/\/mar.netland.pl\/en\/wp-json\/wp\/v2\/media?parent=1324"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/mar.netland.pl\/en\/wp-json\/wp\/v2\/categories?post=1324"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/mar.netland.pl\/en\/wp-json\/wp\/v2\/tags?post=1324"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}