Microsoft announced on October 19, 2026, that Quick machine recovery (QMR) is now supported on Windows Server 2025. The feature applies to systems with the October 2026 security update or later; it is not available across all Windows Server versions.
QMR is designed to help recover Windows when it can no longer start. From the Windows Recovery Environment (WinRE), it checks Windows Update for an applicable repair solution, then downloads and applies one in an attempt to restore booting.
However, cloud recovery is disabled by default on Windows Server 2025. Applying the update alone does not mean QMR is ready to use. Administrators need to configure the feature and check the settings already in place rather than assume it is either enabled or disabled.
Microsoft provides Group Policy guidance for managing cloud recovery, automatic repair, and retry intervals. Before changing settings across an organization, administrators should identify eligible servers and discuss whether QMR is appropriate for them with the people responsible for maintenance.
Check recovery connectivity
QMR does not search for solutions while Windows is running normally. WinRE must be available, and it must be able to make the necessary network connections during recovery. Normal access to Windows Update is not proof that those connections will work from WinRE.
Microsoft’s guidance also cautions that server QMR remediation should not be assumed to work through WSUS or offline update sources. The feature is designed to obtain remediation from Windows Update. Organizations that rely on internal update systems should confirm the requirements with their server administrators or maintenance provider.
This does not mean that all network restrictions should be removed. Connectivity should be assessed against the feature’s requirements and the organization’s security policies.
QMR is not a complete recovery plan
QMR cannot fix every startup problem. A suitable repair solution may not exist, or it may not apply to a particular server. Even if Windows starts again, teams still need to check that applications and data are working and decide whether business operations can safely resume.
Backups and alternative recovery procedures remain essential. Restoring the operating system does not necessarily restore lost data or confirm that the wider business system is healthy.
Before adopting QMR, confirm:
- Which servers are eligible? Check whether they run Windows Server 2025 and have the required updates.
- Is the feature ready to use? Review QMR settings, WinRE availability, and recovery-time connectivity.
- What happens if QMR does not work? Identify the escalation contact, alternative recovery steps, and when to switch to manual support.
For outsourced server management, ask not only whether the provider supports QMR, but whether they intend to use it on the specific server—and what recovery process they will follow if they do not. Microsoft recommends validating settings on a limited set of systems before expanding deployment, rather than testing by rebooting production servers all at once.
QMR offers an additional recovery option, not a guarantee of recovery. The important distinction is between a feature being supported and an environment being configured and prepared to use it.