Stop the "Windows update madness" on WS2016!
Dear Microsoft Windows Server team. We would like _complete control_ over when we would like our our WS2016 to install windows updates! No more slow / timeconsuming server restarts because of "Getting Windows ready. Do not turn off your computer" messages when we just would like a quick restart of a production server.. No more TiWorker.exe using 100% of a CPU core during "*********" and so on.. And please fix the issues with '2017-08 Update for Windows Server 2016 for x64-based Systems (KB4035631)' asap. Thank you.
KjB
shared this idea
16 comments
-
Kerry
commented
Just had to do updates on a server. One of the VMs failed the same update 4 times, I have had to remove the VMs NIC to get the VM to finally update. 14 hours for updates on the physical box and 2 VMs later and I am annoyed.
-
DepressiveUser
commented
Windows 2016 update horrible. BareMetal ... VMs ... doesnt matter, runs for hours. Microsoft, why make all more worse, than it is anyway. Year after year. We pay for this software, its not linux where **** is free (and you know, linux is not ohnly ****). I think every customer could expect a little of value for the money. Its the same over years now: 66% of what you doing ... is scrap. Features, nobody wants. AppStore on a Server, and so on ... ARGHHHHH. Sorry, but thats the truth. Slowly i'm beginning to hate you, and a long time ago I was really pleased about your products. Unforunately you've lost the sense for what a customer stands and what your role is in that game. And mor unfortunaly there is no real way out of this misery ...
-
DScholle
commented
I have been having a problem with the update database becoming corrupted. So, the updates install slowly, the server reboots slowly, then the server needs to rollback slowly and reboot (slowly) again. Then I have to intervene to fix the update database. What a headache!!!
-
PhilS
commented
I have to agree with all of the comments here. I have several 2016 Hyper-V hosts running 2016 VM's. To patch a single host and 4 VMs can take more than a full day. Why?
The build process has now become impossibly long. It now takes two days to build a 2016HV host, and deploy 2 or 4 VM's on it. Most of that time is waiting for patches to install. -
Davide
commented
The era of Windows Server (with a GUI) end with 2012 R2.
-
Karl W-E.
commented
David, Update log is available only via Powershell. This is a change.
Anonymous try to enable software vGPU on ESX / Hyper-V this should heal your GUI slowness and greatly improve the performance on Citrix for free.On the topic I am sad that Server 2016 does not offer Edge, as a substitute to IE as IE is still loading while other products are already ready.
So my plea is: faster updates (better utiliziation and GPOs to steer dism / installer worker)
implement Edge on Servers, please. -
David Saphier
commented
Give us back out WindowsUpdate log as well.
-
Anonymous
commented
Agree with other people comments here.
Brand new install 2016 servers and then get an update that takes over 2 hours to install and then machine reboots and takes another 35-40 minutes.
We also notice the graphical interface on 2016 as very slow compared to previous - is this why Microsoft is pushing Powershell and nano-server as the GUI is hopelessly poor at performance on 2016. During all the patching etc, CPU, disk usage are barely noticeable -
Anonymous
commented
Really sick of waiting 2 hours every month to apply these updates. I have a 3 node Hyper-v cluster, (which freaks out when you use Cluster Aware Updating) and doing one node at a time means 6 hours of applying updates.
-
Anonymous
commented
Microsoft needs to give us more control over windows update scheduling (ie monthly reboots) and also make these updates install quicker. 3 hours I've been staring at the Getting Windows ready. Don't turn off your computer screen with 2% CPU and 1gb memory being consumed. What is actually going on? Probably nothing but to **** us off.
-
Anonymous
commented
I agree with Matt, the more I use WS2016, the more I hate it as a server because of the Windows Update problem. Every month I have to wait for it to download updates from WSUS (also a WS2016 server) and while the download from WSUS isn't too bad, it's the super long install of the cumulative updates with the extra long reboot of the server that's a glaring huge problem.
As we continue to replace our older Windows servers with WS2016, updates become more and more time sensitive and while Microsoft may find this hard to believe, we and many, many, other organizations don't have the budget for a fleet of servers with redundancy to the Nth degree to be able to afford to have the downtime imposed by the Windows Update madness that's going on. If we're going to be forced to spend the money on the computing resources to be able to house all those servers, we may as well start deploying more Linux servers where we have FULL CONTROL over what the server does.
The cost of the extra computing power to have all the server redundancy can be easily funneled into converting things over to Linux, and I'm sure Microsoft is already painfully aware that there are likely more public facing servers on the Internet that run other OS's that aren't Windows based.
-
Matt
commented
I have to agree with all the comments I have read and I feel everyones pain, everyday.
The frist suggestion here is this: QUIT treating Server 2016 like it is someones home PC. I am fairly sure that MS2016 Datacenter is NOT a home product.
- GET RID OF DEFENDER - I can provide screen shots of machines utilizing defender with
thousands and thousands of infections - IT HAS NO PLACE ON SERVER !!!
- Next, just to refresh Microsofts memory - Server products are used for critical operations
STOP focring updates and restarts let us choose the times so we can notify critical operation
that restarts are going to happen - you are putting the jobs of professionals in jepardy - We
are tired of being blamed for Microsofts Dictatorship style of ruling!
- FIX IE - just because you have it so locked down upon install does NOT make it a secure
product. Especially when we have to disable all the securtity just to go to Microsofts websites!
You really could learn a thing or two from Chrome and Firefox - they put their customers first.
- STOP moving our tools around, you may enjoy Easter Egg hunts with you kids - BUT NOT at
work in critical situations. You are HURTING the engineers that support you ! Give us
(YOUR MCSE's) the choice of wanting to search for how to do everything or not. Your
screwing with our jobs.
- Try fixing the tens of thousands of bad links on your websites. I really hate the click here for
details or help and all I get is half-@#$ ****.
- How can you have an event ID and source for event log errors that have no information on
them?
- STOP trying to force ****** apps like Defender and IE on us, now it's edge and skype that
you can't unistall.
- Make your System Center products (that you forced us to buy with Datacenter) perform like
your competors tools. After 20 years, DPM still can not restore a single mailbox, let alone a
single email! Everyone else does it, are you to incompetent to give your engineers what they
need? I would be ashamed to have my company name on any of your System Center
Products1I could go on for days writing this, I have been supporting Microsoft WIndows since 3.1 and NT 3.1. So I definately have the background to say "You Treat those of us that support you LIKE TRASH". I am probably one of your oldest engineers, and never, not once, have you ever listened to us. Well, maybe getting us the business verion of XP, but nothing else.
The one thing that keeps Microsoft going is it's engineers and our recomendations. I have news for you, we are fed up with your ****, your incompetence and your forcing garbage on us. Start fixing your products, or you'll end up just like Tandy as we, the engineers start pushing to remove all Microsoft products from our environments.
NOT A JOKE - you better start asking us, the engineers what we want and need in new versions of Server. We use, support, fix, recomend and buy your products. It's time to put us first, Linux is starting to become very attractive.
Sorry to rant here, but I am sick and tired of all the bull. Auditing starts again next week and we will get ripped apart because of Microsoft yet again!
-
. -
HK Schütze
commented
I'm also! The time to restart a SERVER-Machine shouldn't be incalculable!!!
-
Anonymous
commented
Same here, this is ludicrous! There's no reason why we, the admins, should not have full control over updates on a SERVER regardless of the server edition.
-
Richard P.
commented
Also here: Very Long time for installing updates on 2016 Servers.
For example: 2 identical Servers with Exchange 2016 in VM. One took only 1h 45m for cumulative November update, the other one ist working(?) on the same update since 7 hours!
No remarkable CPU / Disk / LAN activity.
Seems, MS has forgotten how to write programs at all. -
binary
commented
#MeToo
I experinece exaclty the same problem on all my Server 2016 machines at work and in my private lab environment. Even with nvme SSD it take about 8 minutes to pass "Getting Windows ready" screen. On SAN without SSDs it takes about 50 min and for our 2012R2 servers everything is done in only 20 min.