It can't, really. What Linux will do (and Windows won't) is delete old files and replace them with new ones while they are still in use. But this has two problems.

1. It can lead to stability issues. See e.g. Firefox, which refuses to open new tabs and can't shut down cleanly if you update using the package manager while the browser is running. If you replace a binary executable in use and it later tries to load a shared library dynamically, it will get an unexpected version of that shared library which can potentially lead to memory corruption. Similar problem if the program tries fork+exec itself to create more instances (like Firefox and Chrome do).
2. It won't actually update the running process in memory, so even if you install security fixes your system will still be vulnerable. To be safe after e.g. fixes to libc you really need to reboot your system, but most distributions hide this fact from the user.

Windows could certainly opt for a similar solution as Linux. They just chose a stricter and more reliable model for file locking, for good or bad. For what it's worth I personally prefer the Linux model, but that's because I know to reboot my system after updating it. I don't trust my dad to take that social responsibility so he needs to be forced.

You're confusing linux with nodejs.

There's a configuration file you can edit to prevent that. The Flatpak configures this automatically for you.

Linux distros usually raises a reboot required flag. But thats usually to complete some kernel or system update. Windows just go ahead and reboot on update ruining the workflow.

When you get the message to reboot ignore it and do your work. Then shutdown after doing it. Turn on when you need it the next time. And its all well

“updates were installed, you should reboot”.

But I think you can ignore it, the updates just will not take effect until you reboot.