AnswersPublished20 sources
Windows Hotpatch Reboots Return in September and October 2026
The September 8, 2026 Windows security update will require a conventional cumulative update and reboot—even on hotpatch enrolled devices—because it changes system components that cannot be updated while Windows is run... The exception affects eligible devices using Windows Autopatch, Windows 11 Hotpatch, and Windows...
Published byEdited with GPT-5.6 LunaImages generated with GPT Image 1.5
Research answer
Key takeaways
- The September 8, 2026 Windows security update will require a conventional cumulative update and reboot—even on hotpatch enrolled devices—because it changes system components that cannot be updated while Windows is run...
- The exception affects eligible devices using Windows Autopatch, Windows 11 Hotpatch, and Windows Server Hotpatch.
- IT teams should notify users, review Intune restart deadlines and active hours, and reserve maintenance windows for both September and October.
AI Prompt
openai.comCreate a landscape editorial hero image for this Studio Global article: What has Microsoft announced about the temporary suspension of restart-free hotpatching during the September and October 2026 Windows update. Article summary: Microsoft says the September 8, 2026 security release will be delivered as a conventional cumulative (baseline) update—not a hotpatch—because it changes system components that cannot be safely updated while Windows is ru. Topic tags: general, general web, user generated. Style: premium digital editorial illustration, source-backed research mood, clean composition, high detail, modern web publication hero. Use reference image context only for broad subject, composition, and topical grounding; do not copy the exact image. Avoid: logos, brand marks, copyrighted characters, real person likenesses, fake screenshots, UI text, readable text, watermarks, charts with fa
Microsoft is temporarily interrupting the expected restart-free Windows hotpatch cycle. The September 8, 2026 security release will arrive as a conventional cumulative, or baseline, update and will require a reboot—even on devices enrolled in hotpatching—because some security changes affect system components that cannot be safely updated while Windows is running. 2
6
That makes September an exceptional reboot month. October will also require a restart, but for a different reason: it is the regularly scheduled quarterly baseline month in Microsoft’s servicing cycle. 7
14
What changes in September
Hotpatch is designed to apply eligible monthly security updates while Windows continues running. Baseline updates are different: they include broader cumulative changes and require a restart to complete installation. 7
Microsoft’s September advisory treats the release as a baseline update for hotpatch-enabled systems because the security improvements include changes that cannot be applied in memory. Organizations should therefore plan for temporary device or service unavailability rather than assume that hotpatch will eliminate the September reboot. 2
6
Which devices are affected?
The exception applies to hotpatch-enrolled devices using:
- Windows Autopatch
- Windows 11 Hotpatch
- Windows Server Hotpatch
Windows Autopatch began enabling hotpatch updates by default for all eligible managed devices with the May 2026 Windows security update. That means the affected population is potentially broader than an opt-in pilot group, although the available material does not provide a numerical count of affected Intune endpoints. 17
25
Eligibility still matters: the rule applies to devices enrolled in and capable of receiving hotpatch updates, not to every Windows device in an organization.
September and October reboot schedule
The normal quarterly pattern uses one baseline month followed by two hotpatch months. Microsoft’s published schedule lists January, April, July, and October as baseline months, with the following two months designated for eligible restart-free security updates. 7
14
For the September–December 2026 period, the published release schedules show this practical sequence:
- September: Baseline update; restart required because of the exceptional component changes.
2
- October: Scheduled baseline update; restart required.
10
- November: Hotpatch update expected; no restart for eligible devices.
- December: Hotpatch update expected; no restart for eligible devices.
The key operational point is that September and October both need maintenance planning. September is the temporary departure from the expected hotpatch behavior; October is the normal quarterly reset of the servicing baseline.
Does installing the September update remove enrollment?
No. Installing the standard September update does not remove a device from hotpatch enrollment. The device remains enrolled and should be able to receive later eligible hotpatch releases once the servicing schedule returns to its normal pattern. 2
Administrators should distinguish between receiving a baseline update and leaving the hotpatch program. The September reboot changes how that release is installed; it does not cancel the device’s enrollment.
What enterprise IT administrators should do
1. Inventory hotpatch-enabled devices
Identify Windows client and server deployment rings that use Windows Autopatch, Windows 11 Hotpatch, or Windows Server Hotpatch. Include Autopatch-managed Intune devices whose hotpatch setting was enabled by default.
2. Tell users to expect a September restart
Update service-desk scripts, user notifications, change records, and compliance communications. September should not be presented as a normal no-reboot hotpatch month.
3. Review Intune restart controls
Check active hours, restart notifications, deadlines, and enforcement behavior. Intune policies can allow users to restart immediately or schedule a restart, while also enforcing the restart after the configured deadline. 18
4. Reserve two maintenance windows
Plan restart-capable maintenance windows for both September and October. For servers and production workloads, validate application shutdown, startup, failover, and recovery procedures before deployment.
5. Reconcile compliance expectations
A restart requirement does not mean the September update should be deferred. The baseline release is required to apply the relevant security-component changes. Treat September as an exceptional baseline month, October as the planned quarterly baseline, and November as the point at which restart-free hotpatching is expected to resume.
Bottom line
Microsoft’s message is straightforward: hotpatch enrollment does not guarantee a reboot-free update every month. The September 8, 2026 release requires a conventional cumulative update and restart because of changes that cannot be applied while Windows is running. October already carries its normal baseline reboot, while eligible devices are expected to return to restart-free hotpatch updates in November. 2
6
10
13
30
Studio Global AI
Continue your research
This page includes a source-backed answer you can continue inside Studio Global.
People also ask
What is the short answer to "Windows Hotpatch Reboots Return in September and October 2026"?
The September 8, 2026 Windows security update will require a conventional cumulative update and reboot—even on hotpatch enrolled devices—because it changes system components that cannot be updated while Windows is run...
What are the key points to validate first?
The September 8, 2026 Windows security update will require a conventional cumulative update and reboot—even on hotpatch enrolled devices—because it changes system components that cannot be updated while Windows is run... The exception affects eligible devices using Windows Autopatch, Windows 11 Hotpatch, and Windows Server Hotpatch.
What should I do next in practice?
IT teams should notify users, review Intune restart deadlines and active hours, and reserve maintenance windows for both September and October.
Sources
learn.microsoft.comHotpatch updates | Microsoft Learn
github.comwindows-itpro-docs/windows/deployment/windows-autopatch/manage/windows-autopatch-hotpatch-updates.md at public · MicrosoftDocs/windows-itpro-docs