A restart lets an update replace the code you were using

Why an update can restart a computer

An operating-system update may change no icons, menus, or other visible features and still alter how the computer works. Patches can replace parts of the system that are active while the computer is running, including files used by the operating system itself. Those files may be locked in use, so the installer cannot safely swap them out immediately.

A restart gives the computer a chance to load the patched versions from the beginning. Before the desktop appears, the update process can finish replacing files and adjusting system components that could not be changed while they were active. The restart is not just a prompt to save work; for some updates, it is part of installing the change.

Why the change can seem invisible

Many patches address security flaws, reliability problems, or compatibility issues rather than adding a feature. Their success is measured by what stops happening: a vulnerability is harder to exploit, or a fault is less likely to occur. Because these changes work behind the scenes, the computer can look exactly the same afterward.

Not every update requires an immediate restart. Some changes can be applied while the system is running, while others must wait until startup. If the update replaces a component that the computer currently depends on, postponing the restart also postpones the point when the patched version takes effect.

The practical tradeoff

The interruption reflects a basic constraint: a computer cannot always replace a working part of its operating system while that part is in use. Restarting briefly takes the machine out of service, but lets it start with the updated components together. That is why a patch that appears to do nothing can still demand the one change users notice most: the screen goes dark, and the computer boots again.