Ya, I’m sure the AI code isn’t helping, but is it materially any different? I spent way too many long nights trying to unfuck Windows servers after updates failed to install correctly. And that was well before the AI Slop Boom. Even more fun is when the update reported installing correctly but the Nessus scans came back showing the old version of DLLs still in the System32 folder. There is a reason no one installs Windows patches on day 1. At minimum, you give them a week to let the foolhardy and fanboys get their disks slapped by Microsoft, again.
Going back to my days supporting Window 2000/2003, I remember working in environments where management had decreed that we would not install updates ever, because of too much downtime due to bad updates. Even today, updating in OT environments can be very difficult due to shitty software running on really old versions of Windows. At least that stuff can usually be kicked off the network and left to rot in isolation.
There is a reason no one installs Windows patches on day 1.
I love how they earned this reputation, so rather than repair that reputation, the next move was to force update their users whether they like it or not.
I remember working in environments where management had decreed that we would not install updates ever. . .
That’s…definitely a decision that puts a lot of trust in Microsoft’s security. Lol
Windows Update:Damned if you do, Damned if you don’t.
I remember working in environments where management had decreed that we would not install updates ever. . .
That’s…definitely a decision that puts a lot of trust in Microsoft’s security. Lol
It was a very different time. Security was still something that happened mostly at the network perimeter, and even then not much. Routers without firewalls were very common and things like SQLSlammer were much more possible.
Ya, I’m sure the AI code isn’t helping, but is it materially any different? I spent way too many long nights trying to unfuck Windows servers after updates failed to install correctly. And that was well before the AI Slop Boom. Even more fun is when the update reported installing correctly but the Nessus scans came back showing the old version of DLLs still in the System32 folder. There is a reason no one installs Windows patches on day 1. At minimum, you give them a week to let the foolhardy and fanboys get their disks slapped by Microsoft, again.
Going back to my days supporting Window 2000/2003, I remember working in environments where management had decreed that we would not install updates ever, because of too much downtime due to bad updates. Even today, updating in OT environments can be very difficult due to shitty software running on really old versions of Windows. At least that stuff can usually be kicked off the network and left to rot in isolation.
I love how they earned this reputation, so rather than repair that reputation, the next move was to force update their users whether they like it or not.
That’s…definitely a decision that puts a lot of trust in Microsoft’s security. Lol
Windows Update: Damned if you do, Damned if you don’t.
It was a very different time. Security was still something that happened mostly at the network perimeter, and even then not much. Routers without firewalls were very common and things like SQLSlammer were much more possible.