That's no excuse because there exists easy workarounds. From my understanding with how the winsxs store works, almost every system binary is really a hidden sy

That's no excuse because there exists easy workarounds. From my understanding with how the winsxs store works, almost every system binary is really a hidden symlink to the right binary in winsxs (with some having different cpu optimizations). One of the cool things about symlinks is handles don't hold on them, they just hold on to the target, so you can change a symlink target without interrupting or getting blocked by handles that have that symlink open. Windows update could put all the new binaries in to new winsxs loctions then just swap over all of the symlinks on next boot. I know this works because I use it to deploy updates to a running game server binary so that the next time it restarts itself on round end it's using the new binary. We also update the loaded dlls it uses this way.