The Windows 10 Updater doesn't require the PC to be idle before rebooting.
The Windows 10 Updater doesn't require the PC to be idle before rebooting.
I'm still using Windows 10 mainly because of laziness and the confusing UI in Win11. Recently, I've been running background tasks on my PC nonstop. The "Update is ready" window appeared, but I ignored it since I rarely experienced unexpected restarts. Windows actually rebooted after about an hour when I left the machine. It was busy with a VM, a download app, Visual Studio debug mode, and many open programs. CPU, GPU, and storage usage exceeded 50%, plus a full network connection. Windows detected high power consumption in Task Manager, so it didn't think the PC was idle. The real clue is the active hours setting—reflecting typical usage, not just when you're using it. If you want to prevent interruptions during overnight work, you might need to adjust this setting or use a more stable OS.
You can disable updates by adjusting the Windows Update settings a few times before they are forced. Most users notice similar behavior. The most effective approach I've tried is ensuring C: full so updates can't download. Then just accept the "insufficient space" warning and proceed. It would be helpful if updates could be forced on the next reboot instead of requiring a full system restart.
Can confirm, in theory it works, I've been using that technique on my phone/tablet for years But on my PC Windows likes to play with pagefile/hiberfil file sizes, giving or taking a couple of GB, now I'm interested how it would work if there was no space to expand.
Another effective approach is to turn off Windows updates using Winareporter. I've tried it myself and it really helps.
Windows doesn't monitor CPU activity when deciding to restart or not. Set Active Hours to prevent the system from restarting during that period, or delay updates for up to 7 days. In Settings > Update & Security > Windows Update > Advanced options, ensure "Get me up to date" is disabled (it's set by default). Restart timing varies by update type. Critical security patches require immediate restarts. Bug fixes allow a few days before the fix expires. If your version is nearing support end, it may force a restart to apply the latest build. You can pause updates and resume up to 35 days later by choosing a date, with a 7-day limit for Insiders. After resuming, Windows will check for updates immediately. This is the optimal choice among available options.
I used a metered connection with Windows to achieve this. While Comcast limits us to 1.2 TB monthly, it prevents automatic downloads and uploads. This also stops all Microsoft services from running without manual installation of updates as needed.
Sure, glad the suggestion helped! I tried this method before with Wi-Fi, but Ethernet didn’t work. Now I know there’s a limit for Ethernet, so I’ll use it more often now. If possible, I’d like to highlight both answers as solutions since the first one was really detailed and helpful for beginners, but I’m hoping everyone reads them carefully.