Run updates without me having to worry that “whoops, an update was fucked, and the system is not unbootable anymore. Enjoy the next 6 hours of begging on forums for someone to help you figure out what happened, before being told that the easiest solution is to just wipe your drive and do a fresh install, while you get berated by strangers for not having the entirety of the Linux kernel source code committed to memory.”
Windows recovery fails in plenty of circumstances, it’s not a magic bullet. Snapshots are like you can do with btrfs, but that’s not exactly how Windows recovery works.
As someone who has hundreds of installed programs with tweaks on top of tweaks and hundreds of thousands of files, I always find the suggestion to “just reinstall” beyond laughable.
Even in the most stable distros I’ve had this issue. We had a RHEL 9 server acting as a graphana kiosk and it failed after an update. Something dbus related. I’d love to know why, as it’s been the only failure we ever had but nonetheless it shakes confidence. Windows 11 updates trashed three servers, one to the point we had a to fly an engineer out. My hope is that immutable distros fix this.
You might be suffering from the opposite of survivorship bias: When you work in IT you end up having to fix the strangest shit that reoccurs on certain categories of hardware.
I know for a fact that RHEL 7 just did not like certain appliances by vendors that used it (back in the day). They would regularly break themselves until the vendor put out an update that switched it to a Debian-based custom thing.
Also, all the (thousands of) appliances that use Windows are utter shit so it’s not really a high bar. The vendor just needs to hire people that actually know what they’re doing and if they do they won’t use Windows on an appliance!
I have an uncle who will assume anything that takes over 20 minutes has crashed so managed to break his Windows box by continually hard resetting as it was trying to apply a large upgrade.
I’ve actually had more issues with Windows doing that. My wifi drivers have stopped working on more than one occasion, and once it just decided to stop recognizing my wife’s hard drive.
Run updates without me having to worry that “whoops, an update was fucked, and the system is not unbootable anymore. Enjoy the next 6 hours of begging on forums for someone to help you figure out what happened, before being told that the easiest solution is to just wipe your drive and do a fresh install, while you get berated by strangers for not having the entirety of the Linux kernel source code committed to memory.”
Just to provide another data point: I’ve had bad Windows updates render my machine unbootable too.
And then you’re left searching for bullshit error messages and potentially unable to fix the problem regardless of your level of expertise.
… No you just use Windows built-in rollback feature. Which I think even auto-recovers these days of it detects a failure to boot after an update.
Windows recovery fails in plenty of circumstances, it’s not a magic bullet. Snapshots are like you can do with btrfs, but that’s not exactly how Windows recovery works.
Of course not, but it works 9/10 times for most people. Enough so that most people never have to deal with a faulty Windows update.
Hah! Can someone here chime in and tell me when the slow AF (as in, it can take hours) rollback feature actually worked‽
Who TF is that patient‽ You can reinstall Windows and all your apps in half the time required.
As someone who has hundreds of installed programs with tweaks on top of tweaks and hundreds of thousands of files, I always find the suggestion to “just reinstall” beyond laughable.
I think it recovered my PC for me twice, and it took about ~10 minutes each time at most. Good luck reinstalling everything in that time lol.
sfc /scannow didn’t work? Well too bad, cuz now you gotta reinstall your OS
And Microsoft support that’s in fact clueless fanboys.
Spoken like someone who doesn’t do stable releases
Even in the most stable distros I’ve had this issue. We had a RHEL 9 server acting as a graphana kiosk and it failed after an update. Something dbus related. I’d love to know why, as it’s been the only failure we ever had but nonetheless it shakes confidence. Windows 11 updates trashed three servers, one to the point we had a to fly an engineer out. My hope is that immutable distros fix this.
You might be suffering from the opposite of survivorship bias: When you work in IT you end up having to fix the strangest shit that reoccurs on certain categories of hardware.
I know for a fact that RHEL 7 just did not like certain appliances by vendors that used it (back in the day). They would regularly break themselves until the vendor put out an update that switched it to a Debian-based custom thing.
Also, all the (thousands of) appliances that use Windows are utter shit so it’s not really a high bar. The vendor just needs to hire people that actually know what they’re doing and if they do they won’t use Windows on an appliance!
I have an uncle who will assume anything that takes over 20 minutes has crashed so managed to break his Windows box by continually hard resetting as it was trying to apply a large upgrade.
I’ve actually had more issues with Windows doing that. My wifi drivers have stopped working on more than one occasion, and once it just decided to stop recognizing my wife’s hard drive.