Here we go again - MS confirms problem with update halting systems from starting

It's logical - the word secure together with Microsoft has for a long time been synonymous with not opening. Like outlook attachments :D
 
I'm pretty neutral when it comes to OS's. I like them all and hate them all about the same. I have to say though that Microsoft has given me a lot more headaches in the last year than any other OS. Oracle Linux server? Never has issues. CentOS production server? I have to occasionally check to make sure its running because I'll go weeks without even a status notification. Month old Windows Server 2016 with our reporting services on it? Wants to reboot every other day. Takes it upon itself to reboot itself if I ignore it. OSX Server Box? Just kidding nobody uses OSX server lol.
 
I'm pretty neutral when it comes to OS's. I like them all and hate them all about the same. I have to say though that Microsoft has given me a lot more headaches in the last year than any other OS. Oracle Linux server? Never has issues. CentOS production server? I have to occasionally check to make sure its running because I'll go weeks without even a status notification. Month old Windows Server 2016 with our reporting services on it? Wants to reboot every other day. Takes it upon itself to reboot itself if I ignore it. OSX Server Box? Just kidding nobody uses OSX server lol.

Sounds like you don't keep your centos server/packages up to date then..... They have to be patched at least weekly to keep up with the high crit vulns that keep getting flagged by the security scans. Then you have the dependency hell with packages as they get updated / break other tools etc.

And you should get your GPO setup properly for the 2k16 server. Update checks and automatic reboots can all be controlled from there and disabled. Once that's done, it's typically a misconfigured 3rd party update tool that causes the reboots.



And no one should be pushing patches on day 1 to production. Should always wait a week and test in dev environments first so you don't push a broken patch. This applies to all systems, not just windows.
 
Sounds like you don't keep your centos server/packages up to date then..... They have to be patched at least weekly to keep up with the high crit vulns that keep getting flagged by the security scans. Then you have the dependency hell with packages as they get updated / break other tools etc.

And you should get your GPO setup properly for the 2k16 server. Update checks and automatic reboots can all be controlled from there and disabled. Once that's done, it's typically a misconfigured 3rd party update tool that causes the reboots.



And no one should be pushing patches on day 1 to production. Should always wait a week and test in dev environments first so you don't push a broken patch. This applies to all systems, not just windows.
I thought everyone did testing in prod ;)
 
My friend has automatic updates turned off, yet his Win10 bluescreened mysteriously on friday :D
 
My friend has automatic updates turned off, yet his Win10 bluescreened mysteriously on friday :D
I have a friend with Linux, yet his computer is constantly kernel paniking and/or being stuck on normal operations. What gives?!
 
My windows defender and firewall became disabled this week (I don't know why) and I couldn't enable it from Services in Admin Tools. Next Windows Store and XBox Live app didn't work. Not sure if this is related to this issue but this was the 3rd time this happened to me and the two times before led to reformat... This time around, luckily a combination of System Restore, Media Creation Tools and Powershell helped resolve this issue and Windows Defender and firewall are working again. Windows 10 has been the worst OS in my experience and every update is nerve racking... Never had these issues with W7 or Vista or XP
 
I have many Win10s and Server 2016s. Before that I had many Win7's. I have to admit I never had an issue more now than before with Win7s and 2008 R2s. I remember an issue with Win7 where it failed to install an update once and I had headaches. I had this once with Win10 2 years ago. I had to try twice before it installed Ok. Then I think it was some problem with WU servers. Never happened since then. In the other hand, WU proved to be troublesome for Win7 few years ago when Win10 was at its peak. It was updating slowly as hell (as 1-2 days).
 
Back
Top