# Why Microsoft patches Windows in two days but makes third-party apps wait

By MarketScale Newsroom · Published 2026-11-21 · Software & Technology on MarketScale
Canonical: https://www.marketscale.com/industries/software-and-technology/why-microsoft-patches-windows-in-two-days-but-makes-third-party-apps-wait

> Microsoft Digital's patch policy runs two clocks: days for Windows, a buffered wait for 1,500-plus outside apps. Intune now automates the second one.

## Key points

- Microsoft's IT patches Windows within two days but intentionally defers new third-party app versions. They believe a short delay might allow vendors and researchers time to identify compromised releases.
- Microsoft Digital doesn't wait for a CVE to reach a severity threshold before updating third-party apps: disclosure can lag by months, so the current version is treated as the safest one.
- Intune's generally available auto-update lacks rollout rings or rollback capabilities. The ring, deferral, and pause controls described by Microsoft Digital pertain to an expanded version highlighted in an upcoming private preview.

A chief information security officer at one of Microsoft's large enterprise customers saw the monthly security releases growing and raised the questions every patch team now faces. Was AI surfacing more vulnerabilities? Did teams need to patch faster, push reboots earlier, and cut back on how often employees could delay a restart? And how does Microsoft handle its own machines?

Microsoft answered in a new Inside Track post from Microsoft Digital, the company's internal IT organization. It reads like a working patch policy. The stakes come from Chris Tulip, principal product manager lead in Windows Servicing and Delivery. He says the latest Patch Tuesday included as many Windows security fixes as the rest of the year combined, and he credits AI for much of the faster pace. Microsoft didn't identify the release or list the fixes, so the comparison is the company's own.

The answer to the CISO is that the strategy hasn't changed. Keep every operating system and app on the newest version, on hard deadlines. What has changed is how far that reaches and how much of it runs without a person pushing a button. The most useful detail for anyone running endpoints is that Microsoft keeps two clocks: one for software it builds, and a deliberately slower one for software it doesn't.

## Two days from release to restart

Block Field

The Windows clock starts before Patch Tuesday. Each month the Windows product group ships security updates early to about 25,000 Microsoft devices through the Windows Insider program, so breakage shows up before the broad rollout. Device compliance policies and Conditional Access, which check a device's security state before granting access to corporate resources, enforce minimum patch levels. Enforcement is staggered so employees can fix their devices without swamping the help desk.

The plumbing is Microsoft's own stack. Windows Autopatch handles updates for Windows, Microsoft 365 Apps for enterprise, Edge and Teams, with Autopatch groups putting devices on different schedules under one view. OEM driver and firmware updates arrive through Windows Update and get approved in Intune rather than packaged by hand. Servers, whether in Azure, on premises or hybrid, run through Azure Update Manager.

How aggressive is two days? For a team still running a two- or three-week cycle, Microsoft's internal deadline could serve as the benchmark to explain to leadership.

What makes a two-day restart tolerable is Windows Hotpatch, which applies most monthly security updates without a reboot. Microsoft Digital turns it on through the same Autopatch policies. The catch is eligibility, and it decides how much of the fleet actually avoids the reboot.

Block Field

For an organization with a mixed fleet of older hardware and Windows 10 holdouts, that list matters more than the deadline itself. A two-day restart rule on hotpatch-eligible devices is a monthly non-event for employees. On ineligible ones it means a forced reboot every month, and the help desk feels it.

## More than 1,500 apps on their own schedules

Microsoft Digital calls third-party software its biggest patching risk, and the cause is a deliberate choice. Most Microsoft employees are administrators on their own machines and can install nearly anything that hasn't been blocked. According to senior engineering manager Trevor Balloun, Microsoft Defender scans turn up more than 1,500 third-party apps across the environment at any given moment. Defender flags the vulnerable ones. The fixes go out through Intune, which now fully manages Microsoft's client devices, and Intune also verifies that they were installed.

Vendor disclosure is the other problem. CVE details can trail by months, and plenty of smaller vendors fix a flaw quietly and release an updated version with no announcement. Microsoft Digital therefore won't hold off until a published vulnerability passes a severity threshold. It works from the assumption that the current version is usually the most secure, and it aims to keep every installed app on the newest approved release. The patch-diffing logic runs in reverse here: when a vendor fixes something silently, waiting for a CVE means waiting for information that may never come.

Devices get 30 days from a patch's release to adopt it, after which they turn red on internal dashboards and IT follows up. For the worst cases there's no waiting at all. For about a year, Microsoft has run a process it calls tech evict: when a vulnerability is serious enough and no fix exists, Intune removes the app from every managed device and the team verifies it's gone.

Then comes the counterintuitive part. When a new third-party version does ship, Microsoft doesn't rush it. Attackers increasingly hide malicious code in an open-source component or a legitimate app's update so it arrives through a trusted channel. A brief deferral period, three days in Microsoft's example, gives the vendor and security researchers time to spot a compromised release and pull it. WinGet, the Windows Package Manager, adds its own waiting period on top. Admins can still expedite when a threat is urgent.

Microsoft's IT team gives a Windows patch two days to land, then makes a new third-party app version sit out a deferral period, because for software it doesn't build, a short wait gives vendors and researchers time to catch a poisoned release. The difference between the two clocks comes down to who controls the build pipeline, and that's a test any patch team can apply to its own catalog.

## From PowerShell scripts to a vetted catalog

Until now, Microsoft Digital forced third-party updates with custom PowerShell scripts calling WinGet. It works, but rollouts can take weeks, and when an update fails, engineers pull logs from individual machines to find out why. Senior product manager Harshitha Digumarthi describes running those scripts every month as admin overhead the new tooling should remove.

What replaces it is a feature announced at Ignite 2026: automatic app updates in Microsoft Intune Enterprise App Management, which Microsoft Digital helped build as Customer Zero. Admins choose which apps from Microsoft's Enterprise App Catalog update on their own; Microsoft Digital's starting list topped 500 titles. Devices run their own scans and display available updates to employees on the settings page. Admins place device groups into rings, define a deferral period and an install deadline, and can pause a problem rollout or speed up an urgent one. Reporting lists successes and failures with error codes that correspond to WinGet's, retries installs that failed, and marks devices that will never succeed, such as one where a policy blocks the update.

The vetting is the part a security lead will want to read twice. Each catalog app goes through the same process used for the Microsoft Store: signing certificate and hash checks, malware scans, static analysis, and a test install on a virtual machine that covers upgrade and uninstall paths. A report card tells admins what was tested and what the package changes on a device, down to shortcuts, services, scheduled tasks and registry keys. Handling apps that are open during an update, along with collecting device logs, appear on the list of future plans.

Here the stages matter. Microsoft Learn's documentation for the current auto-update feature describes a narrower tool than the Inside Track post: it covers catalog apps with a Required assignment on Windows 10 and 11, needs a subscription on top of Intune Plan 1 or Plan 2, and has no rollout rings, so a new version goes to every targeted device at once. There's no rollback or automatic uninstall either. If Microsoft finds a malicious version, it pulls it from the catalog and notifies customers, but catalog data can be cached for up to an hour and the customer still has to find and fix affected devices.

Microsoft Digital describes rings, deferral periods and installation deadlines as part of its own rollout as Customer Zero. According to Microsoft Learn, the generally available auto-update doesn't support rollout rings. A team that reads Microsoft's internal account as a list of what it can switch on this week would be getting slightly ahead of the product.

That doesn't make the generally available version a lesser choice for everyone. In an organization where employees can't install their own software, the Required-assignment path already covers everything IT deploys, and teams that want to review each version can stay on guided update supersedence. The expanded preview matters most where Microsoft's own conditions hold: local admin rights and a long tail of self-installed apps.

## Macs and phones get 14 days

Microsoft applies the same thinking to macOS, iOS and Android wherever the technology allows, but it can't control when Apple or Google ship patches or how they install. So access becomes the lever. Principal product manager John Philpott describes a standard 14-day enforcement window within a rolling 60-day patching compliance policy.

In practice, macOS and iOS users are told that after 12 days without the update, IT will install it and force a restart if needed. At 14 days, Conditional Access cuts their network access. Where the management tools fall short, Microsoft Digital takes the gap to the Intune product group. The pattern travels well: when IT can't push a patch, it can still make an unpatched device stop working on the corporate network.

## Checks to run before November 23

For endpoint and security leads weighing Microsoft's model, three checks follow from the reporting. First, count hotpatch-eligible devices before shortening restart deadlines, since eligibility decides whether a tighter clock is a policy change or a monthly reboot campaign. Second, map installed third-party titles against the Enterprise App Catalog. Microsoft Digital switched on automatic updates for more than 500 titles while Defender sees more than 1,500 apps, so even Microsoft expects a long tail that needs other handling.

Third, pick one deployment method per app. Microsoft Learn warns that an auto-update app and, say, a line-of-business assignment targeting the same software can trap devices in a race between two versions. It's also worth deciding now who can order a tech-evict-style emergency removal and how its success gets verified, before a vulnerability with no fix forces the question.

Block Field

The next marker is the November 23 private preview. The signal worth watching is whether rings, deferral periods and in-use app detection show up in Microsoft Learn's Enterprise App Management documentation as the preview moves toward general availability. If they do, the policy Microsoft runs internally becomes one more organizations can adopt.

## Sources

- [Inside Track - Keeping corporate IT software current: How we’re modernizing patch management in Microsoft Digital](https://www.microsoft.com/insidetrack/blog/keeping-corporate-it-software-current-how-were-modernizing-patch-management-in-microsoft-digital/)
- [Microsoft Intune Enterprise Application Management - Microsoft Intune | Microsoft Learn](https://learn.microsoft.com/en-us/intune/app-management/deployment/enterprise-app-management)
- [Microsoft Digital Patch Strategy: 2-Day Windows Updates, Hotpatch and ...](https://windowsforum.com/news/microsoft-digital-patch-strategy-2-day-windows-updates-hotpatch-and-intune-tech-evict.453019/?amp=1)

Tags: Microsoft Intune, Enterprise App Management, Windows Hotpatch, Windows Autopatch, Patch management, Third-party app updates

---
Source: MarketScale, https://www.marketscale.com/industries/software-and-technology/why-microsoft-patches-windows-in-two-days-but-makes-third-party-apps-wait. Published for AI indexing and citation; cite the canonical URL. Site guide for agents: https://www.marketscale.com/llms.txt
