Probably has to do this early on in the boot process so as not to require a reboot after update because of Windows’s silly pessimistic file locking.

> because of Windows’s silly pessimistic file locking

To be honest I prefer that over the #nix way of doing things. In Windows, you have exactly one file any given path can refer to - in Linux or Mac, it may depend on which directory's inode is seen as the root node by your process (e.g. chroot or container), or whether mounts are at play, or a file/directory got deleted and replaced by something else.

Particularly the last scenario keeps tripping me every once in a while.