Black Friday sale: an extra 40% off every course until Monday, November 30.New Year sale: an extra 30% off every course until Friday, January 1.Memorial Day sale: an extra 25% off every course until Monday, May 31.SysAdmin Day sale: an extra 25% off every course until Sunday, August 1.Back to School sale: an extra 25% off every course until Sunday, August 22.Labor Day sale: an extra 25% off every course until Monday, September 6.Black Friday sale: an extra 40% off every course until Monday, November 29.New Year sale: an extra 30% off every course until Saturday, January 1.Choose your certification →

Copyright (c) 2026 MindMesh Academy. All rights reserved. This content is proprietary and may not be reproduced or distributed without permission.

4.2.2. Windows Autopatch and Hotpatch

💡 First Principle: Restarts are the hidden cost of patching. Users postpone them, so a downloaded fix can sit uninstalled for days. Hotpatch removes the restart from most months, and Windows Autopatch removes the scheduling work by running the rollout as a service. Both shorten the gap between "fix released" and "device protected", which is why Microsoft now switches hotpatch on by default.

Windows Autopatch orchestrates feature, quality and driver updates (plus Microsoft 365 Apps and Edge updates through Autopatch groups). Its prerequisites define which devices can use it:

  • Microsoft Entra ID P1 or P2 plus Intune for the tenant.
  • Devices enrolled in Intune, corporate-owned (Windows personal devices are blocked at registration), managed by Intune or co-managed (Configuration Manager alone isn't supported) and in contact with Intune within the last 28 days.
  • On co-managed devices, the Windows Update policies and Device configuration workloads set to Intune or Pilot Intune.
  • A Windows license with the Autopatch entitlement. All entitled tiers get the core features; only the E3, E5 and F3 tiers can open Autopatch support requests — Business Premium and the A3/A5 education tiers can't.

LTSC devices are supported for quality updates only.

Autopatch groups automate staged rollout. A group is a logical container of device-based Entra groups plus update policies, and it always has a Test ring and a Last ring that can't be removed or renamed. A group needs at least two rings and supports up to 15; a tenant supports up to 300 groups. Devices are distributed to rings dynamically by percentage or assigned by group, and user-based Entra groups aren't supported. Microsoft's recommended quality rollout (deferral, deadline, grace in days) is Test 0/0/0, Ring 1 1/0/1 and Last 2/1/2. Autopatch groups don't configure everything: quality, expedite and hotpatch settings are still configured manually.

Hotpatch delivers the monthly security update ("B release") in a form that takes effect without a restart, in a much smaller package than a cumulative update. Its requirements:

  • Windows 11 version 24H2 or later, on the latest baseline.
  • VBS running.
  • An eligible license: Windows 11 Enterprise E3 or E5, Microsoft 365 F3, Windows 11 Education A3 or A5, Microsoft 365 Business Premium or Windows 365 Enterprise.
  • Intune management through a Windows quality update policy with hotpatch allowed.
  • On Arm64 devices, CHPE disabled.

Hotpatch isn't a separate policy type. It's the setting "When available, apply without restarting the device ("Hotpatch")" inside a Windows quality update policy (Devices > Manage updates > Windows updates > Quality updates > Create > Windows quality update policy). With hotpatch now on by default for eligible devices, you use that same setting in a quality update policy to opt groups out. Devices that aren't eligible simply get the standard cumulative update, which needs a restart.

Hotpatch doesn't eliminate restarts entirely. It follows a fixed quarterly rhythm:

That's four baseline months and eight hotpatch months a year. An unplanned out-of-band baseline doesn't shift the calendar, and a device that isn't on the latest baseline in a hotpatch month gets both the baseline (with a restart) and the hotpatch. Timing a Windows version upgrade matters: upgrading, say from 24H2 to 25H2, in a baseline month keeps the device on hotpatch, but upgrading in a hotpatch month switches it to standard updates until the next baseline. A device upgraded in May would therefore take a standard, restart-requiring update in June and return to hotpatch after the July baseline.

A few more behaviors to know:

  • Hotpatch doesn't change ring deferrals, deadlines or active hours.
  • There's no automatic rollback. You can uninstall a hotpatch (which needs a restart) and install the cumulative update instead.
  • To verify, check Settings > Windows Update > Advanced options > Configured update policies for Enable hotpatching when available, confirm VBS shows as running, watch for the Autopatch alert Hotpatch – VBS not running, and use the Hotpatch quality update report.

⚠️ Exam Trap: If a quality update policy has hotpatch enabled and approves monthly non-security preview updates, devices don't get the non-security updates, because installing them would break the hotpatch path. To receive them, disable hotpatch for those devices.

Reflection Question: A Windows 11 24H2 laptop with a Microsoft 365 Business Premium license restarts for its security update every single month. List three things you would check to find out why it isn't receiving hotpatches.

See how it connects
Alvin Varughese
Written byAlvin Varughese
Founder•26 professional certifications earned