Question Fun one, Windows 10 updates cause the system to hang in the middle of the update process ?

[artk2219]

I have this issue on 3 different machines, different hardware all around on all 3, same windows 10 22H2 build though. The issue is that when windows does its updates, and it goes for that first reboot after the 30% mark, the systems start to reboot, and then just hang. The systems will stay in a hung state indefinitely, until the computer is manually powered off, and then back on. The computer will then boot normally, and Windows updates will then finish installing as though nothing ever happened. Its like Windows finishes the first part of the update process, tells the system to reboot, and then the system just doesn't finish rebooting. Ive tried various bios updates, driver updates, software updates, but again, they all 3 have completely different hardware, anyone else ever run into this issue?

System 1
Ryzen 9 7900X3D
Samsung PM981A 256GB NVME SSD boot drive
64GB Crucial RAM
Asus ROG STRIX X670E-A Gaming Wifi
RX 7900 XTX
EVGA 850W PSU
Windows 10 22H2
Windows Defender

System 2
Ryzen 5 7500F
Crucial P3 2TB NVME SSD boot drive
32GB Corsair RAM
MSI Pro X670-P Wifi
RX 6900 XT
EVGA 850W PSU
Windows 10 22H2
Windows Defender

System 3
Dell Precision 3660
I7 12700K
Crucial P1 1TB NVME SSD boot drive
32GB Kingston RAM
Dell 1100W PSU
Windows 10 22H2
Crowdstrike

 

[Lutfij]

Take a screenshot of Disk Management for all three systems. Notable the OS drive/partitions. What update are you/the OS trying to update to?

 

[artk2219]

Take a screenshot of Disk Management for all three systems. Notable the OS drive/partitions. What update are you/the OS trying to update to?

It's not a particular set of windows updates, it's literally every time windows update runs and requires a reboot. I'll get a shot of disk management with disk utilization though

 

[johnbl]

any chance all three machine were connected to some network storage? I have looked at machines that would not shutdown because they were writing roaming profiles to network storage and the network storage failed to indicate that the data was flushed to disk. Windows would just wait with a black screen until it got the network packet that never came. (server bug)
people just rebooted the machines to continue