How Windows updates are changing for your clinic
By David Freeland3 min read · 
A screen that says you’re behind
Your team is having trouble with the EHR, so they connect with the EHR company’s support. The agent checks the computer and says, “It looks like your computer hasn’t installed updates in a while.” The Windows Update screen seems to agree. It says the last updates were installed 132 days ago.
Your team calls your IT company, worried the computer has fallen behind. It hasn’t. Your IT company installs updates on that computer every month with its own tool. The Windows Update screen doesn’t show them.
The worry was misplaced, but it raises a good question. Who decides when updates install at your clinic, and how would you know they did? It’s a good time to ask. Microsoft is changing how Windows updates work.
What Microsoft is changing
Beginning with updates released July 28, 2026, Windows 11 is moving to one restart a month. Updates that need a restart, like driver and firmware updates, now wait for the monthly security update and install alongside it. Drivers are the small programs that run hardware like printers. Then the computer restarts once, outside its active hours when it can. Active hours are the hours you tell Windows the computer is in use.
Security updates keep their normal monthly schedule. Emergency fixes and Microsoft Defender’s updates on known threats still install right away. People can also hold off updates for as long as 35 days.
There’s a catch. Microsoft says this change is “currently only available to devices not managed by IT departments.” It covers Windows 11 versions 24H2, 25H2, 26H1, and 26H2. So if an IT company manages your clinic’s computers, nothing changes for them yet. Your IT company still decides how updates happen.
Two ways your IT company can run updates
Both ways can keep your computers current. They differ in who presses install and in what your team sees.
Fully managed by your IT company. Your IT company’s update tool checks each computer, installs updates on a schedule, and restarts it after hours. Your IT company can approve each update and hold back one that’s causing problems before it reaches every computer. It also gets a report on every machine. The trade-off: depending on the tool, the Windows Update screen may not show those installs. A computer with every update installed can still look months behind, like the one the EHR agent saw.
Windows, with your IT company’s oversight. Windows installs its own updates, under rules your IT company sets. Those rules include a deadline to install, a short grace period before a forced restart, the clinic’s working hours, and whether staff can pause updates. For monthly updates, Microsoft recommends a deadline of 1 day and a grace period of 2 days. It says no more than 7 days should pass from an update’s release to its install. Your IT company gets an alert if a computer falls behind, and the Windows Update screen stays accurate. The trade-off: less control over any one update. If an update causes trouble, your IT company pauses updates instead of holding back that one.
Neither way is wrong. What matters is that someone is watching every computer and acts when one falls behind.
Three questions for your IT company
- Which way do you run our updates? Fully managed, or Windows with your oversight. Either can work. Ask how you’d know if a computer missed one.
- How fast do security fixes land? Microsoft’s own guidance is no more than 7 days from release. Fixes for flaws attackers are already using should come first. The federal agency CISA calls them “the top priority for remediation.”
- What will my team see on screen? If the Windows Update screen may look out of date, your team should know before it worries. Ask, too, whether staff can pause updates, and for how long.
Microsoft is starting this change on computers no IT department manages. A short talk with your IT company tells you how updates work at yours.
Last reviewed November 14, 2026.
References & statutory citations
- Microsoft: One restart a month for Windows updates (KB5121772, August 14, 2026; updated October 19, 2026). (opens in a new tab)
- NinjaOne: NinjaOne Patching: Windows OS Patch Management (an example of an IT company’s update tool; undated; viewed November 14, 2026). (opens in a new tab)
- Microsoft: Enforce compliance deadlines for updates (Microsoft Learn, updated September 28, 2026). (opens in a new tab)
- Microsoft: Policies for update compliance, activity, and user experience (Microsoft Learn, updated July 2, 2026). (opens in a new tab)
- Microsoft: Common policy configuration mistakes for managing Windows updates (Windows IT Pro Blog, January 19, 2021; updated February 2, 2023). (opens in a new tab)
- Microsoft: What are Windows Update client policies? (Microsoft Learn, updated August 20, 2026). (opens in a new tab)
- Cybersecurity and Infrastructure Security Agency (CISA): BOD 22-01: Reducing the Significant Risk of Known Exploited Vulnerabilities (November 3, 2021). (opens in a new tab)