How to Stop Automatic Updates in Windows 10

Nobody actually objects to security patches. What people object to is a machine that decides on its own that now is a good moment to restart, or a feature update that lands the week of a deadline and quietly moves everything you use. That is a fair complaint, and it has real answers. It also has a lot of fake ones, which is most of what makes this topic exhausting.

So let me split it cleanly. First the things that genuinely work, in the order I would try them. Then, plainly, the things that do not, so you do not spend an evening on a registry key that Windows quietly puts back overnight.

Pause updates: the supported off switch

Start here. It is built in, it works on every edition including Home, it needs no registry editing, and it buys you five clear weeks. For most people who are simply mid-project and want to be left alone, this is the entire answer.

Metered connection: the longest-running trick that still works

Marking a network as metered tells Windows you are paying per gigabyte. It responds by holding back non-essential downloads, including most Windows updates and Microsoft Store app updates, indefinitely: no 35-day limit.

Group Policy deferral on Windows 10 Pro

If you are on Pro, Enterprise or Education, this is the proper tool. It lets you separate the two kinds of update: quality updates, which are the monthly security fixes, and feature updates, which are the twice-yearly releases that move things around. Deferring the second while accepting the first is exactly the right posture for most people.

If the real problem is the restart, fix the restart

It is worth stopping to ask what you are actually annoyed about, because a lot of people reach for update-blocking when they do not need it. For most of us it is not the patching at all, it is losing an unsaved session to a reboot nobody asked for. That has its own setting, and it is a far better trade than switching off security fixes.

• Active hours — under Windows Update, set the window during which Windows will never restart automatically. It covers up to 18 hours a day, and on recent builds Windows can set it from your usage pattern.
• Restart options — schedule a specific time for a pending restart, once per pending update.
• Notify before restarting — under Advanced options, turn on Show a notification when your PC requires a restart.

The methods that no longer work

These are still near the top of the search results, and they are worth naming precisely so you can recognise one and close the tab. Every one of them worked at some point, which is exactly why they refuse to die.

• Disabling the Windows Update service (`wuauserv`). Set it to Disabled in services.msc and it will be running again within hours. Update Orchestrator Service and Windows Update Medic Service exist specifically to repair this, and Medic is protected against being disabled itself.
• Renaming or deleting the SoftwareDistribution folder. Windows simply rebuilds it and re-downloads. It is a legitimate troubleshooting step for a stuck update, but it is not a block.
• Third-party "update blocker" utilities. Most work by doing one of the two things above, and inherit the same fate. Some also disable Defender updates as a side effect.
• The `wushowhide` troubleshooter. Microsoft's own tool for hiding a specific update still functions, but it is per-update rather than a general switch, and it does not survive a feature update.

If an update has already installed and broken something

Worth saying plainly, because it catches people out: blocking future updates does nothing about the one that already landed and broke something. Removing an installed update is a separate job. Go to Settings → Update & Security → Windows Update → View update history → Uninstall updates, then pause updates afterwards, or Windows will cheerfully reinstall the same one within a day or two.

If Windows will not start at all after an update, that is a recovery problem rather than an update problem — work through the escalation order in the guide to repairing Windows without reinstalling, and treat a factory reset as the last step rather than the first.

A related annoyance: the space updates leave behind

Feature updates keep your previous installation in C:\Windows.old so the upgrade can be rolled back, and that folder is routinely twenty gigabytes or more. Windows deletes it automatically after ten days. If you need the space sooner and are confident you will not roll back, the guide on deleting temporary and update files covers doing it safely through Disk Cleanup rather than by dragging the folder to the Recycle Bin, which will not work.

What we would actually do

Set active hours honestly, so the machine never restarts while you are using it. On Pro, defer feature updates by 90 to 180 days and leave quality updates alone — you avoid the disruption of a brand-new release without leaving security holes open. On Home, use pause when you have a deadline and let it lapse afterwards. Turning updates off entirely on an internet-connected machine trades a small recurring annoyance for a genuine and growing risk.