An IT professional monitors a centralized software update rollout across networked laptops.
Windows Autopatch now does more than approve and deploy updates. Petri's latest roundup groups readiness checks, approval controls, hotpatching, Extended Security Updates (ESU) tracking and Quick Machine Recovery (QMR) management into one expanded Autopatch story. Microsoft's own documentation shows those features did not all arrive at the same time. This piece separates what is new from what was already available, and notes which claims could not be confirmed.

The main new feature is this: one quality update policy in Intune can now steer Windows quality updates, supported .NET Framework updates, and quick machine recovery fixes, with automatic or manual approval by update type and status surfaced in new Autopatch reports. Microsoft announced it on the Windows IT Pro Blog on November 12, 2026, a week before Petri's article. Message Center notices had already flagged it. M365 Admin's tracking of the notice describes the enhancements as rolling out Sept 1–Oct 15, 2026.

An IT professional monitors a centralized software update rollout across networked laptops. What changed in Windows Autopatch quality update policies​

The approval model is more granular than it was. Admins can configure automatic or manual approval by update type for monthly security updates, monthly non-security preview updates, out-of-band security updates, and out-of-band non-security updates. Approval settings for each category apply to both Windows OS quality updates and supported .NET Framework releases.

Microsoft also gives a clear recommendation. Windows Autopatch recommends automatic approval for security updates and manual approval for optional updates. According to Microsoft Learn, automatic approval for monthly security updates is the default in a new policy and all other update types default to manual. The "Make updates available after" deferral setting accepts 0 to 30 days. Microsoft advises keeping quality update deferrals under three days.

You'll find the new policy in the Microsoft Intune admin center under Devices > Manage updates > Windows updates > Quality updates. To create one, select Create, then Windows quality update policy. On the policy page, the top section covers Windows quality updates and Windows 11 .NET Framework updates together. Quick machine recovery and hotpatch controls live on the same page.

The deferral rule that can catch you out​

If you already run update rings or Windows Autopatch Groups, pay close attention to this one. Under automatic approval, the quality update policy's deferral replaces your ring deferral. It does not add to it. Microsoft's own example: a device with a 5-day ring deferral and a 2-day quality policy deferral gets the update 2 days after release, not 7. Under manual approval there's no deferral at all, and devices get the update once you approve it.

ITECS's deployment guide says the same thing: cloud quality-policy deferrals override legacy update-ring/CSP deferrals; other client deadlines and grace periods still apply. Deadlines, grace periods and restart behaviour still come from your rings. Only the timing of when an update is offered moves to the new policy.

Microsoft suggests a simple way to keep phased rollouts and still get approvals. Create one quality update policy for each ring, give it the same deferral as that ring, and assign it to the same groups. Rings at 0, 1 and 5 days become three policies at 0, 1 and 5 days.

Watch-outs before you switch:

  • You can't change the approval method later. Changing an existing policy's approval method requires a new policy.
  • Pausing doesn't roll back. A paused release stops reaching new devices but stays installed where it already landed. Microsoft says devices can take up to eight hours to pick up new pause settings.
  • Pauses are per release. Pausing a .NET Framework release doesn't pause an approved Windows OS update, and pausing an OS update doesn't pause .NET.
  • Older hotpatch policies need attention. If you created a hotpatch quality update policy before approvals reached your tenant, Microsoft says to open it, review the approval settings and save it.
  • Windows 10 ESU devices are an exception. Microsoft Learn says Windows 10 devices enrolled in ESU still get .NET Framework updates from Windows Update based on client-side settings. On those devices, policy approvals cover only Windows OS quality updates, and .NET updates may cause a separate restart. .NET Framework 3.5 updates can't be managed through these policies at all.

Section summary: One Intune policy now handles approvals for Windows quality updates, supported .NET Framework updates and QMR fixes. Its deferral replaces your ring deferral rather than adding to it.

Quick Machine Recovery under Autopatch management​

QMR is part of Microsoft's broader Windows Resiliency Initiative, which Petri also mentions. It's aimed at the kind of mass boot failure no admin wants to repeat. Quick machine recovery launches the Windows Recovery Environment (WinRE) after two failed boots and pulls a Microsoft fix when one is available. Petri notes it targets boot failures caused by Windows issues or third-party kernel-mode drivers.

Approval works much like it does for other quality updates. In Autopatch, configure QMR approvals through Intune's Windows quality-update policies. New policies default to manual QMR approval. If you choose automatic approval, you can add an optional deferral. If you leave the default, a Microsoft-issued fix waits in Manage updates until someone approves it.

Pick that default carefully. If a fleet-wide boot loop happens at 3 a.m., is someone on call to approve the fix?

Microsoft Learn adds some precedence rules:

  • Autopatch-enrolled devices have cloud remediation and auto remediation turned on automatically. You don't need to deploy the Recovery CSP to enable them.
  • Autopatch service settings take precedence over Recovery CSP, Group Policy, scripts and custom OMA-URI settings. You can't use those methods to switch cloud remediation off on an enrolled device.
  • Remediations apply only after they're approved in the device's quality update policy. Manual approval and Pause are your control points.
  • QMR is described as best effort. It uses WinRE and Windows Update to look for remediations, so network connectivity matters. Microsoft says only wired networks and WPA/WPA2 password-based Wi-Fi are currently supported.

If a managed device doesn't apply a remediation you expected, Microsoft says to first check whether the remediation is approved or paused for that device's policy in the Intune admin center.

The QMR report is quiet until something goes wrong​

According to the Message Center notice, admins can use the new quick machine recovery update status report to view affected devices, remediation status, applicable fix version, release date, assigned quality update policy, and OS version. Don't expect it to show anything on a normal day. The Quick machine recovery updates report stays blank until a boot-critical issue occurs and Quick machine recovery updates are deployed. Microsoft lists three device states: In boot failure, In progress and Remediated. Both quality update reports refresh every four hours.

Section summary: QMR fixes now go through the same approval process as other quality updates, with manual approval as the default. The status report is empty until a real boot-critical incident occurs.

Readiness checks: useful, but not new this month​

Petri leads with automated readiness checks and a device update journey view. Both exist, but neither is new. Microsoft made Windows Autopatch update readiness generally available on March 2, 2026. It includes:

  • A management status report listing all Intune-managed Windows devices, including those not covered by any update policy
  • A device update journey report
  • A centralized alerting framework
  • A readiness checker that runs without a deployment policy and checks connectivity, safeguard holds, appraiser markers and hotpatch prerequisites

One limit matters here. Microsoft's documentation says the current device update journey report covers feature updates specifically. Don't assume every update type gets the same step-by-step tracking yet.

Hotpatch on Arm64, ESU tracking and maintenance windows​

Hotpatch on Arm64: Microsoft's Autopatch FAQ confirms hotpatch updates are available for Arm64 devices, but devices have to qualify. Requirements include a qualifying license, Windows 11 version 24H2 (build 26100.2033 or later), a current baseline, Intune management with a hotpatch-enabled quality update policy, and Virtualization-based Security enabled. Arm64 devices must also disable compiled hybrid PE usage (CHPE). Devices that don't qualify keep getting the standard monthly security updates.

ESU tracking: Petri says Autopatch can track ESU enrollment, identify Windows 10 devices without coverage and send alerts. The Microsoft documentation reviewed for this piece doesn't describe those specific functions, so treat them as unconfirmed for now. The documented ESU detail is the .NET exception covered above.

Maintenance windows: Petri says maintenance windows covering drivers, .NET, apps and Windows will arrive "starting in early 2026." That date has already passed, and no current Microsoft documentation found for this piece confirms the feature's availability or scope. Check your own tenant and the Message Center before planning around it.

The bigger picture​

Microsoft's approach is clear. Approvals, phased timing, recovery fixes and reporting are all moving into one Intune policy surface. For admins with sprawling ring setups, that consolidation is welcome. It also brings new risks: deferrals that replace each other quietly, approval methods you can't edit after creation, and a recovery feature whose default may leave fixes waiting for a human.

Petri's own conclusion is the right one. These features are operational improvements, not a substitute for testing, change control or getting off unsupported Windows 10 machines.

Before you roll this out:

  1. Write down your current ring deferrals and build matching quality update policies one-to-one.
  2. Decide on QMR approval (automatic with a short deferral, or manual) and record who can approve a fix out of hours.
  3. Open and re-save any older hotpatch policies.
  4. Check Arm64 devices for VBS, the required baseline and the CHPE setting before you expect hotpatches.
  5. Make sure WinRE has wired or WPA/WPA2 network access, or QMR can't download a fix.

If you're already running these policies, share how your per-ring setup has worked out in the forum's Intune and Windows Update threads.

 

References

  1. Microsoft Expands Windows Autopatch With Recovery, Reporting, and Update Controls - Petri IT Knowledgebase Petri IT Knowledgebase 2026-11-19T15:03:22+00:00
  2. Quick machine recovery updates in Windows Autopatch | Microsoft Learn learn.microsoft.com
  3. More control for Windows Autopatch updates: quality updates, .NET Framework, and quick machine recovery - M365 Admin m365admin.handsontek.net