How to stop Windows from restarting automatically for updates

Close-up of laptop screen showing TikTok news articles with a purple background.

Photo by UMA media on Pexels

Windows automatic restarts for updates are designed with good intentions. The system installs a patch, needs to apply it, and schedules a reboot. The problem is that Windows doesn't always pick a convenient moment, and plenty of people have lost unsaved work or had a presentation disrupted by an unexpected restart. The good news is you can control this behaviour without turning updates off entirely.

Why Windows restarts automatically in the first place

When Windows installs certain updates, particularly kernel-level security patches, it can't fully apply the changes while the operating system is running. A restart flushes everything out of memory and loads the patched code cleanly. Without that reboot, the fix exists on disk but isn't actually active yet. That matters, because keeping your software updated is one of the most reliable defences against cyberattacks, and a pending restart means you're not fully protected yet.

Windows tries to be smart about timing. It looks at when you normally use the computer and schedules restarts during what it calls "active hours." In practice, this heuristic misfires often enough to be genuinely annoying.

Set active hours correctly

Active hours tell Windows the window of time when you're likely to be using the computer. Windows won't restart automatically during this period. The default window is only 8 hours wide, which isn't enough for most people who work long days.

To adjust active hours on Windows 11, open Settings, go to Windows Update, then select Advanced options, and find Active hours. You can either let Windows detect your activity automatically or set a custom range. The manual range now supports up to 18 hours, which covers most working and evening schedules. Set it to match your real hours: if you're at your desk from 8 am to 11 pm, use that range.

Windows 10 follows the same path: Settings, then Update & Security, then Windows Update, then Change active hours.

Schedule restarts manually

Once an update is downloaded and ready, Windows shows a "Schedule the restart" option in the Windows Update panel. Use it. Pick a specific time overnight or during a lunch break when you won't be in the middle of anything. Windows respects scheduled restarts reliably, so this is the most direct way to stay in control.

If you see a notification that a restart is pending and no schedule prompt appears, go to Settings, Windows Update, and look for the Restart options button. It's there even when the notification doesn't offer it directly.

Pause updates temporarily

If you have a critical deadline and need a few days without any update activity at all, Windows lets you pause updates for up to 5 weeks. Go to Settings, Windows Update, and select Pause updates. Pick a date that suits you. When the pause expires, Windows will immediately resume downloading and may restart sooner than usual to catch up, so plan accordingly.

Pausing is a short-term measure. Leaving a Windows machine unpatched for more than a few weeks does carry real security risk, and if you've run into update errors before, it's worth reading about common Windows 11 update errors and how to fix them before the pause expires.

Use metered connection to slow automatic downloads

Marking your network connection as metered tells Windows to hold off on downloading large updates automatically. This works on both Wi-Fi and Ethernet. Go to Settings, Network & Internet, select your current connection, and toggle Set as metered connection to On. Windows will still show available updates but won't download them in the background, which means no restart prompt until you decide to install manually.

This approach suits laptops on mobile data or people on slower connections. On a home broadband plan it's a blunter tool than active hours, but it works.

Group Policy and Registry options (Windows Pro and above)

Windows 11 Pro, Enterprise, and Education editions include Group Policy settings that give finer control over restart behaviour. Open the Local Group Policy Editor by pressing Win + R and typing gpedit.msc. Navigate to Computer Configuration, Administrative Templates, Windows Components, Windows Update, and then Manage end user experience. The setting "No auto-restart with logged on users for scheduled automatic update installations" does exactly what it says: Windows won't restart while any user is signed in.

On Windows 11 Home, Group Policy isn't available, but the same result is achievable through the Registry. The key is HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU. Set a DWORD value named NoAutoRebootWithLoggedOnUsers to 1. Edit the Registry carefully: a wrong change in the wrong key can cause real problems, so back up the Registry before making any changes.

What not to do

Disabling the Windows Update service entirely is a common suggestion online and it's a bad one. It stops security patches from arriving, which leaves the system exposed to vulnerabilities that attackers actively scan for. It also eventually causes Windows to behave unpredictably, since some components expect the update mechanism to function.

Similarly, deferring feature updates through Windows Update settings is fine for a few weeks, but deferring quality updates (which carry security fixes) beyond their supported window means running code with known, public vulnerabilities. The goal is to control when you restart, not to avoid updating.

The right balance

The most practical setup for most people combines three things: an 18-hour active hours window that covers your whole working day, a habit of manually scheduling restarts for overnight when an update is ready, and a pause when a genuinely time-sensitive period demands it. That keeps patches arriving on a reasonable schedule without Windows deciding a restart is a good idea mid-sentence.

If your machine does restart unexpectedly and something breaks, that's a separate problem. Rolling back a Windows update that caused an issue is straightforward once you know the steps.