Stop Windows Updates? You Can Pause for 35 Days

An update is about to restart your machine in the middle of something, and you want it to stop, permanently if possible.

Windows will let you pause, and it will not let you stop. The pause is generous, it is one click, and understanding why it expires is what stops you fighting it every month.

I read the update settings on this laptop before writing, and one of them turned out to explain a lot about when updates arrive.

What Microsoft actually offers

One control, and the number attached to it is larger than most people expect.

⭐ Microsoft states the route on its pause updates page: "Select Start > Settings > Windows Update. Select Pick a date on the Pause updates control."

⚡ And the limit: "You can pause updates for up to 35 days from the current date."

⚠️ Five weeks is a long pause. It covers a project, a trip, or a month you cannot afford a restart.

⛔ It is not a switch, it is a date. You pick when it ends rather than turning something off.

What happens when it runs out

Microsoft says this plainly, and it is the part people are not told.

⭐ Microsoft says: "If you do nothing, updates resume automatically when the pause expires to help keep your device secure and reliable."

⚡ There is no rolling pause. It ends, and Windows catches up on everything it missed.

⚠️ That catch-up is bigger than a normal month. Expect a longer install and a restart you did not plan.

⛔ So end a pause deliberately rather than letting it lapse on a busy day. That one habit removes the ambush.

The setting that decides when it restarts

This is the one worth changing, and almost nobody does.

⚡ Active hours tell Windows when not to restart you. It will still install, it just waits to reboot.

⭐ This machine is set to 11 to 5, read from its own update settings. That wraps past midnight, so it is an eighteen hour window.

⚠️ Widen yours to match when you actually use the machine. Settings, Windows Update, Advanced options, Active hours.

⛔ This is the setting that solves the real complaint. Most people who want to stop updates only want to stop the restart.

What this machine reports

Read rather than assumed, and the ordinary configuration is ours to report.

⭐ Updates are not paused here. The pause expiry value is unset, which is what an untouched machine looks like.

⚡ The update service is stopped and set to start manually. When I checked, that was normal, and not a machine with updates disabled.

⚠️ A stopped service alarms people who go looking. Windows starts it when it needs it and stops it again.

⛔ So a stopped update service is not evidence of anything. Reading a state is only useful if you know what normal looks like.

The things people do instead, and what they cost

All four are worse than the pause, and saying which is ours.

⚡ Disabling the update service is the popular one. Windows re-enables it, and in the meantime you get no security fixes at all.

⭐ Metered connection was the old trick. It delays some updates and not the important ones.

⚠️ Group Policy edits are a Pro feature. Home does not have that editor at all.

⛔ And third party update blockers break in ways that are hard to undo. They also stop the fix for whatever they broke.

When you genuinely should pause

Four cases, and they are all short term.

⭐ The night before something that matters. A presentation, a deadline, a flight.

⚡ When a known issue is affecting your build. Release health names those with dates.

⚠️ On a machine you cannot easily restart, such as one recording or rendering for days.

⛔ And on metered mobile data, where a feature update is a real cost.

When pausing is the wrong answer entirely

Two of these are urgent rather than optional.

⚡ If updates are failing rather than annoying you, pausing hides the fault. Errors have their own numbers and meanings.

⭐ If an update never finishes, that is a different problem. Nine fixes, commonest first.

⚠️ And if your version is close to its end date, a pause is the last thing you want. 24H2 runs out in October.

⛔ Pausing is for timing, not for avoiding. Anything else and you are storing the problem up.

What to do at the end of the 35 days

Three steps, and the middle one is the one people skip.

⭐ Pick an evening rather than letting it expire on its own. You choose the restart instead of Windows choosing it.

⚡ Install everything in one go, then restart, then check again. A second round is common after a long gap.

⚠️ Back up first if it has been a long pause. Somewhere for your files to live is worth ten minutes.

⛔ Then set active hours properly so you do not need the next pause. That is the actual fix.

Status: update settings read on this laptop on 29 August 2026, Windows 11 Home 25H2, against Microsoft's own pause updates page. ⛔ Nothing was paused, changed or installed, no update was deferred, and no account or identifier is published.

How long can you pause Windows updates?

Microsoft's limit is 35 days from the current date, set through Settings, Windows Update, and the Pick a date control on Pause updates. It is a date rather than a switch, so you choose when it ends rather than turning updates off.

Can you stop Windows updates permanently?

Not through any supported setting. Microsoft says updates resume automatically when the pause expires, to keep the device secure and reliable. The methods people use to block them permanently either get undone by Windows or leave the machine without security fixes.

How do I stop Windows restarting my PC?

Set active hours rather than pausing. Windows will still install updates but will wait to restart outside that window. It is under Settings, Windows Update, Advanced options. Most people who want to stop updates only actually want to stop the restart.

The Short Version

• Microsoft's pause limit is 35 days from the date you set it.
• It is a date, not a switch. There is no permanent off.
• When it expires, Windows resumes and catches up on everything missed.
• Active hours stop the restart without stopping the updates.
• This laptop is set to 11 to 5, which wraps midnight and covers eighteen hours.
• Updates are not paused here and the update service is stopped, which is normal.
• Disabling the service, metered tricks and blockers all cost more than they save.
• End a pause on an evening you choose rather than letting it lapse.

Where to Next

Set active hours first. That fixes the restart complaint without touching updates at all.

Use the pause only when you have a real date to protect, and note when it ends.

Come back to it on an evening of your choosing rather than letting it expire mid morning.

Install everything, restart, then check again, because a long gap usually needs two rounds.

And if a pause of yours ended with an update that broke something, say which build in the comments. That pattern is worth collecting.