Windows finally lets you pause updates forever. Please don't

There is a particular silence that happens when the front desk computer restarts in the middle of a Tuesday morning. The tech stops typing. The woman holding the beagle looks up. Somebody says "it does this sometimes," and then four people stand there watching a percentage climb while the phone rings.

That was a vet clinic in Zionsville in June. Eleven minutes, and four appointments stacked up behind it.

On July 14, Microsoft shipped something that fixes that, and it also shipped a way to make your shop's computer a much bigger problem than a slow Tuesday. The update is KB5101650. It landed on Windows 11 versions 24H2 and 25H2, and it changes how pausing works: you pick a date on a calendar, Windows leaves you alone until that date, and when the date arrives you can pick another one. No limit on how many times. No backlog to install first.

So yes, you can now pause Windows updates forever. Do it for one week at a time instead, and set the thing you should have set two years ago.

What actually changed on July 14

Pausing updates is not new. Getting out of the pause is the part that changed.

Before this update, you could pause for up to 35 days, and then Windows made you install everything that piled up before it would let you pause again. That forced checkpoint is gone. Now you open Settings, then Windows Update, and pick an end date up to 35 days out. You can go back in the middle of a pause and pick a new date without taking the pending updates. There is no cap on how many times you renew.

It applies to Windows 11 versions 24H2 and 25H2, all editions. Home matters most here, because Home never had the deferral controls Pro users could reach through Group Policy. A salon running Windows 11 Home on the scheduling PC now has the same lever a corporate IT department has.

Why does this matter if all you run is a register?

Your card reader probably isn't Windows. Toast and Clover run Android. Square runs its own hardware.

The Windows machine in a small business is the other one. The back office PC with QuickBooks Desktop on it. Mitchell 1 Manager SE at an auto shop, which requires Windows 10 21H2 or Windows 11, 64-bit, and runs nowhere else. Dentrix at a dental office. The practice management software at that clinic in Zionsville. The PC driving the menu board over the counter, or the TV in the waiting room, or the machine where the schedule lives.

Those computers run one important program and then sit untouched for months. Nobody logs into them at night. Nobody watches for the little restart notice in the corner. They are exactly the machines that reboot at 10:40 on a Tuesday, because 10:40 on a Tuesday is when Windows finally got a window it thought was quiet.

So should I just pause it forever?

No, and I want to give you the honest version of why, because the scary version is mostly wrong.

That same July 14 batch fixed about 570 flaws. Three were zero-days and two of those were already under active attack when the patch shipped. That sounds like an emergency. It wasn't one for you. The two under attack were in Active Directory Federation Services and SharePoint Server, which your clinic does not run. The third, a BitLocker bypass, needs somebody standing in your building holding your computer.

For a six-person shop, the July batch was not urgent.

The problem is that you don't get to make that judgment call each month, because you won't be making it. A pause holds the whole bundle, and Windows gives you no way to take the security fixes and skip the interface changes you didn't ask for. The month that does matter to you, a browser hole or a bug in the file type your bookkeeper opens twice a week, arrives while the pause is still rolling and nobody has looked at that screen since August.

A pause is not a decision that you don't need the update. It moves the decision to a morning when nobody is looking.

The October date that settles the argument

Windows 11 version 24H2, Home and Pro, stops getting updates on October 13, 2026. Enterprise and Education editions get another year, until October 12, 2027. Most small businesses are on Home or Pro.

If you're on 24H2 and you keep renewing a 35-day pause through the fall, you will roll past that date on a version Microsoft has stopped patching, and you won't notice, because not noticing is the entire point of a rolling pause.

Checking takes ten seconds. Press the Windows key, type winver, hit enter. A small box tells you the version. If it says 24H2, you need to be on 25H2 before mid-October, and unmanaged Home and Pro machines get moved to 25H2 automatically once you let them.

What to do this week

Set active hours first. This is the real fix and almost nobody in a shop has touched it. Settings, then Windows Update, then Advanced options, then Active hours. Switch it from Automatically to Manually and enter your open hours. Microsoft caps the window at 18 hours, so 6am to midnight is as wide as it goes. Windows will not restart inside that window. Do this on every machine in the building and the mid-shift reboot mostly stops happening, with nothing paused and nothing at risk.

Then use the pause for one specific week. The State Fair runs August 7 through August 23 this year, and if that stretch is your busiest, that's what this feature is for. Open Windows Update, pick August 24, and put "install Windows updates" on the calendar for that morning so it arrives as a chore instead of a surprise.

Install on purpose. Pick a slow morning, come in twenty minutes early, click install, and go make coffee while it reboots with nobody waiting on you. An update you scheduled costs twenty minutes. An update that ambushes you costs a Tuesday, plus four appointments.

One footnote if your shop runs Dell

Microsoft is holding KB5101650 back from some Dell machines with certain Intel processors, citing unexpected shutdowns, degraded performance, heat, and battery drain. There's no published date for when the hold lifts.

If your Dell hasn't offered you the July update, that is why, and it's deliberate. Don't go find the standalone installer and force it on.

The clinic in Zionsville set active hours from seven to seven and hasn't thought about it since. Nobody there knows what KB5101650 is or that a pause calendar exists. That seems like the right outcome to me.

---

Sources

#	Source	What it backed up
1	July 14, 2026: KB5101650 (OS Builds 26200.8875 and 26100.8875)	Release date, OS builds, applicable Windows 11 versions, and the 24H2 Home/Pro end-of-updates date.
2	Keep your PC up to date with active hours (Microsoft Support)	How to set active hours, and the 18-hour cap on the window.
3	Microsoft July 2026 Patch Tuesday fixes massive 570 flaws, 3 zero-days	The 570 count, the two exploited zero-days in AD FS and SharePoint Server, and the BitLocker bypass.
4	Windows 11 Adds Renewable 35-Day Update Pause Option	The renewable pause mechanics, Home and Pro coverage, and the Dell hold.
5	Windows 11 24H2 Home and Pro reach end of support in 90 days	The October 13, 2026 cutoff and the automatic move to 25H2 on unmanaged devices.
6	Mitchell 1 / ShopKey Manager SE installation guide	Manager SE requires Windows 10 21H2 or Windows 11, 64-bit.
7	Indiana State Fair	The August 7 to August 23, 2026 fair dates.