The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
I was under the impression that Microsoft had listened to the pitchfork wielding masses and stopped the practice of rebooting your machine without warning. I honestly had.
I was in the middle of debugging some really messy TypeScript. Lots of windows open, Visual Studio debugging Chrome, Chrome debug tools, breakpoints everywhere, nothing really working properly in the debugger because I'm using vue and webpack and the .map files don't work, but it was all there. I had found the spot it was broken and was stepping through carefully.
I left the computer to take a break. An hour no more. There had been a notification about a Windows update and I'd lazily hit the "bother me later" button.
And so I come back an hour later to a freshly rebooted computer.
Are you effing kidding me?? I cannot even vaguely understand the mentality of this. Maybe if the machine was idle for 10 hrs. Maybe if I'd been warned 3 times with ever increasing levels of direness. Maybe if there was truly a security issue that was going to threaten my cat or something.
But to just reboot and lose an hour of sleuthing and setup?
A feature that is abso ing-lutely worthless, since you can't set the Active Hours to what you want. They limit it to a 12 hour period, there's only one interval, and there are further constraints on the start and end times.
In other words, it's their ing computer and they'll reboot it if they ing want to, so off.
1) You're some sort of weirdo who completely wraps up everything you were doing on your computer leaving zero lose ends before going away but is too lazy to turn it off.
2) Every piece of software you're using supports background auto-save of data and state to recover after a reboot.
I'm not sure which of those is most preposterous.
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, weighing all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies.
-- Sarah Hoyt
You're some sort of weirdo who completely wraps up everything you were doing on your computer leaving zero lose ends
That's me. When I'm done for the day, nothing's running except the normal background stuff. Some of this is so that I don't have to worry about my automated nightly backup having to deal with access conflicts. The other part of it is from bitter lessons learned from applications and/or their data being corrupted from an unwanted restart.
I wish I could afford to be that tidy and close things off at the end of a day.
I can be working on many different things on any given day (and typically have to task-switch multiple times in a single day), so I would leave projects opened for weeks if I could. But reality settles in and always finds a way to prevent me from doing that.
It would only get worse if I actually started using the "multiple desktops" feature that Windows 10 finally got a few versions back. My desktop is typically a mess of windows piled high on top of each other. What helps in my case is that I run many VMs, each of which being dedicated to very specific subsets of tasks (meaning, I have a VM doing nothing but being a DC, a WSUS VM, a SQL VM, a development VM, etc...I'm done assigning completely different roles to the same OS instance). And that's me just being a home user.
My issue isn't just how much time has been lost, but that which is yet to be lost -- because Windows tries to open a few of the things I had open, but doesn't, and can't do so in the correct order, so I need to close them all and reboot again to start fresh.
How can I get it to at least not try to reopen what it shut down?
Settings ⇒ Accounts ⇒ Sign-in options
Make sure "Use my sign-in info to automatically finish setting up my device and reopen my apps after an update or restart" is off.
This really should have been two options: when it restarts after a major update, I do want it to finish the annoying "Please wait, we're getting things ready..." sequence as soon as possible, without waiting for me to sign in. But I don't want it to try to reopen any apps, or to run any startup apps. Just finish the setup and leave the computer logged out.
"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer
Still, there's something to be said for it, once you get used to it. It quickly becomes second nature.
That being said, I've also seen plenty of updates gone horribly, horribly wrong, on clean, hardly used Linux VMs, that should still be in such a pristine state that failures couldn't be blamed on having some uncommon, untested configuration.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
truth - I haven't driven unix command line in a while. It *is* what I meant to say
Years ago, my wife was running a budding web development business. This was before all of the frameworks and other stuff out there. It was just you, the command line, and knowing where to look for bugs in your perl scripts.
And yes, one day I taught her the rm -rf command. Told her to be careful too - didn't matter, you always do it once
<italic>Stuck in a dysfunctional matrix from which I must escape...
"Where liberty dwells, there is my country." B. Franklin, 1783
“They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759
Last Visit: 28-Sep-20 8:37 Last Update: 28-Sep-20 8:37