The reality is they probably don’t know the full scope or root cause and are going off of limited reporting coming from their beta channels.
But they likely determined the impact was low enough that they could still ship the update while they investigate further.
There are similar known issues reported in the update KBs all the time that sound much worse to me as an admin but are as equally low impact in the end. But they’re not as easy for the layperson to latch onto like these low-effort “VPN no worky” articles.
Regardless, none of this absolves IT of the responsibility of testing patches.
I don’t disagree with anything you’ve said. But I know Microsoft can do better, because they used to before they gutted their documentation team. That’s only one symptom I’ve seen of their recent decline though.
Lately I’ve had support engineers answering support cases with stuff they clearly got from Copilot or ChatGPT because they do things like giving me PowerShell cmdlets to run with parameters that don’t even exist and never have. I even recently had one engineer argue with me and tell me I didn’t run the command correctly when I pointed out to him that he gave me incorrect syntax, parameters that don’t exist, so I had fixed it and ran what was really needed to get the data he was after. I got the case reassigned to an engineer who didn’t have his head up his ass. But it’s not a great sign.
Yep totally. The documentation is downright wrong so much more today than it used to be. It’s all written like they pawned it off on a junior engineer, who then threw shit at the wall until they got it working, then that process becomes the official documentation.
And don’t get me started on Copilot hallucinating Powershell cmdlets.
With support it’s become kind of a game to see how quick you can get to T2. My tactic is to passive aggressively point out how their first response shows a complete lack of understanding of the topic, then directly request escalation.
The reality is they probably don’t know the full scope or root cause and are going off of limited reporting coming from their beta channels.
But they likely determined the impact was low enough that they could still ship the update while they investigate further.
There are similar known issues reported in the update KBs all the time that sound much worse to me as an admin but are as equally low impact in the end. But they’re not as easy for the layperson to latch onto like these low-effort “VPN no worky” articles.
Regardless, none of this absolves IT of the responsibility of testing patches.
I don’t disagree with anything you’ve said. But I know Microsoft can do better, because they used to before they gutted their documentation team. That’s only one symptom I’ve seen of their recent decline though.
Lately I’ve had support engineers answering support cases with stuff they clearly got from Copilot or ChatGPT because they do things like giving me PowerShell cmdlets to run with parameters that don’t even exist and never have. I even recently had one engineer argue with me and tell me I didn’t run the command correctly when I pointed out to him that he gave me incorrect syntax, parameters that don’t exist, so I had fixed it and ran what was really needed to get the data he was after. I got the case reassigned to an engineer who didn’t have his head up his ass. But it’s not a great sign.
Yep totally. The documentation is downright wrong so much more today than it used to be. It’s all written like they pawned it off on a junior engineer, who then threw shit at the wall until they got it working, then that process becomes the official documentation.
And don’t get me started on Copilot hallucinating Powershell cmdlets.
With support it’s become kind of a game to see how quick you can get to T2. My tactic is to passive aggressively point out how their first response shows a complete lack of understanding of the topic, then directly request escalation.