CPU at 80%+ utilization, for a malware scanner, during a relatively trivial update. I've somewhat ranted about this in the past but Windows updates seem very inefficient. I wondered if it was some weird SSD/NVME thing but I'm running it in a VM and can do fairly disk heavy tasks outside the VM so it's not DRAM/NAND weirdness. It's Windows weirdness.
I know it's be ideal to schedule the update for night but it's a laptop so I try to do updates as they come given available time. I've love to know more about what the Windows Module Installer Worker is actually doing because it takes the same time as recompiling a medium large app. It's make sense for Android or other OSes where there is potential bytecode rejigging or heavy compression or hashing on a mobile CPU. Or a Python framework like NixOS.
This one was a fairly quick cumulative update at around 20 minutes without cockblocking* the keyboard for ages during the reboot.