As was foretold, we've added advertisements to the forums! If you have questions, or if you encounter any bugs, please visit this thread: https://forums.penny-arcade.com/discussion/240191/forum-advertisement-faq-and-reports-thread/
Options
I want control back - as in I decide when to do Windows Update
BlindZenDriver
Registered User regular
Registered User regular
In general Windows 10 works well for me, but I absolutely detest that I can not have complete on when to do Windows Update and especially when the system is rebooted.
While, sort of, livable with my gaming rig as I have scheduled it to update at night it really messes with my media server. I have this DIY build really frugal silent server which runs 24/7, since it does duty as not only music server but also FTP server and stuff used by friends of mine spread across the globe. This means there is really isn't any great time for Microsoft to make it reboot, but I find my self unable to stop it doing so
Any tips on what to do?
My server in question runs Win10 Pro which I know of course isn't meant as a server OS. From what I gather if the machine was on a company network with an AD and all that, then the Windows updates could be controlled by policies defined by the AD only here at home with 2-3 PC's and no Windows Server that isn't the way forward. Swapping Windows 10 for Linux is also out(I tried that but to much wasn't running well), likewise is going back to Windows 7 or 8 since that would then only be a temporary solution.
I could get a Windows Server OS using the MSDN subscription I have from work, but that then would not be legit and also my server is on the small side hardware wise (4 GB ram).
While, sort of, livable with my gaming rig as I have scheduled it to update at night it really messes with my media server. I have this DIY build really frugal silent server which runs 24/7, since it does duty as not only music server but also FTP server and stuff used by friends of mine spread across the globe. This means there is really isn't any great time for Microsoft to make it reboot, but I find my self unable to stop it doing so
Any tips on what to do?
My server in question runs Win10 Pro which I know of course isn't meant as a server OS. From what I gather if the machine was on a company network with an AD and all that, then the Windows updates could be controlled by policies defined by the AD only here at home with 2-3 PC's and no Windows Server that isn't the way forward. Swapping Windows 10 for Linux is also out(I tried that but to much wasn't running well), likewise is going back to Windows 7 or 8 since that would then only be a temporary solution.
I could get a Windows Server OS using the MSDN subscription I have from work, but that then would not be legit and also my server is on the small side hardware wise (4 GB ram).
Bones heal, glory is forever.
0
Posts
Procrastinate and shove the updates away and it'll eventually just do it for you.
Update your computer.
And for the record, Windows 10's most recent versions will wait as long as a week from the time the update is first installed to when it finally just forces a reboot. You have a week. that's plenty of time to just schedule 5 minutes for it to be down.
but still yeah, just update every night before you go to bed, ezpz
If it's just the monthly patch, yea it's usually 5 minutes. Maybe 10 on a bad day. The feature updates (i.e. 1709 to 1803) are a lot longer of course.
I'm not a Windows admin so I don't know the best way to do that, though.
If you don't mind getting your hands dirty with some scripting I'd be happy to share.
the "no true scotch man" fallacy.
I get that I should just do it and also that Microsoft has made it like that since they want everyone to update - they properly got tired of people saying bad things about their security when really a big issue was users newer upgrading.
I should perhaps given a bit more detail on my server. I sits hidden away and not connected to anything but power and LAN. Which means all interaction with it is done remotely or rather my intention is to do so and thus I do not see the update prompts except only by chance, so the effect I will know it has updated because it rebooted and one of the services it runs has not gotten back up.
Like for example the server updated two days after I went away on Holiday, since it was one of those updates that come with new stuff ie. bloatware it halted during final reboot so I could not access from my Holiday. Of course I should have checked the server before going away, but it is my computer so I should have control and not be the slave of Microsoft.
Please do share. I work in IT as a Problem Manager and while I do not get my hands into the machinery on a daily basis, doing so isn't one bit scary and in fact it can even be fun.
I use a Windows Powershell module called PSWindowsUpdate.
Then I use Task Scheduler to kick off the PSWindowsUpdate job.
Task Scheduler lets me choose a specific date and time. I can also choose whether to reboot immediately or defer the reboot.
Note that I use Windows 10 Professional and Windows 10 Enterprise, so I don't know if this method works on Home.
I'll post more details in a little while.
the "no true scotch man" fallacy.
With the exception of the feature updates, i.e. 1709-1803. Those, unfortunately can come at random. but the vast majority of the time the monthly patch comes on a predictable day.
But luckily I posted the procedure in the sysadmin thread a while back and the instructions are more or less the same
https://forums.penny-arcade.com/discussion/comment/37742738/#Comment_37742738
the "no true scotch man" fallacy.
That is totally fine. It will be a few days before I have time to thinker with things anyway, so there is no rush.
I haven't done much with Powershell in recent times, so this could be a good excuse to revisit the tool.
Thank you for all the info.
You're right about patch Tuesdays and I guess being more systematic about that can take away some of the issue. However as you mention there is still the feature updates.
I shall give the solution Ferai has come with a go, but thank you for reminding me about the Tuesday thing.