4 ms·
If the upgrade fails, that's a completely different issue, not a typical path. We need to separate those, otherwise we'll end up with "On <any> system, when the
by viraptor 7y ago
If the upgrade fails, that's a completely different issue, not a typical path. We need to separate those, otherwise we'll end up with "On <any> system, when the upgrade catastrophically fails, I have to reinstall the whole machine, so upgrades take hours."
- pixl97 7y agoEh, windows updates, especially when you're including .net 4+ take a pretty considerable amount of time, especially when on a HDD. Server 2016 updates Re very memory hungry.
- z3t4 7y agoI get into the install-reboot-uninstall-reboot cycle every time I start Windows (yeh, it's broken, but I've tried nuking the upgrade cache, "repeair" etc). I've also got a few upgrade fails on Linux. Where I had to boot a live-cd/usb and chroot in to fix the problem. And those took a few hours. I've probably spent more time fixing stuff on Linux. But it you would run a distro like Ubuntu, and not make any customization, then the upgrade experience is much better on Linux then Windows.