3 ms·
The real issue is that Windows updates themselves take way too long, and mostly seem to require a restart. Why is the former worse than before and the latter st
by tdeck 6y ago
The real issue is that Windows updates themselves take way too long, and mostly seem to require a restart. Why is the former worse than before and the latter still so bad?
- freeone3000 6y agoThe removal of incremental patching means most major updates are now secretly a reinstall. This has increased system stability - now patched installs and fresh installs are the same. The rebooting even for minor updates is due to files not being able to be changed while they're open, so a change to, ex, gdi32.dll is going to prompt a restart, regardless of the size.
- ztjio 6y agoThat doesn't really explain why an updated to, say, .NET forces a restart. Far too many updates force restarts when it seems they shouldn't require it. It's not just the main OS updates.
- alkonaut 6y agoI'm guessing applications will be running with the old libraries loaded and developers should be able to count on this one-version-only situation (e.g. ABI between processes). Forcing a restart is just the simple but crude way of ensuring that no applications are using any system files (.NET is part of the OS, up until .NET Core).
- Akronymus 6y agoMost of the time, you can just ignore the restart option. It seems to be the windows philosophy to just throw a restart in for good measure.