if you're not going to let me do this microsoft then let me turn off auto restart all together.
image caption: A Microsoft Windows screen showing "Active Hours" with start time set to 12 AM and end time set to 12 AM and an error that says "Choose an end time that's no more than 18 hours from the start time".
You know. It's interesting. I've been trying out Debian 12 with KDE Plasma. It actually has been a joy and feels like what Windows 11 should have grown into, had Microsoft actually been designing software with the customer in mind.
...but then there have been times where things so easily critically break until you fix them. Don't get me wrong. I'll go mess with kernel code if I have to, so I'm comfortable, but... I just want my computer to work. Windows, for all its shittiness, still keeps working through it like a slow cargo train pushing through a park piled in millions of pancakes.
I had one event the other day where I was installing a Snap app for the first time. Decided rather than installing the Snap package manager because I wanted to avoid Canonical if possible, I'd just manually put it in /opt. Figured out how to edit the KDE "start" menu to add the app using the included GUI tool. Wanted to use the app's icon. The snap app had an icon embedded in it that Dolphin file manager recognized and displayed.
So I went, "ok, sometimes applications can parse out images from binary files. I've seen this work for decades," so I tell the menu editor to ingest the snap binary for the icon, to see if it will scrape the icon. No icon showed up, so I found a a svg online and assigned that to the icon.
Then I went and saved and launched another application.
GUI slowly started not working and eventually the entire OS locked, even the alt text consoles would not load. Ctrl+alt+backspace was dead, caps lock died, which was when I knew, "he's dead, Jim."
Tried rebooting, tried launching that program again, (bearing in mind, not the program I manually added to the "start" menu) and every time the whole OS freezes up. Tried launching apps in different order, launching from command line, etc. When the one app launched that wasn't the one I created a launcher icon for, same thing. Freeze. (It is possible that the bug is in fact time-based or boot-sequence-based, and since I was trying to reproduce the bug rapidly, the other app had nothing to do with it.)
I go remove the start menu link, hoping that, what I assumed was part of Plasma was trying to load this binary as an icon even though it should have checked the file, recognized it as "no I can't parse this," and done nothing or displayed an error or parsed it and showed the icon. Especially after I assigned it another image. I just hoped whatever screwed up would be connected to the code executing that app launcher icon config, and deleting the config for that application would delete whatever mess that was created, and hopefully was created discretely.
Shit you not, the computer became rock solid stable again after that and one more reboot. Hasn't glitched since.
It's shit like that that makes me proooobably give up on this experiment and end up on a commercial OS like MacOS again despite the cost and downward trend they are also suffering in a lack of innovative energy.
Just to mention also, I've been running Debian for much longer than I care to think about (since my teen years, I'm now in my 40s), with config file requirements that make arch look like lazy mode by comparison.
If you have to use something, flatpak wins, but personally I'd lean away from any of it as much as possible. The Debian stable repos are stable, so what's in there will work. Add flatpak to KDE Discover by installing plasma-discover-backend-flatpak to get that option in there.
But snaps should be strictly off limits. For everyone, tbh.
Debian tends to require a lot of tweaking to get it to work well with more modern things. I've never gotten video and audio hardware to work out of the box to my satisfaction, for example. Ubuntu is definitely easier to use out of the box. But I also don't like the way Canonical has been taking it lately. And since I've been using CENTOS for servers for many, many years and more recently Rocky Linux, I decided to give Fedora another try after a failed attempt like a decade ago (I think the version at the time was Verne).
Combined with Plasma as a front end, Fedora is awesome. Some things aren't there that I'd prefer and flatpacks and snaps always have minor, annoying issues, but for the most part it does everything I need and even supports my fairly new laptop with a touchscreen and pretty modern hardware without any tweaking.
Give Fedora Kinoite a shot. Atomic distros are the shit. If you fuck it up, you literally just reboot, roll back, and you are up and running again. I’m finally starting the process of migrating off of windows and onto Bazzite for my desktop (because it doubles as my gaming machine), but I’ve been using Kinoite on my personal dev laptop for a while now and it’s awesome! It’s a bit of a paradigm shift from a traditional distro, but it’s really not that hard to figure out and adjust to.
1: I could host my desktop with Parsec (client support exists, but not host support).
2: Sunshine/Moonlight actually worked, as an alternative. It is broken and janky and isn't a substitute. I've tried. A lot.
3: I could wirelessly link my Quest 2. VR support is a hot mess and I'm still waiting for a solution to wirelessly link my Quest 2 in linux that actually works and doesn't require a month of programming a solution myself.
4: Better compatibility with some stuff. Proton gaming works most of the time, but not for the titles I play.
I started using linux by setting up a dual boot: using windows only for things I couldn't do at the time on linux. That were gaming and some apps only supported by windows
After usig it for some time I now have everything on linux (or an alternative) and uninstalled windows. Still in the process of figuring out some very specific stuff like you with your Quest, but someday I just couldn't have it with windows anymore.
There are a lot of ressources online and some distros are really great for gamers/ newcomers. Just give it a try and some time. You will have to learn some things like you had to with first using windows.
That annoyed me with Windows too, however, Active Hours adjusted to the times that I actively used my PC. As I kept my PC up to date and never kept it running while not in use for too long, I've never been threatened with a forced restart randomly. That being said, a user should have full control over their PC. They will though in turn be responsible for any poor outcomes due to making poor decisions.
I ended up choosing a Linux distro over Windows because I have absolute control over my PC at all times. Freedom to modify, to potentially break, but also easily recover my distro if I truly fuck up.
The real solution is to set it so it starts just before you are supposed to wake up, and ends 6 hours before that. That gives you the active hours as intended, and it won't reboot the system in the middle of work ever again.
The whole point of this option existing is to keep the system from auto install/reboot in the middle of work. You're telling the machine when it's not okay to do this... so you're the one in control.
What fully functioning adult even uses their computer for 18 hours straight? Last time I used my computer for more than 12-14 hours was probably when I was a teenager. Pretty sure if I had used a computer for 12 hours straight right now, my head would hurt for the rest of the day, and the next one as well.
I would agree, but there's been at least two updates in the last six months that restarted my machine before I even got to see the pending restart warning. I use it every day and shutdown if I won't be. So the restart happened less than 24 hours after any warning if there even was a warning.
That has the potential to lose things I'm working on. Windows pathetic attempt to bring things back falls woefully short of functional.
Flash up alerts to say there's critical updates, but the action to actually restart should be a human interaction.
If CrowdStrike has taught us anything, it’s that blindly trusting automation can be equally (if not more) disastrous.
It’s one thing to ask me to update, but give me options; including to not update. There are machines out there in the world that still run Windows 95. They are vital to manufacturing processes, and cannot be updated because they run software that is no longer updated and there is no inexpensive alternative. It happens.
While that may not be the case in this circumstance, the point is that it’s up to the operator to determine when it’s time to update, not Microsoft.
Anecdotally, the only reason Microsoft does this is because people historically do not update their software regularly. Why? Because it’s burdensome and problematic. Whose fault is that? I’ll give you three guesses; the first two don’t count.
There was a time when I would’ve believed this and there was actual transparency regarding what was in those updates. They can also break your system because you are the tester. They fired all their QA long ago.
I just don’t think they command the level of trust that they wanted, but on the other hand, that’s the reason I don’t use their OS in the first place so I may not be qualified..