Windows Updates Crashing Computers
Posted by Ok_Emu_8095@reddit | sysadmin | View on Reddit | 23 comments
I know that is like saying water is wet, but yesterday I had a couple of physical machines have to roll back the updates and now I have 4/4 Windows 11 VMs that are busted and one physical machine. Anyone else having issues or am I special.
SubstantialWitness55@reddit
I have some PCs with no network connection after updates :(
TheBrossef@reddit
did you roll back to fix the issue? we seem to have issue on a few PCs as well
taikowork@reddit
Try reinstalling their network drivers, I had two machines that had the same issue and wiping the driver from device manager and reinstalling fixed it.
Fake_Cakeday@reddit
I've had a month long support case with Microsoft about a similar issue. This is on 23H2 and 24H2.
WiFi and cabled internet doesn't work.
Plugging in a cable and rebooting makes cabled connection work, but if you plug it out and back in then it stops working.
If you connect it to WiFi however, then you can be connected to wifi for a few hours or the rest of the day. Or sometimes multiple days.
Untill it then stops working and you have to plug in a cable, reboot, connect to WiFi, and then unplug the cable.
We've went back on WiFi drivers to 23.30.x (they were on 23.130/140.x)
Rolled back the May and June updates.
Set registry keys "EnableDHCP" DWord to 1 for all interfaces.
The Microsoft logs found that in the DHCP DORA sequence the client is not sending the request. But it is sending the Discover first. So it's only partly broken on the clients side.
Weird issue for sure.
JohnSysadmin@reddit
Along the same lines as u/jpba1352 we have 4 machines testing "driveablility" for 24H2 and had wifi issues. We fixed by changing a reg key to disable depedencies between Winhttpautoproxy and wcmsvc
HKLM\SYSTEM\CurrentControlSet\Services\Wcmsvc
Edit the DependOnService key and remove WinHttpAutoProxySvc. Reboot the machine, and your wireless NIC should be back.
jpba1352@reddit
To fix this we ran this in an elevated command prompt and rebooted
sc config WcmSvc depend= RpcSs/NSI
jpba1352@reddit
had that problem so my higher ups told us to this in an elevated command prompt
sc config WcmSvc depend= RpcSs/NSI
gunkthruster@reddit
Same here. 4 couldn’t connect over WiFi. One worked with new drivers , the other 3 had very low disk space. Not sure why that would break networking.
LeaveMickeyOutOfThis@reddit
The issue I had was that the machine got IP address via DHCP, but then nothing worked after that. After a couple of reboots, it worked again. No other changes.
taikowork@reddit
I had two machines that wouldn't connect to ethernet after updates, reinstalled their network drivers and they're good to go now in case that's helpful.
Short-Shoe-1080@reddit
With Kb5056579 my touchpad and network stopped working and usb devices started disconnecting randomly
Roll back and apparently everything went back to normal.
Surtle-Teck-Nweater@reddit
KB5062553 crashed my personal machine and a clients machine at work
Kuipyr@reddit
Heavy stuttering on the Desktop, fixed with a video driver reinstall.
Sparkycivic@reddit
I had bsod on two machines this week, which were recently upgraded from W10 to W11 . It was a roundabout of bugcode ndis something or other, kmode blah blah, and a third more cryptic one. I eventually got out of it by going into safe mode and disabling all of the non network card drivers in the network driver section. Good thing I have no need for vpn or whatever other services those drivers supported. Just older workstations with dual Intel NICs.
Eli_eve@reddit
No issues on our three test machines. Our pilot group is starting up soon - I’ll report back if any have similar issues.
vadavea@reddit
yeah, my main win11 laptop barfed badly after updates this week. Got the whole "enter your bitlocker recovery key" UI on booting which is always fun. It rolled itself back and I'm back in business.
aprimeproblem@reddit
I had the same on a few vm’s. Running kvm/army as hypervisor with amd proc as host cpu assigned to the vm. bsod with unsupported processor warning. Fixed by selecting a different kind of processor.
If this is in anyway helpful?
DoomliftDaemon@reddit
We've had issues with amd laptops background going black and running slow, updating the graphics driver from amd if not up to date seems to fix it so far.
My own pc this morning was acting weird after the update installed last night a reboot seems to have chilled it out but everything was running real choppy and the mouse and keyboard wouldn't respond and then catch up to themselves a few seconds later.
christurnbull@reddit
I've been getting graphics card bluescreens pointing at nvidia & intel drivers. No devices with amd graphics to compare against.
GuessSecure4640@reddit
I upgraded a laptop from Win10 > Win11 and it blue screened this week. I finally got it to go after 07/25 cumulative update went through on Win10. Now I'm going from 23H2 > 24H2 on Win11 and it blue screened again. Never had issues with this PC prior to attempting the upgrade
ZealousidealClock494@reddit
I seem to remember seeing a very similar post yesterday or maybe it was a comment on the patch Tuesday thread.
So far so good here. Rolled the initial group with no issues.
SysManPesho@reddit
Can you share a KB number or any update number ?
Ok_Emu_8095@reddit (OP)
KB5056579 installed overnight. Cumulative Update for .NET . That's from a machine that was hung on boot, maxing out the cpu, it actually came up after I shut it down/put it back on. One of the other ones had to roll back whatever the update was in order to boot.