QMR Arrives on Windows Server 2025
Microsoft says Windows Server 2025 now supports Quick Machine Recovery (QMR) after the October update. The feature first appeared in Windows 11.
When the system hits a severe fault, Windows Server 2025 QMR uses the Windows Recovery Environment (WinRE). WinRE connects to Microsoft servers, finds a targeted fix, and applies it.
How QMR Handles Boot Failures
After several failed boots, the server drops into WinRE automatically. Once WinRE has network access, a built-in process asks Microsoft for a suitable remedy.
If it finds one, the server downloads and installs the fix, then restarts. If not, the server falls back to the normal recovery process.
Why Targeted Fixes Matter
After a large-scale failure, Microsoft or an OEM usually publishes a remedy. QMR lets machines fetch that remedy over the network on their own.
The feature traces back to the July 2025 outage caused by a CrowdStrike antivirus driver. Roughly 8 million devices worldwide hit the blue screen of death. Microsoft then built QMR to help organizations restore machines quickly.
Admins Stay in Control
IT administrators decide whether QMR runs, and whether it scans for and applies fixes automatically. They can find the options in Group Policy under Computer Configuration, Administrative Templates, System, then Quick Machine Recovery. Microsoft documents the steps in its guide to configuring QMR through Group Policy.
Key Policy Settings
- Cloud remediation: lets WinRE go online and fetch fixes.
- Auto remediation: controls whether the server checks for fixes after a boot failure.
- Retry interval and total wait time: by default, the server tries only once. For unattended or headless servers, admins can set an interval above zero so the server checks again within the wait time.
Microsoft’s Rollout Advice
Microsoft advises admins to test the policy and the recovery environment on a small set of servers first. If all goes well, they can widen the rollout step by step.
When managing the policy through domain Group Policy, admins should scope it to Windows Server 2025 only.
Support Our Threat Intelligence
Find our tech and OS security coverage helpful? Support our work today and unlock a 100% ad-free reading experience!