ANAVEM
Languagefr
How to Enable Intune Quick Machine Recovery for Windows 11 Devices

How to Enable Intune Quick Machine Recovery for Windows 11 Devices

Configure Intune Quick Machine Recovery to automatically remediate Windows 11 24H2 devices stuck in recovery mode using cloud-based solutions and Settings Catalog policies.

April 4, 2026 15 min
mediumintune 8 steps 15 min

What is Intune Quick Machine Recovery and Why Enable It?

Quick Machine Recovery (QMR) represents a significant advancement in Windows 11 device management, providing automated cloud-based remediation for devices stuck in recovery scenarios. Available starting with Windows 11 version 24H2 (build 26100.4700), QMR leverages Windows Update infrastructure within the Windows Recovery Environment (WinRE) to automatically download and apply fixes when devices encounter boot failures or system corruption.

For enterprise environments managing hundreds or thousands of Windows 11 devices, QMR reduces the need for manual intervention when devices experience recovery issues. Instead of requiring IT staff to physically access affected machines or perform complex remote troubleshooting, QMR enables devices to self-heal using Microsoft's cloud-based remediation packages.

How Does QMR Integration with Intune Benefit Enterprise Deployments?

Microsoft Intune integration allows centralized management of QMR settings across your entire Windows 11 fleet. Using the Settings Catalog approach, administrators can configure cloud remediation policies, set retry intervals, define timeout periods, and even preconfigure Wi-Fi credentials for devices that lack Ethernet connectivity during recovery scenarios.

The key advantage lies in consistency and scale. Rather than manually configuring each device or relying on Group Policy in domain-joined scenarios, Intune ensures that all enrolled Windows 11 24H2 devices receive identical QMR configurations. This standardization is particularly valuable for hybrid work environments where devices may not always have direct domain connectivity but maintain cloud-based management through Intune.

What Are the Technical Requirements for QMR Implementation?

QMR requires specific technical prerequisites that distinguish it from traditional recovery methods. Windows 11 Pro and Enterprise editions require explicit policy enablement through Intune, while Home editions enable cloud remediation by default. The feature depends on network connectivity during recovery scenarios, making Ethernet connections ideal or requiring Wi-Fi credential preconfiguration for wireless-only environments.

Implementation Guide

Full Procedure

01

Verify Windows 11 24H2 Requirements and WinRE Status

Before configuring QMR, confirm your devices meet the minimum requirements. Quick Machine Recovery requires Windows 11 version 24H2 (build 26100.4700 or later) and an enabled Windows Recovery Environment.

Open an elevated Command Prompt on a target device and run:

winver

Verify the build number shows 26100.4700 or higher. Next, check WinRE status:

reagentc /info

Look for "Windows RE status: Enabled" in the output. If disabled, enable it:

reagentc /enable

For bulk verification across your environment, use this PowerShell command on each device:

Get-ComputerInfo | Select-Object WindowsVersion, WindowsBuildLabEx
reagentc /info
Pro tip: Use Intune device compliance policies to report on Windows versions across your fleet before deploying QMR policies.

Verification: Confirm all target devices show Windows 11 24H2 and WinRE enabled status.

02

Create Device Groups for QMR Deployment

Navigate to the Microsoft Intune admin center and create targeted device groups for QMR deployment. This ensures you can control which devices receive the policy and monitor deployment progress.

In the Intune admin center:

  1. Go to Groups > All groups > New group
  2. Set Group type to Security
  3. Enter Group name: "Windows 11 24H2 - QMR Enabled"
  4. Set Membership type to Dynamic Device
  5. Click Add dynamic query

Use this dynamic membership rule to target Windows 11 24H2 devices:

(device.deviceOSVersion -startsWith "10.0.26100") and (device.deviceOSType -eq "Windows")

Alternatively, for manual assignment, select Assigned membership and manually add your Windows 11 24H2 devices.

Warning: QMR policies only work on Windows 11 Pro/Enterprise 24H2+. Home editions have cloud remediation enabled by default but cannot be managed via Intune policies.

Verification: Check the group shows the expected device count under Members after Azure AD sync completes (usually 5-10 minutes).

03

Create Settings Catalog Configuration Profile

Create a new configuration profile using Settings Catalog to configure QMR settings. This is the recommended method as it provides the most granular control over QMR parameters.

In the Intune admin center:

  1. Navigate to Devices > Windows > Configuration profiles
  2. Click Create > New policy
  3. Select Platform: Windows 10 and later
  4. Select Profile type: Settings catalog
  5. Click Create
  6. Enter Name: "Windows 11 - Quick Machine Recovery (QMR)"
  7. Add optional description: "Enables cloud-based automatic remediation for Windows 11 24H2 devices in recovery scenarios"

Click Next to proceed to configuration settings.

Verification: Confirm you're on the Configuration settings page with "Add settings" button visible.

04

Configure Remote Remediation Settings

Add and configure the Remote Remediation settings that control QMR behavior. These settings determine how aggressively the system attempts automatic recovery and network connectivity options.

On the Configuration settings page:

  1. Click Add settings
  2. In the search box, type "Remote Remediation"
  3. Expand Remote Remediation and select all available settings
  4. Click Add

Configure each setting as follows:

SettingRecommended ValuePurpose
Enable Cloud RemediationEnabledAllows downloading fixes from Windows Update in WinRE
Enable Auto RemediationEnabledAutomatically applies downloaded remediation without user intervention
Set Retry Scan Interval30 (minutes)How often to scan for new remediation packages
Set Time To Reboot180 (minutes)Maximum time before forcing reboot (max 4320 = 72 hours)

For enterprise environments with Wi-Fi, optionally configure:

  • Wi-Fi SSID: Your corporate Wi-Fi network name
  • Wi-Fi Password: Network password (stored encrypted)
Pro tip: Set Retry Scan Interval to be less than or equal to Time To Reboot to avoid timeout loops. For critical systems, consider shorter intervals like 15-30 minutes.

Verification: All Remote Remediation settings should show "Configured" status with your specified values.

05

Assign Policy to Target Groups

Assign the QMR policy to your previously created device groups and configure deployment settings for controlled rollout.

Click Next to reach the Assignments page, then:

  1. Under Included groups, click Add groups
  2. Select "Windows 11 24H2 - QMR Enabled" group
  3. Click Select

For production deployments, consider using Intune's deployment rings:

Pilot Ring: 5-10 test devices
Broad Ring: Remaining production devices
Deployment schedule: 7-14 days between rings

Configure assignment filters if needed to exclude specific device types:

  1. Click Edit filter next to your assigned group
  2. Select Include filtered devices in assignment
  3. Choose existing filter or create new one

Example filter to exclude virtual machines:

(device.model -notContains "Virtual")
Warning: QMR policies will override any local reagentc.exe configurations. Ensure no conflicting Group Policy or local settings exist before deployment.

Verification: Confirm your target group appears under Included groups with the correct device count estimate.

06

Review and Deploy the Configuration Profile

Complete the policy creation process and initiate deployment to your target devices.

On the Review + create page:

  1. Verify all settings match your requirements
  2. Check assignment groups and filters
  3. Click Create to deploy the policy

Monitor deployment progress:

  1. Return to Devices > Windows > Configuration profiles
  2. Click on your "Windows 11 - Quick Machine Recovery (QMR)" policy
  3. Review the Device and user check-in status

Force immediate policy sync on test devices using PowerShell:

Get-ScheduledTask | Where-Object {$_.TaskName -eq "PushLaunch"} | Start-ScheduledTask
Start-Sleep -Seconds 10
Invoke-MDMAppDiagnosticsTool -AreaName "DeviceProvisioning" -OutputPath "C:\temp\MDMDiag"

Or use the Company Portal app: Settings > Sync

Verification: Policy should show "Succeeded" status for target devices within 15-30 minutes. Check individual device compliance in the policy overview.

07

Validate QMR Configuration on Target Devices

Verify that QMR settings have been successfully applied to your target devices using built-in Windows tools and registry verification.

On a target device, open an elevated Command Prompt and export the current recovery settings:

reagentc /getrecoverysettings

This creates an XML file (typically in C:\Windows\System32\Recovery\) containing current WinRE configuration. Look for RemoteRemediation entries.

Check the Windows Settings UI:

  1. Open Settings > System > Recovery
  2. Look for Quick machine recovery section
  3. Verify "Cloud remediation" shows as enabled

For programmatic verification, check these registry locations:

reg query "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\RemoteRemediation" /v CloudRemediation
reg query "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\RemoteRemediation" /v AutoRemediation

Expected output should show:

CloudRemediation    REG_DWORD    0x1
AutoRemediation     REG_DWORD    0x1

Use PowerShell to check across multiple devices:

$devices = @("Computer1", "Computer2", "Computer3")
foreach ($device in $devices) {
    Invoke-Command -ComputerName $device -ScriptBlock {
        Get-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\RemoteRemediation" -ErrorAction SilentlyContinue
    }
}

Verification: All target devices should show CloudRemediation and AutoRemediation values set to 1 (enabled).

08

Test QMR Functionality in Safe Environment

Test QMR functionality using Windows Insider builds or controlled test scenarios to ensure the configuration works as expected before relying on it in production.

Warning: QMR testing requires Windows Insider Dev or Beta Channel enrollment. Production testing should only be done on dedicated test devices, never on critical production systems.

For Windows Insider devices, enable test mode:

reagentc /SetRecoveryTestmode

Initiate a controlled boot to recovery environment:

reagentc /BootToRE

The system will reboot into WinRE and simulate a recovery scenario. QMR will:

  1. Detect the simulated failure
  2. Connect to Windows Update (using configured Wi-Fi if needed)
  3. Download available remediation packages
  4. Apply fixes automatically
  5. Reboot back to normal Windows

After the test completes, verify remediation occurred:

  1. Open Settings > Windows Update > Update history
  2. Look for entries related to "Quick Machine Recovery" or "Remediation"
  3. Check timestamps to confirm recent activity

Disable test mode when finished:

reagentc /disable
reagentc /enable

For production validation without full testing, monitor these event logs:

wevtutil qe "Microsoft-Windows-RemoteRemediation/Operational" /f:text /rd:true /c:10
Pro tip: Create a dedicated test device group with Windows Insider builds for ongoing QMR validation. This allows you to test new remediation packages before they reach production devices.

Verification: Test devices should successfully complete the recovery simulation and show remediation entries in Windows Update history.

Frequently Asked Questions

What Windows 11 versions support Intune Quick Machine Recovery?+
Quick Machine Recovery requires Windows 11 version 24H2 with build 26100.4700 or later. The feature reached general availability in build 26100.4770. Earlier Windows 11 versions (21H2, 22H2, 23H2) do not support QMR functionality. You can verify your build version using the 'winver' command.
Does Quick Machine Recovery work without internet connectivity during boot failures?+
No, QMR requires network connectivity to download remediation packages from Windows Update servers. Ethernet connections work automatically in WinRE, but Wi-Fi requires preconfigured credentials through the Intune policy. Without network access, QMR cannot function and devices will rely on traditional local recovery methods.
Can I test Quick Machine Recovery functionality without causing actual system failures?+
Yes, but only on Windows Insider Dev or Beta Channel devices. Use 'reagentc /SetRecoveryTestmode' to enable test mode, then 'reagentc /BootToRE' to simulate recovery scenarios. This safely tests QMR without actual system damage. Production devices cannot simulate QMR scenarios without Insider enrollment.
What happens if Quick Machine Recovery fails to remediate a device?+
QMR will retry based on your configured retry scan interval (default 30 minutes) until the timeout period expires (default 180 minutes, maximum 72 hours). If remediation fails completely, the device reboots normally and may present traditional recovery options. Failed attempts are logged in Windows Update history and RemoteRemediation event logs.
How do I monitor Quick Machine Recovery deployment success across my Intune environment?+
Monitor QMR policy deployment through the Intune admin center under Device configuration profiles. Check device compliance status, review assignment reports, and use the 'reagentc /getrecoverysettings' command on individual devices. You can also query registry keys under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\RemoteRemediation to verify policy application programmatically.

Discussion

Share your thoughts and insights

Sign in to join the discussion