F5F Stay Refreshed Software Operating Systems Check system settings or update options to turn off automatic reboots following updates.

Check system settings or update options to turn off automatic reboots following updates.

Check system settings or update options to turn off automatic reboots following updates.

T
Tanhu
Member
212
09-05-2016, 01:40 AM
#1
Whenever theres an update that needs restart Win 10 says that you must restart either now or leave your pc and it will automatically restart on inactive hours. I don't want either. How do I disable this?
T
Tanhu
09-05-2016, 01:40 AM #1

Whenever theres an update that needs restart Win 10 says that you must restart either now or leave your pc and it will automatically restart on inactive hours. I don't want either. How do I disable this?

C
62
09-06-2016, 10:26 AM
#2
It’s difficult to completely stop Windows 10 automatic updates and reboots. You should keep them enabled since they usually allow enough time before a restart. Which version of Windows 10 are you running?
C
Cute_Almond0v0
09-06-2016, 10:26 AM #2

It’s difficult to completely stop Windows 10 automatic updates and reboots. You should keep them enabled since they usually allow enough time before a restart. Which version of Windows 10 are you running?

X
XxvalentinoxX
Member
67
09-06-2016, 11:15 AM
#3
Normally it'll reboot outside "active hours" (typically overnight) which is too soon if you're running the systems 24/7 and don't check it every day. I think 7 days grace would be better. I had a few reboot overnight since yesterday was patch day and I forgot about it. And just to make it more annoying, it downloaded yet another update today and that wants to reboot too. Why not do it in one MS? Anyway, the easiest solution I found is to add the WU servers to a hardware firewall blocklist. This is great if you have a lot of computers and saves you needing to apply it on each one. MS have a list of WU servers on their website somewhere, intended for admins to allow WU to work behind a firewall, but the reverse is also true. Temporarily disable this once a month after the 2nd Tuesday which is when the routine patch day is. There is a risk you may miss out of cycle updates, and this will also break MS store if you care at all about that. I stopped using this method only because my previous firewall died and I haven't got around to replacing it yet (using ISP provided router, eww!).
X
XxvalentinoxX
09-06-2016, 11:15 AM #3

Normally it'll reboot outside "active hours" (typically overnight) which is too soon if you're running the systems 24/7 and don't check it every day. I think 7 days grace would be better. I had a few reboot overnight since yesterday was patch day and I forgot about it. And just to make it more annoying, it downloaded yet another update today and that wants to reboot too. Why not do it in one MS? Anyway, the easiest solution I found is to add the WU servers to a hardware firewall blocklist. This is great if you have a lot of computers and saves you needing to apply it on each one. MS have a list of WU servers on their website somewhere, intended for admins to allow WU to work behind a firewall, but the reverse is also true. Temporarily disable this once a month after the 2nd Tuesday which is when the routine patch day is. There is a risk you may miss out of cycle updates, and this will also break MS store if you care at all about that. I stopped using this method only because my previous firewall died and I haven't got around to replacing it yet (using ISP provided router, eww!).

T
Th3o4oR
Junior Member
7
09-06-2016, 07:00 PM
#4
For advanced control over Windows Update, configure WSUS to select specific updates at your convenience. GP can be adjusted to delay reboots up to 14 days. The reboot issue likely stems from a cumulative monthly update, but some drives may require separate scheduling due to differing release timelines.
T
Th3o4oR
09-06-2016, 07:00 PM #4

For advanced control over Windows Update, configure WSUS to select specific updates at your convenience. GP can be adjusted to delay reboots up to 14 days. The reboot issue likely stems from a cumulative monthly update, but some drives may require separate scheduling due to differing release timelines.

R
RageGlitch
Posting Freak
771
09-07-2016, 01:20 AM
#5
I manage several systems, and not all are Pro. That adds extra work unless I switch to a fully managed corporate network. The second one was a .net preview. I didn’t request it, but it installed automatically.
R
RageGlitch
09-07-2016, 01:20 AM #5

I manage several systems, and not all are Pro. That adds extra work unless I switch to a fully managed corporate network. The second one was a .net preview. I didn’t request it, but it installed automatically.

G
190
09-19-2016, 06:36 PM
#6
To avoid automatic restarts, my schedule changes frequently so I might be running during off-hours.
G
gustavbengters
09-19-2016, 06:36 PM #6

To avoid automatic restarts, my schedule changes frequently so I might be running during off-hours.

M
MineTurtel
Member
62
09-19-2016, 07:21 PM
#7
Which Windows 10 edition are you running? Most tasks fit within group policy settings, allowing updates only when activated in certain versions. You can simply restart after completing your work, which usually provides ample time before the system enforces a restart.
M
MineTurtel
09-19-2016, 07:21 PM #7

Which Windows 10 edition are you running? Most tasks fit within group policy settings, allowing updates only when activated in certain versions. You can simply restart after completing your work, which usually provides ample time before the system enforces a restart.

A
appies
Member
160
09-21-2016, 10:06 AM
#8
I believe you activated that feature: disable it, similar to the image shown. This setting appears in: Settings > Update & Security > Windows Update > Advanced Options.
A
appies
09-21-2016, 10:06 AM #8

I believe you activated that feature: disable it, similar to the image shown. This setting appears in: Settings > Update & Security > Windows Update > Advanced Options.