Turkey (Turkish)
Germany (German)
Worldwide (English)
Microsoft states that Quick Machine Recovery is available on Windows 11 24H2 build 26100.4700 or later.
Halkali merkez neighborhood fatih st ozgur apt no 46 , Kucukcekmece , Istanbul , 34303 , TR
Learn Windows 11 Quick Machine Recovery cloud remediation, auto remediation, WinRE flow, reagentc XML settings, network requirements and test mode.
Microsoft states that Quick Machine Recovery is available on Windows 11 24H2 build 26100.4700 or later.
QMR uses a connected WinRE to search Windows Update for targeted remediations during critical boot failures.
Cloud remediation is enabled by default on unmanaged Home/Pro devices and disabled by default on enterprise-managed devices.
Startup Repair tries to repair known local boot problems. QMR adds a network-connected path that queries Windows Update for a Microsoft-published remediation. Its main advantage appears during widespread, known boot incidents.
Microsoft describes QMR as a best-effort feature. A cloud fix is not guaranteed for every boot failure; if no remediation is found, WinRE falls back to other options or retries according to configuration.
The baseline is Windows 11 24H2 build 26100.4700 or later. Use `winver` to verify the actual build, not just the 24H2 label. Older builds may not expose the same QMR configuration.
Cloud remediation is enabled by default on Home and unmanaged Pro devices with a one-time scan. Enterprise/Education and domain/MDM-managed Pro devices default to disabled so administrators can choose policy.
winverreagentc.exe /inforeagentc.exe /getrecoverysettingsThe current UI path is Settings > System > Recovery > Quick machine recovery. You can enable QMR and Automatically check for solutions, then choose a one-time or retry scan interval.
These settings do not represent a post-boot troubleshooter; QMR operates inside Windows Recovery Environment. If WinRE is disabled, QMR cannot operate as intended.
reagentc.exe /infoQMR can be applied from an XML file. The XML can contain CloudRemediation, AutoRemediation, totalwaittime, waitinterval and supported Wi-Fi credentials. Organizations should separately assess whether storing a password in such configuration meets their security policy.
After applying settings, verify them with `/getrecoverysettings`. Microsoft documents `/clearrecoverysettings` to remove the configured recovery settings.
reagentc.exe /setrecoverysettings /path settings.xmlreagentc.exe /getrecoverysettingsreagentc.exe /clearrecoverysettingsMicrosoft currently documents support for wired networking and WPA/WPA2 password-based Wi-Fi. Captive portals, 802.1X enterprise authentication or networks requiring additional clients can prevent connectivity in recovery.
For Windows VPS use, QMR depends on WinRE recognizing the virtual NIC and having outbound Windows Update access. It should not be the only recovery strategy when console/KVM access is unavailable.
Microsoft provides a QMR simulation mode, but it requires Windows Insider Program Dev Channel enrollment. `/SetRecoveryTestmode` followed by `/BootToRe` simulates the recovery experience on next boot.
Do not run this test without a maintenance window on a production domain controller, critical Hyper-V host or system whose only access path is RDP. Even the simulation triggers a restart and WinRE flow.
reagentc.exe /SetRecoveryTestmodereagentc.exe /BootToReMicrosoft states that an applied QMR remediation appears after boot under Settings > Windows Update > Update history in Quality updates. This provides evidence of what changed rather than treating the recovery as unexplained.
| Device state | Cloud remediation default |
|---|---|
| Windows Home | Enabled, one-time scan |
| Unmanaged Windows Pro | Enabled, one-time scan |
| Enterprise/Education or managed Pro | Disabled; admin configures |
Before production changes, verify context and keep backups and a rollback plan. Do not change several DNS, TLS, recovery, Docker or WordPress variables at once because it obscures the root cause.
No. Microsoft describes it as best effort; an automatic fix requires a relevant cloud remediation.
The current Microsoft page documents it for Windows 11. Do not assume Windows Server has the same feature.
Microsoft currently supports wired and WPA/WPA2 password-based Wi-Fi; enterprise or captive-portal networks can be problematic.
If the problem persists in hosting, VPS, Docker, Cloudflare, Windows or WordPress infrastructure, open a technical support request with the exact error output and current architecture.