The Windows operating system playbook for the first 72 hours
- 0 to 4 hours: 4 steps
- 4 to 24 hours: 3 steps
- 24 to 72 hours: 2 steps
- Hours elapsed: the bar under the cells
Checklist to print
0 to 4 hours4 steps, due by hour 4
- 1
Security lead, hand-off
Read Microsoft's own exploit flag, then CISA's entry. Download the month's CVRF file with curl -s https://api.msrc.microsoft.com/cvrf/v3.0/cvrf/2026-Sep -o 2026-Sep.xml (about 36 MB for September 2026) and find the CVE's Exploit Status threat. For CVE-2026-85880, CVE-2026-81963 and CVE-2026-68820 it reads "Publicly Disclosed:No;Exploited:Yes;Latest Software Release:Exploitation Detected". Then read dateAdded, dueDate and forensicTriage for the same CVE in the KEV feed at https://www.cisa.gov/sites/default/files/feeds/known_exploited_vulnerabilities.json. All three were added the day Microsoft published, with a due date 14 days later and forensicTriage No.
Done at
- 2
Platform engineering, hand-off
Fix one build floor for each Windows release before anyone queries a host. A cumulative update carries earlier fixes, so the September 2026 update for a release clears every one of the three flaws that applies to it. Floors: Windows 10 22H2 10.0.19045.7725 and 21H2 10.0.19044.7725 (both KB5122878); Windows 10 1809 and Server 2019 10.0.17763.9245 (KB5122876); Windows 10 1607 and Server 2016 10.0.14393.9512 (KB5123099); Server 2022 10.0.20348.5622 (KB5122882); Server 2012 R2 6.3.9600.23398 (KB5123066); Server 2012 6.2.9200.26349 (KB5123065); Windows 11 23H2 10.0.22631.7582 (KB5122880); Windows 11 24H2 10.0.26100.9445 and 25H2 10.0.26200.9445 (both KB5124008); Windows 11 26H1 10.0.28000.2954 (KB5124012); Server 2025 10.0.26100.33438 (KB5122871). Windows 11 24H2 and Server 2025 share build 26100 with different revisions, so compare each to its own row. CVE-2026-85880 is listed for Windows 10 and Server 2012 to 2022, CVE-2026-81963 for Windows 11 and Server 2025, and CVE-2026-68820 for all of them.
Done at
- 3
Platform engineering, hand-off
Read the build and the restart state off every host in one pass: Invoke-Command -ComputerName (Get-Content .\hosts.txt) -ScriptBlock { $v = Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion'; [pscustomobject]@{Host=$env:COMPUTERNAME; Type=$v.InstallationType; Release=$v.DisplayVersion; Build="$($v.CurrentBuild).$($v.UBR)"; RebootPending=(Test-Path 'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update\RebootRequired')} } | Export-Csv builds.csv -NoTypeInformation. Match each row to its floor by Type and CurrentBuild, then compare the revision after the dot. Intune or ConfigMgr inventory gives the same two numbers if you cannot reach hosts with remoting.
Done at
- 4
Security lead, hand-off
Order the hosts by how many people can run code on them. First: Remote Desktop session hosts, VDI pools, jump hosts, shared lab and kiosk machines and build agents. Second: servers that open files from outside, such as mail, upload and document-conversion servers. Third: administrator workstations. Last: single-user laptops. List who can sign in with net localgroup "Remote Desktop Users" and qwinsta /server:HOST.
Done at
- 1
4 to 24 hours3 steps, due by hour 24
- 5
Platform engineering, hand-off
Read Microsoft's Known Issue entry for your floor KB before the pilot. The September CVRF lists one for 9 of the 10 September KB articles (all except KB5123065 for Server 2012). Pilot on IT machines plus one host from each tier for 4 hours, then release the first wave. Do not hold a wave for a cosmetic issue, and do hold it for anything that stops sign-in, printing, a line-of-business app or the agent that reports patch state.
Done at
- 6
Platform engineering, hand-off
Force install and restart on workstations. With Intune, create an expedite policy for the floor update; it needs Windows Pro, Pro Education, Enterprise or Education (not LTSC), telemetry set to at least Required, and the wlidsvc service running. Without it, use Windows Update deadlines: set ConfigureDeadlineForQualityUpdates (range 0 to 30 days) to 1 and ConfigureDeadlineGracePeriod (range 0 to 7, default 2) to 0. Group Policy path: Computer Configuration > Administrative Templates > Windows Components > Windows Update > Manage end user experience > Specify deadline for automatic updates and restarts. Microsoft: "After the deadline passes, restarts will occur regardless of active hours and users won't be able to reschedule." These two values are our suggestion for an exploited flaw, not Microsoft's.
Done at
- 7
Platform engineering, hand-off
Handle servers by hand, not by deadline. Microsoft's restart guidance for servers is Configure Automatic Updates option 7, notify to install and notify to reboot. Take the tier-one servers from the ordering step first. Patch one node of a cluster at a time, or let Cluster-Aware Updating do it with Invoke-CauRun -ClusterName NAME -MaxFailedNodes 1 -RequireAllNodesOnline. Restart domain controllers one at a time and run repadmin /replsummary before the next.
Done at
- 5
24 to 72 hours2 steps, due by hour 72
- 8
Security lead, hand-off
Rerun the build query every 4 hours and sort the hosts below the floor into two groups. RebootPending true means the update is installed and the host is waiting: contact the owner and schedule the restart. RebootPending false means the update never installed: check that the host reported in, that its update source approves the KB, and that the disk has room. For laptops that stay off the network, create one Intune compliance policy for each release, assigned by an Entra dynamic device group such as device.deviceOSVersion -startsWith "10.0.19045", with Minimum OS version set to that release's floor, and require a compliant device in Conditional Access.
Done at
- 9
Security lead, hand-off
Write an exception for every host that cannot reach its floor: a release missing from the floor table, a host under a change freeze, or an application that breaks on the update. Each exception names the owner, the date the host will reach the floor, and the compensating control from the no-fix section. Note that the KEV due date is 14 days after the fix, so the exceptions list is what you hand over on day 3 and not on day 14.
Done at
- 8
Windows zero-days in this set arrive with the fix already out. Microsoft marked each flaw Exploited:Yes in the monthly release that carried the update, so the first hour of the clock is Patch Tuesday itself, with a cumulative update waiting and a restart pending. All three are local privilege escalations (CVSS vector AV:L, PR:L): the attacker already runs code on the host and the flaw takes them to SYSTEM. CVE-2026-85880 in ALPC is built to leave an AppContainer, the sandbox that holds browser content and Store apps. CVE-2026-68820 in the WinSock driver afd.sys is a race condition, which Microsoft rates High attack complexity and still marks exploited. CVE-2026-81963 in the Update Stack is a link-following flaw that is listed only for Windows 11 and Windows Server 2025.
What makes this hard is bookkeeping, not discovery. The fix is a cumulative update with a different build number for each of a dozen Windows releases. The KB article number proves little, because a later cumulative update carries the same fix under another KB. And the update does nothing until the host restarts. This page covers the operating system. The browser that may carry the attacker's first foothold is covered in the endpoint fleet playbook.
When no fix exists yet
For these three flaws Microsoft lists no workaround, and neither Microsoft nor CISA publishes a log signature, file name or network indicator. When a host cannot take the update, the only levers cut the supply of local code. Remove who can sign in: list the Remote Desktop Users group and take out accounts that do not need it, with Remove-LocalGroupMember. Block unapproved programs with Windows Defender Application Control or AppLocker. For CVE-2026-85880, keep browsers and document readers current, because the attack starts inside an AppContainer. The costs are real: people lose access to shared hosts, and unsigned line-of-business software stops starting under application control.
Decide by who can run code, not by the severity label. Take a host offline, or close it to all but a named administrator, when several unrelated users or untrusted files reach a local session and the update cannot be installed inside the KEV window of 14 days. Leave a server online when nobody signs in interactively and it opens no outside files, and patch it in the next window inside the due date. Microsoft's Exploited:Yes flag means someone already has the second stage of an attack, so the open question is whether they can get the first stage on that host.
CVE-2026-68820, CVE-2026-85880 and CVE-2026-81963 worked through, hour by hour
Two Patch Tuesdays four weeks apart carried three exploited privilege flaws. August 2026 fixed the WinSock driver flaw CVE-2026-68820 for every supported release. September 2026 fixed the ALPC flaw CVE-2026-85880 for Windows 10 and Server 2012 to 2022, and the Update Stack flaw CVE-2026-81963 for Windows 11 and Server 2025. The times below start at the CVRF release time, which the file gives as 07:00 with no time zone.
| When | What happened | Source |
|---|---|---|
| 11 Aug 2026, 07:00 | Microsoft's August release lists CVE-2026-68820 with Exploited:Yes and Publicly Disclosed:No. It carries 13 fixed KB articles, from KB5120386 for Server 2012 to KB5121000 for Windows 11 26H1. Windows 10 22H2 needs 10.0.19045.7663 (KB5120249). | source |
| 11 Aug 2026 | CISA adds CVE-2026-68820 to the KEV catalog the same day, with forensicTriage No and a due date of 25 Aug 2026. | source |
| 25 Aug 2026 | KEV due date for CVE-2026-68820, 14 days after the fix. | source |
| 8 Sep 2026, 07:00 | Microsoft's September release (999 CVEs) lists CVE-2026-85880 and CVE-2026-81963 as Exploited:Yes, both with revision 1.0. Windows 10 22H2 now needs 10.0.19045.7725 (KB5122878); Windows 11 24H2 needs 10.0.26100.9445 (KB5124008). | source |
| 8 Sep 2026 | CISA adds both September flaws to KEV the same day with forensicTriage No and a due date of 22 Sep 2026. | source |
| 11 Sep 2026, 07:00 | Hour 72 of the clock started on 8 Sep. Microsoft publishes revision 1.1 of CVE-2026-81963, which updates an acknowledgement and is marked informational, so nothing needs redoing. | source |
| 16 Sep 2026, 07:00 | Microsoft revision 1.1 of CVE-2026-85880 corrects the temporal Exploit Code Maturity value in the CVSS vector. The change is informational and the base score stays 7.8. | source |
| 22 Sep 2026 | KEV due date for CVE-2026-85880 and CVE-2026-81963, 14 days after the fix. | source |
The September floor for Windows 10 22H2 is 62 revisions above the August floor (7725 against 7663), and for Windows 11 24H2 it is 277 above (9445 against 9168), so a host that took the August update still needed the second restart. A fleet that waits for each KEV due date spends 14 days, or 336 hours, on an exploited build after each fix: 28 days across the two months. Following the steps above, the restart is forced within about a day on workstations and the straggler list is closed by hour 72, which leaves 6 days across the two months and finishes 264 hours (11 days) before the September due date.
Related pages
Sources
- Microsoft Security Response Center CVRF, August 2026 release (CVE-2026-68820: exploit status, fixed builds, KB articles), read 19 Nov 2026
- Microsoft Security Response Center CVRF, September 2026 release (CVE-2026-85880 and CVE-2026-81963: exploit status, fixed builds, KB articles, known issues, revision history), read 19 Nov 2026
- CISA Known Exploited Vulnerabilities feed, catalog version 2026.11.18, read 19 Nov 2026
- Microsoft Learn, Policy CSP Update (ConfigureDeadlineForQualityUpdates, ConfigureDeadlineGracePeriod), read 19 Nov 2026
- Microsoft Learn, Manage device restarts after updates, read 19 Nov 2026
- Microsoft Learn, Manage Windows quality updates in Intune (expedite requirements), read 19 Nov 2026
Last reviewed 19 Nov 2026.