Windows Server Updates Keep Crashing the Machine on Reboot
19 posts across 3 communities in the last 60 days; 90% from r/sysadmin.
“That's it. That's the post. Anybody else tired of the vibecoded KBs? Their OOB patch KB5129241 seems to reinstall KB5124008, which seems to kill explorer.exe upon login, amongst many other things.”
“Sorry I didn't realize that not knowing what specific update was causing this issue was going to turn so many heads in the wrong direction. I am looking for anyone who might have seen or have any more additional information as to WHAT the issue is as we have ONLY found the fix.”
“Just disable it, you will find out eventually if anything is broken. Leave it for two months disabled, document it and delete. Some random software needs some wierd things on the FW to work but if it is still in use as I said you will know about it. I found the same thing on a…”
System administrators frequently discuss patching processes, driver compatibility issues, security protocols like Secure Boot, and SNMP usage. There's a strong reliance on community knowledge for troubleshooting and staying current with updates.
SOURCES (32)
“I suggest we stop questioning people's use of acronyms and just check the patch level. You're describing exactly what September's update caused. [re: Unresponsive vm after rdp]”
“How do you manage TPM firmware updates? In the past it requires bitlocker and Vtx to be disabled , is that still the case nowadays? submitted by /u/EconomyArmy [link] [comments]”
“Hello everyone, With W11 26H2 now release, it's time for deployment planning. We just newly migrated to Co-Managed and Autopatch. I was looking at my autopatch policy where I had deferals and deadline configured and then I saw a message saying MS recommend setting defferal to 0 and use a seperate targeted policies. I went to the feature update policies and see there's less options, like no deadline. You just set when it's available or mandatory and that's about it. Is that how yo”
“We automate through RMM using the vendor tools. Windows environment. Technically our RMM can push bios updates through the Windows update management, but I haven't had a perfect record with that. Dell and HP have tools for updating the BIOS drivers etc that you can push through scripts. So vendor tools. So for the bios for example you can set up your script to not update if the version is the same. Then you can run that script manually every so often to push the updates out or have it run au”
“That's it. That's the post. Anybody else tired of the vibecoded KBs? Their OOB patch KB5129241 seems to reinstall KB5124008, which seems to kill explorer.exe upon login, amongst many other things. submitted by /u/sudobw [link] [comments]”
“Does not connect at all. Although it looks like it is intermittent. A few hours back I waa able to rdp to a sql server which has windows server 2019 OS. When I disconnected and tried to connect again it does not connect at all… It is stuck as “securing network connection””
“Is there any hassle with BIOS password or Bitlocker Sometimes yes. We've had some. Two things come to mind: firmware updates don't always suspend BL, they don't always suspend BL until the update is actually done, and re-enabling BL when you require that the recovery key is saved to AD/Entra can be a bit wonky if it doesn't find the controller at that exact time (VPN).”
“It uses the credentials of the Windows user you run it as, whether that's the logged-in account or a third-party account (shared or not).”
“WSUS is fine for us for windows updates but we have a bunch of third party updates so that’s where pdq comes in for us currently, but we need to load updates manually and push out. Essentially I just want a product that is WSUS for third party that I can simply export, then import and let it go.”
“I just want to know I’m not crazy, but I’m not hearing anything about this method of failure anywhere. It’s either MS put out a bad patch or my entire fleets servicing stack/update resources got corrupted or has been in a bad state and something in this update surfaced it. Either way, I just want to know so I can make a plan on how to proceed.”
“We've been seeing a general uptick of failing updates over the past few months, but man September is a dumpster fire.”
“Sorry I didn't realize that not knowing what specific update was causing this issue was going to turn so many heads in the wrong direction. I am looking for anyone who might have seen or have any more additional information as to WHAT the issue is as we have ONLY found the fix.”
“We utilize automatic approvals for drivers via Microsoft Autopatch with a long deferral period in our clients with Autopatch as a best practice. I haven't seen any issues that stem from it in comparison to the vendor for pushing a bad driver update. I have issues broadly with the lack of reporting that Intune provides for Drivers prior to them being deployed, which makes manual approvals incredibly difficult, especially to find out WHAT device it deploys to, as the "HP Firmware - XX.YY&”
“I analyzed this MSI (KIR), and it can be safely applied before installing the CU. I applied it using this procedure to over 100 WS 2022 and 2016 servers, and everything is working.”
“And ain't it just mind blowing that we have to go to a 3rd party website to get the KIR information , still no mitigation guidelines on Microsoft's CU known issues or release health pages. 🤦🏼♂️😠”
“Crazy you rarely have issues Windows updates themselves have bricked entire entire client's site twice for us in the last 5 months”
“Duly noted! We'll take this into consideration. This is a data point in favor of making the `windows-installer` thing in the previous comment the default. We aren't trying to scare anyone. And as a note: nearly every traditional Windows app you install already has these scary permissions by default! MSIX has them off by default and makes them sound bad so people stop using them. We use the registry for big enterprise installations, sysadmins can disable features they don’t like. We keep”
“A CVSS 10 pre-auth bug with no public IOCs is rough. At that point patching immediately seems safer than waiting on support for detection guidance.”
Software updates are major concern due to compliance issues.
“Tell me only when it runs on windows for my mi50 and it can set power limit. Otherwise I'm doing fine with native rocm 7.2 on Ubuntu.”
“I mean, it's a cluster in the first place - the 'total failure' scenarios are fairly limited already IMO. In a home lab I'm much more concerned about single points of failure. But when I can take 30 nodes, split them into 3 or 4 clusters per site, and have broadly independent networking and storage (and of course 'server hardware'). I just don't lose sleep over the 'so what if all of it fails' - I guess someone hitting the EPO in the server room would do it (b”
“Sounds like you would be shocked at how many companies (rightfully so) still expect basic update management to be provided by the vendor (Microsoft in this case) for their own product as a built-in or cheap function.”
“yea we have already looked at it. The installer we used still actually has 1.29 instead of the 1.30 required.”
“The logic goes, an update might break something on your server and you don't want to have to regularly make sure that everything still works with your OS.”
“Yes it can……. 🙃 How long until it’s fully automated? submitted by /u/Quiet_Bad_8520 [link] [comments]”
“I literally asked was it terminal services, because they never specified in their post but sure VDI is getting far less common than it used to be, healthcare seems like the main user these days”
“No, this started with Windows 2000, Server and Professional. That was the first time both client and server were using the same kernel and more or less the same shell. NT Server was a completely different beast from 95/98, the client.”
“Just disable it, you will find out eventually if anything is broken. Leave it for two months disabled, document it and delete. Some random software needs some wierd things on the FW to work but if it is still in use as I said you will know about it. I found the same thing on a clients FW we just took over and disabled all the random ports they had open. The next day I get a call from one of their software suppliers saying they cannot poll the server anymorre.”
“We usually test and push out a week after patch tuesday, so its time for us to push and Ive found that I have no status from ~500 clients, and they cant pull approved updates from WSUS. They've released an article about it and ive yet to look at this fix, there is a previous documented fix for 0x80244007 I also have not attempted to implement yet. Anyone else getting issues with clients reporting in (no status) or pulling from WSUS? Has anyone tried the fixes yet? submitted by /u”
“Hey all, Since Patch Tuesday back in May, all 3 of my Domain controllers running server 2019, get an "unexpected crash" notice when rebooting for windows updates, despite the updates still completing successfully. Was there a bug notice or something about this that i missed? Not sure what to do here as troubleshooting whats causing it has led me to a dead end. Anyone else getting this? submitted by /u/Fizgriz [link] [comments]”
“Anyone else noticing Microsoft is releasing SQL Server CUs to WSUS a couple days after Patch Tuesday? I swear we used to get those the same time as all our other patches so we could include them in the patch cycle if we wanted to. They aren't security-related but still would be nice to have the option. I would understand if they came out a couple weeks later, but two days? submitted by /u/jwckauman [link] [comments]”