Windows security updates within three days: what an SME does without a large IT team
On Nov 17, 2026, Microsoft began treating a PC as current when it receives the security update within three days. The default deadline in Windows Update and Intune is now one day. Here is what an SME without a large IT team can do this week.
Photo: Clint Patterson · on Unsplash
On November 17, 2026, John Cable published Rethinking Windows management for modern IT on the Windows IT Pro Blog. The new recommendation is this: for a device to be considered Current, it should be on the latest security update within three days of release. To help get there, the default quality-update deadline in Windows Update client policy and in Microsoft Intune update rings is now one day.
For someone running a small or medium business in Brazil or Latin America, without a large IT team, the practical effect is a shorter clock on the work PC. Automatic updates turned on, a weekly look at the PCs that cannot stop, a time to restart, a copy of the files before the month’s package, and the name of who to call if something breaks. The rest of this text is the detail, with the source of each figure.
This text does not describe a CGT client. The facts come from the November 17 post, from Nuno Costa’s November 5 text on the Windows Experience Blog, from the 9to5Windows report of November 18, and from the KB5132059 page, dated November 10, 2026.
What changed on November 17
A quality update, in Microsoft’s vocabulary, is the monthly security package. A Windows version change, such as moving to 26H2, is a separate decision. John Cable’s post talks about both and separates the timelines. Pausing the new version does not stand in for installing the security package.
Cable writes that AI is changing the pace of vulnerability discovery for defenders and attackers alike. At that pace, shortening the time between an available fix and a device that still does not have it matters more. The post says that moving faster cannot mean giving up the testing, visibility, and control IT needs. The ask is a smaller window, with someone still in charge of the change.
The sentence that changes an SME’s calendar sits in the middle of the text, in the Windows Autopatch section. Under the updated recommendations, devices should be on the latest security update within three days of release to be considered Current. The default quality-update deadline, in Windows Update client policy and in Intune update rings, is now one day. Separate grace periods can be set for quality updates and for feature updates. The post does not publish the deadline that applied before, and it does not say that Microsoft rewrote every policy already saved. Whoever administers the account has to open the policy and read the number that is stored there.
In the same section, Autopatch flags settings that could leave devices Exposed or Critical. The report shows how many devices are affected and what to change, and it warns when an update ring is created or edited. That applies to companies that already use Autopatch. An SME that only turns on Windows Update on each laptop does not see that screen.
Hotpatch is part of the same announcement. Cable asks organizations to use hotpatch updates to apply eligible security updates without a restart, and says that hotpatch, finer approval of quality updates, device risk exposure, and driver update reporting are generally available in Windows Autopatch. Nuno Costa’s November 5 text adds that, on an eligible device, hotpatching can apply monthly security updates without a restart, while standard cumulative baseline updates are still required periodically. A company that is not on Autopatch should not count on that path.
Why leaving it until next week weighs more
On November 5, 2026, Nuno Costa published A new standard for vulnerability management in the AI era. The text says AI is accelerating vulnerability discovery on both sides. It can help defenders find and fix vulnerabilities earlier. It can also help attackers search for vulnerabilities before fixes are available and analyze published fixes after release. Once the update and the associated guidance are public, the fix itself can be analyzed. Microsoft’s sentence is that attackers might be able to use a published fix to better understand the underlying vulnerability and develop an exploit, potentially within hours.
John Cable’s post points to that November 5 text as the reading on why timely updates matter more. 9to5Windows, on November 18, 2026, reports the same turn with a direct formulation: attackers using AI can reverse-engineer a fix into an exploit within hours.
9to5Windows also reports the October 2026 volume: 1,123 Windows-only patches, compared with 134 in October 2025. Nuno Costa’s text, on Microsoft’s site, does not use that pair of figures. It says the October 2026 monthly security update addressed more than 1,100 Common Vulnerabilities and Exposures (CVEs) for Windows. The two reports point at the same month. The closed figure of 1,123 against 134 stays as 9to5Windows’s report.
The same November 5 text publishes a piece of Microsoft diagnostic data from August 2026. Among a measured Windows enterprise sample, fewer than half of devices had installed the security update two weeks after release, and about one in four still had not installed the update after four weeks. 9to5Windows reports the same two-week finding: in a sample of enterprise devices, fewer than half had a given security update two weeks after release.
9to5Windows also records a line from Jeremy Chapman, a Microsoft 365 director, from July 2026. According to that report, Microsoft “no longer recommends delaying monthly updates for three days or more,” because “the risk is real.” The next quotation in the same report: “If you’re not delivering critical quality updates with security fixes until a couple of weeks after they’ve been issued, that’s ample time for attackers using AI to find and exploit known security gaps.”
For an SME, the risk of waiting weeks is that named interval. The fix is already public. The finance PC, the one that issues invoices, and the laptop of the person who approves a payment are still without it. There is no client case in this text, and no loss figure. What is here is Microsoft’s new criterion and the August figure for how long a measured sample of companies still took.
An update can also fail
Waiting weeks is the larger risk in the November 17 recommendation. Updates also break things, and Microsoft documents that on the package’s own page.
KB5132059, dated November 10, 2026, is the security update for Windows 11 version 26H1 (OS Build 28000.3501). The page lists fixes for problems earlier updates had left behind:
- Remote Desktop (RDP) connections might fail because of a certificate mismatch after the October 2026 non-security preview update. KB5132059 marks that as fixed.
- USB Audio 1.0 devices might fail to start and display error code 10 in Device Manager after a recent security update. The same page marks that as fixed.
The page also describes a security change: the client offers NTLM message signing by default for connections that are not anonymous. Microsoft says this helps reduce exposure to NTLM relay attacks and adds auditing for connections that are not using signing.
The same page is not only a list of fixes. On November 17, 2026, a known issue was added: on servers, SQL Server linked-server connections might remain open after the updates released on October 13, 2026, and later. Microsoft points to a temporary mitigation through business support and says it is working on a resolution. That is a server, not the reception laptop. It is a reminder that an update’s page stays open after release day.
The simple plan, for a company without an IT team, fits in two checks before the month’s package. The copy of the company’s files opens a real file, off that PC. On the PC that cannot stop, a restore point was created before the install. If an essential program stops after the update, the restore point is the way back that does not depend on finding an uninstall option. When Windows still offers removal of that quality update, it appears in the history at Settings > Windows Update > Update history. Not every package leaves that way. The KB5132059 page explains that Microsoft combines the servicing stack update with the cumulative package. The restore point made beforehand is the plan the company controls.
In October, a Windows Server security update affected mail on on-premises Exchange servers. The blog post summarizes Microsoft’s notice and the guidance not to uninstall that patch in a hurry. Today’s subject is the work PC. The parallel is the record: an update fixes, sometimes it gets in the way, and a wait of weeks is what the November recommendation treats as exposure.
What to do this week
A short path, without buying a new tool. The menus below are in English, as in Microsoft’s documentation. On a localized Windows, the same items appear translated.
- On each work PC, open Settings > Windows Update. Confirm that automatic updates are on and that a pause is not set to last for weeks. Write down the date of the last quality update that installed.
- Agree on the restart. Many security updates finish only after the PC restarts. Pick a time when that can happen, at the end of the day or during a break, and do not leave the restart notice sitting there. Hotpatch, on an eligible PC and inside Windows Autopatch, covers some security updates without a restart, as the November 17 post describes. A company that does not use Autopatch still restarts. Baseline cumulative updates, in the November 5 text, are still required periodically even where hotpatch exists.
- Once a week, the same person looks at the PCs the company cannot lose: finance, invoicing, the register, the laptop of the person who decides. The pass is short. Date of the last install, whether Windows is asking for a restart, whether the last attempt failed. The length is not a Microsoft figure. It is a routine that fits a company without an IT team.
- If the company already has Microsoft 365 Business Premium, Intune is part of that license and the update rings are where the deadline lives. Read the number stored on the ring. The default announced on November 17 is one day for the quality update. A deferral of weeks can still be in the policy if someone saved it earlier: the post announces the default and does not say that every old policy was rewritten. A company that uses Windows Autopatch reads the Exposed and Critical warnings when creating or editing a ring, and the report of how many devices those settings affect.
- Test on one PC only when that PC is critical. The store system, finance, or a machine that cannot stop in the middle of the day can receive the update a day before the others, to see whether the main program opens. The rest stay on automatic. A three-day window does not fit a two-week test queue.
- Before the month’s update, confirm the copy of the files and, on the critical PC, a restore point. Searching Windows for “Create a restore point” opens the screen. The file copy and the restore point do not stand in for each other.
- List what was left behind. A laptop in a drawer, a reception PC that sleeps all day, a machine with a repeated install failure. A PC that is off does not get the fix. Write down who turns each one on.
- Include the browser and the programs. Edge, Chrome, the PDF reader, the remote-access tool. Open them and let them update. The November 17 post describes a private preview, starting November 23, of automatic updates for supported Windows apps in Intune Enterprise App Management. Until that is the path available on the account, checking those programs stays manual.
- Write down who to call if something breaks, before the next monthly update. Name, phone number, and what that person can do: restart, use the restore point, follow Windows Update history. If there is nobody internal, arrange support beforehand, not in the middle of the error.
Frequently asked questions
Does the PC have to be updated within three days?
That is the November 17 recommendation for a device to be considered Current: the latest security update, within three days of release. The default deadline in Windows Update client policy and in Intune rings is now one day. The post does not describe a fine. It describes the criterion and the new default. If the company already stored a longer deadline, someone has to open the policy and read the number that is still there.
Does this apply to a company without Intune?
Yes. The path for an SME without a management console is automatic Windows Update on each PC, with the routine in the section above. Intune, update rings, and Windows Autopatch are the path for a company that already has that management, for example with Microsoft 365 Business Premium. The hotpatch announced on November 17 is in Autopatch, not on a laptop that only receives Windows Update on its own.
Did the November 10 update break remote access?
The KB5132059 page, for Windows 11 version 26H1, marks as fixed the Remote Desktop failure caused by a certificate mismatch, tied to the October 2026 non-security preview update. It also marks as fixed the USB Audio 1.0 failure with error code 10. The same page, updated on November 17, records a known issue on SQL servers. For an office PC, the use of that page is different: the update fixes an older failure, and the documentation stays open. The restore point made beforehand is still the company’s plan.
Does waiting two weeks still fit?
The August 2026 figure, in Nuno Costa’s text, shows that fewer than half of a measured sample of enterprise devices had the security update two weeks after release. 9to5Windows reports Jeremy Chapman’s line: a couple of weeks is ample time for attackers using AI. The November 17 recommendation puts “current” at three days, with a default deadline of one day.
Does this describe a CGT client?
No. There is no case, client, or CGT result in this article.
Related reading
A copy of the files and rolling the system back are different subjects. On the blog, why “we have a backup” is not enough is about a copy that has to stay out of reach of an attack. The Windows 11 26H2 settings copy keeps preferences and the list of Microsoft Store apps, and it does not replace the files or a restore point.
How CGT can help
CGT supports small and medium businesses with work PCs and Microsoft 365, within the scope agreed with each client: see whether automatic updates are on, what the Intune ring does when the license is there, which machines were left off or failed, and what the plan is if an update gets in the way of an essential program. Human support is Monday to Friday, 08:00 to 18:00, São Paulo time.
Want this routine on the company’s computers? Meet CGT and talk to us.
Sources: Windows IT Pro Blog — Rethinking Windows management for modern IT, John Cable (Nov 17, 2026), Windows Experience Blog — A new standard for vulnerability management in the AI era, Nuno Costa (Nov 5, 2026), 9to5Windows — Microsoft Warns Hackers Can Exploit Windows Security Vulnerabilities Within Hours (Nov 18, 2026), and Microsoft Support — KB5132059, Windows 11 version 26H1 (Nov 10, 2026).
Cover photo: Clint Patterson, on Unsplash.


