Blog Post

Microsoft Intune Blog

4 MIN READ

Understanding readiness for Windows 11 with Microsoft Endpoint Manager

Microsoft

Sep 21, 2021

With the announcement of Windows 11, you might be wondering how your organization can prepare for the upgrade, as well as what you can do right now to set yourself up for success. One of the first things you’ll want to consider is using Microsoft Endpoint Manager to assess which devices in your organization meet the minimum system requirements for Windows 11.

Over the next few days, we’ll be updating the Work from anywhere report in Endpoint analytics with new Windows 11 hardware readiness insights. These changes will allow you to easily determine Windows 11 hardware readiness across your organization. Windows 11 insights will be available for all Intune-managed and co-managed devices in Endpoint analytics, as well as devices enrolled via tenant attach with Configuration Manager, version 2107 or newer.

Looking at Windows 11 readiness at the individual device level in Microsoft Endpoint Manager

If you’re not yet using Endpoint analytics, or you’re using an older version of Configuration Manager, we’re also publishing a Hardware Readiness PowerShell script today as an interim solution that can help you determine if your devices meet the Windows 11 minimum system requirements.

While the script can help you get started planning for Windows 11 right away, we also encourage you to onboard to Endpoint analytics so you can benefit from additional Windows 11 insights as well as the existing features that can help you optimize the end-user experience in your organization. And if you’re using Configuration Manager, consider enabling co-management so that you can benefit from new reports and features – like Windows 11 hardware readiness insights – with no on-premises upgrades required. To learn more about Endpoint analytics, you can refer to Microsoft Docs or some of our sessions from Microsoft Ignite.

Running the Hardware Readiness script

To determine whether an individual device meets the system requirements for Windows 11, you can run the script locally from an elevated PowerShell prompt. To run the script at scale, we recommend leveraging Microsoft Endpoint Manager. While the script has been digitally signed by Microsoft, you may need to adjust the PowerShell Execution Policy on your Windows devices.

Microsoft Intune users can leverage the Intune management extension to upload the Hardware Readiness PowerShell script, and then deploy it to a target set of devices. As with any deployment, we recommend testing on a small set of devices before rolling out more broadly. Then, use Microsoft Graph explorer to access and aggregate the results of the script. The output data can be ingested into Azure Log Analytics or saved locally for you to query and visualize as desired. A step-by-step walkthrough of using this method to aggregate script results is available on the Device Management in Microsoft blog.

Organizations using Configuration Manager can use the Run Scripts feature which provides the built-in ability to deploy and aggregate results from a PowerShell script. To learn more about this process, the Script output section of the Microsoft Docs article, Create and run PowerShell scripts from the Configuration Manager console.

Understanding the Hardware Readiness script output

The Hardware Readiness script is meant to determine if a device meets the minimum system requirements for Windows 11, and in the case that not all requirements are met, it will highlight which hardware checks failed. Results are returned in JSON format with four key/value pairs:

returnCode: an integer value that represents whether the device meets the minimum system requirements for Windows 11. Possible results include:

returnCode	Definition
-2	FAILED TO RUN – the script encountered an error
-1	UNDETERMINED – one or more of the hardware requirement checks failed to execute properly
0	CAPABLE – the device meets all assessed Windows 11 hardware requirements
1	NOT CAPABLE – the device does not meet one or more of the assessed Windows 11 hardware requirements

returnReason: a string value that provides a comma-separated list of the Windows 11 hardware requirements that are not met on the device. For instance, if the script is run on a device that meets all hardware requirements except the Storage requirement, returnReason would equal “Storage.” In the case that all hardware requirements are met, returnReason will be NULL. Possible results include:

returnReason

Storage

Memory

TPM

Processor

SecureBoot

For a complete list of minimum system requirements for Windows 11, see Windows 11 requirements. You can also find additional details on the Windows 11 System Requirements, page, including the steps you might be able to take to modify or update a Windows 10 device to make it eligible for the upgrade to Windows 11.
logging: a string value that provides verbose logging of the determined values for all hardware checks performed on the device.
returnResult: a string value that is a human-readable representation of returnCode. Possible results include: CAPABLE, NOT CAPABLE, UNDETERMINED, and FAILED TO RUN.

Disclaimer: This Hardware Readiness PowerShell Script is not supported under any Microsoft standard support program or service and is distributed under the MIT license.

Updated Sep 21, 2021

Version 1.0

microsoft intune

Zach Dvorak

Microsoft

Joined November 30, 2017

View Profile

Microsoft Intune Blog

Follow this blog board to get notified when there's new activity

26 Comments

drkmccy
Brass Contributor
Dec 15, 2024
Zach Dvorak More CPU's incorrectly being flagged as incompatible:
Barindervicky89
Copper Contributor
Nov 23, 2024
Zach Dvorak
I run this script and it is saying not capanbl. failure reason is processor. The processor is "Intel(R) Core(TM) i5-10500T CPU @ 2.30GHz 792 MHz".

When I run the PC health Check, it is saying good health and machine can upgrade into windows 11. This processor is also supported by Microsoft
https://learn.microsoft.com/en-us/windows-hardware/design/minimum/supported/windows-11-supported-intel-processors

Is there way to fix it and exclude those processors which are supported by Microsoft ?

Thanks,
- KyleSchroeder
  Copper Contributor
  Nov 24, 2024
  It's probably that the CPU is under clocking at 792mhz, one of the script requirements is 1000mhz:
  [Uint32]$MinClockSpeedMHz = 1000
  Try changing the performance/power saving setting, or really the script needs to be updated to look at the CPU model to be supported vs the current mhz (or change that line in the script to 700, then rerun it).
  - Barindervicky89
    Copper Contributor
    Nov 25, 2024
    Yes It is due to clockSpeedMHz. however it is compatible model.
    How we can add this in script "the CPU model to be supported vs the current mhz"
    
    Thanks,
divadiow2
Copper Contributor
Jul 08, 2024
how can we rerun the hardware readiness report that gets uploaded to WUfB? We're sorting EFI system partition free space issues but have to wait days/weeks for the report in Intune to change.
drkmccy
Brass Contributor
Mar 23, 2024
Zach DvorakI've ran the script on our estate using our RMM tool. So far it's worked a treat, however, it's picking up the i5-1230U as not being compatible?
PadSelmke
Microsoft
Mar 16, 2023
In order for a compatibility check to be performed and the registry entry to be created under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\CompatMarkers, the telemetry must be at least Basic (1).

HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\DataCollection:AllowTelemetry = 1

Clients where the telemetry is set to 0 do not create a registry entry.
MostafaRehim10
Microsoft
Feb 16, 2023
I have same issue in my test Lab plus those devices aren't visible under Device Performance
Mortennords
Copper Contributor
Dec 21, 2022
Hello,

I've recently discovered a problem regarding Work from anywhere report in Endpoint/intune.

It looks like not every PC in our organization is showing in the Windows 11 readiness report?
We're missing like 2/20 PC's.
How is this poosible? Every PC is enrolled the same way, and looks "identical".

"Device Performance shows everyone, but "Windows" lacks some...
Afghanboy20221590
Copper Contributor
Nov 12, 2022
I am so satisfied from your services
Thank you so much for your time.
No_Vidya
Copper Contributor
Mar 24, 2022
You can also look into the UPGRADE_EXPERIENCE_INDICATORS attribute class and SQL View v_GS_UPGRADE_EXPERIENCE_INDICATORS to create a simple Windows 11 upgrade readiness report.

MattHempel

Copper Contributor

Jan 11, 2022

The readiness script always returns a Pass for SecureBoot for me even if SecureBoot is disabled.

Might need something like below ?

try {
    $isSecureBootEnabled = Confirm-SecureBootUEFI
	
	if ($isSecureBootEnabled) {
		$outObject.logging += $logFormatWithBlob -f $SECUREBOOT_STRING, $CAPABLE_STRING, $PASS_STRING
		UpdateReturnCode -ReturnCode 0		
	}
	else {
		$outObject.logging += $logFormatWithBlob -f $SECUREBOOT_STRING, $CAPABLE_STRING, $FAIL_STRING
		UpdateReturnCode -ReturnCode 1
		$exitCode = 1
	}
}
catch [System.PlatformNotSupportedException] {

ok , just found that it is not a requirement for Windows 11 to have SecureBoot enabled, system just needs to be capable.

https://support.microsoft.com/en-us/windows/windows-11-and-secure-boot-a8ff1202-c0d9-42f5-940f-843abef64fad

\n returnCode \n	\n Definition \n
\n -2 \n	\n FAILED TO RUN – the script encountered an error \n
\n -1 \n	\n UNDETERMINED – one or more of the hardware requirement checks failed to execute properly \n
\n 0 \n	\n CAPABLE – the device meets all assessed Windows 11 hardware requirements \n
\n 1 \n	\n NOT CAPABLE – the device does not meet one or more of the assessed Windows 11 hardware requirements \n

\n returnCode \n	\n Definition \n
\n -2 \n	\n FAILED TO RUN – the script encountered an error \n
\n -1 \n	\n UNDETERMINED – one or more of the hardware requirement checks failed to execute properly \n
\n 0 \n	\n CAPABLE – the device meets all assessed Windows 11 hardware requirements \n
\n 1 \n	\n NOT CAPABLE – the device does not meet one or more of the assessed Windows 11 hardware requirements \n