Restarting Windows
-
When Restart Manager[^] was introduced, MS claimed it would reduce the number of restarts required when updates were applied. Well, I haven't noticed any decrease in the number of times I have to restart after applying updates! It's so annoying..... Thank you.
The difficult we do right away... ...the impossible takes slightly longer.
-
When Restart Manager[^] was introduced, MS claimed it would reduce the number of restarts required when updates were applied. Well, I haven't noticed any decrease in the number of times I have to restart after applying updates! It's so annoying..... Thank you.
The difficult we do right away... ...the impossible takes slightly longer.
Let's assume it's 75% effective in avoiding a restart. That means on a typical patch Tuesday 2 of the patches will require a reboot instead of all 8 of then. You're still going to have to reboot then. :doh:
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, waging 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? --Zachris Topelius 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
-
When Restart Manager[^] was introduced, MS claimed it would reduce the number of restarts required when updates were applied. Well, I haven't noticed any decrease in the number of times I have to restart after applying updates! It's so annoying..... Thank you.
The difficult we do right away... ...the impossible takes slightly longer.
-
Painful enough to post a small rant on Code Project? Yes.
The difficult we do right away... ...the impossible takes slightly longer.
-
My work laptop I only ever put in sleep mode. I keep everything open so I don't have to spend the first 20 minutes of the day reloading my projects in Visual Studio and reloading all my scripts in SQL Server Management Studio. Rebooting kills me. :-P
-
When Restart Manager[^] was introduced, MS claimed it would reduce the number of restarts required when updates were applied. Well, I haven't noticed any decrease in the number of times I have to restart after applying updates! It's so annoying..... Thank you.
The difficult we do right away... ...the impossible takes slightly longer.
During the kickoff event for Windows 2000 in Phoenix, AZ, the product manager gave a thrilling presentation announcing the end of mandatory restarts. He said that there were only 5 situations that would still need a restart, and he lsited them. I don't recall the particulars, but they were all things that would almost never occur. He lied. The next speaker promised an end to DLL Hell. Ditto. They can call it Tech Ed, or MS Insiders, or whatever other silly name they want, but in the end it's all Marketing.
Will Rogers never met me.
-
During the kickoff event for Windows 2000 in Phoenix, AZ, the product manager gave a thrilling presentation announcing the end of mandatory restarts. He said that there were only 5 situations that would still need a restart, and he lsited them. I don't recall the particulars, but they were all things that would almost never occur. He lied. The next speaker promised an end to DLL Hell. Ditto. They can call it Tech Ed, or MS Insiders, or whatever other silly name they want, but in the end it's all Marketing.
Will Rogers never met me.
Good point. :|
The difficult we do right away... ...the impossible takes slightly longer.
-
Painful enough to post a small rant on Code Project? Yes.
The difficult we do right away... ...the impossible takes slightly longer.
-
Given some of my rants I cannot deny you that right. But the whole armed revolution thing you've detailed in your blog is a bit over the top, isn't it?
Heat of the moment. :-O :-D
The difficult we do right away... ...the impossible takes slightly longer.
-
When Restart Manager[^] was introduced, MS claimed it would reduce the number of restarts required when updates were applied. Well, I haven't noticed any decrease in the number of times I have to restart after applying updates! It's so annoying..... Thank you.
The difficult we do right away... ...the impossible takes slightly longer.
I'd reboot anyway. :shrug:
You'll never get very far if all you do is follow instructions.
-
When Restart Manager[^] was introduced, MS claimed it would reduce the number of restarts required when updates were applied. Well, I haven't noticed any decrease in the number of times I have to restart after applying updates! It's so annoying..... Thank you.
The difficult we do right away... ...the impossible takes slightly longer.
You do understand that the restart is used to simply clear memory of executing processes and services that may have been updated. One restart is usually required (unless the updates were trivial). That's not so bad when the result is an updated run-time environment.
Gus Gustafson
-
You do understand that the restart is used to simply clear memory of executing processes and services that may have been updated. One restart is usually required (unless the updates were trivial). That's not so bad when the result is an updated run-time environment.
Gus Gustafson
It's not clear to me what exactly you are clarifying. One restart is annoying enough when I have ten applications open and everything set up exactly the way I happen to be working that day.
The difficult we do right away... ...the impossible takes slightly longer.
-
When Restart Manager[^] was introduced, MS claimed it would reduce the number of restarts required when updates were applied. Well, I haven't noticed any decrease in the number of times I have to restart after applying updates! It's so annoying..... Thank you.
The difficult we do right away... ...the impossible takes slightly longer.
-
It's not clear to me what exactly you are clarifying. One restart is annoying enough when I have ten applications open and everything set up exactly the way I happen to be working that day.
The difficult we do right away... ...the impossible takes slightly longer.
I am explaining why the restart is necessary. If you are performing a Tuesday update, you should not have anything other than the update executing.
Gus Gustafson
-
When Restart Manager[^] was introduced, MS claimed it would reduce the number of restarts required when updates were applied. Well, I haven't noticed any decrease in the number of times I have to restart after applying updates! It's so annoying..... Thank you.
The difficult we do right away... ...the impossible takes slightly longer.
Tend to agree, Microsoft updates are the biggest offender, I used to do software packaging for a very Large Global Company and we repackaged every MSI/Install because of this and/or bad/poorly developed MSI installs. We talking about 1,000++ software apps. So that the MSI would install with no prompts if using /qb option and no reboots, never ever needed one. The only ones would be exception is windows service pack or Anti-virus software (were it want's to check the boot load), even that could be re-worked to install and reboot scheduled later. That's my 50 cents worth! :-D
-
Tend to agree, Microsoft updates are the biggest offender, I used to do software packaging for a very Large Global Company and we repackaged every MSI/Install because of this and/or bad/poorly developed MSI installs. We talking about 1,000++ software apps. So that the MSI would install with no prompts if using /qb option and no reboots, never ever needed one. The only ones would be exception is windows service pack or Anti-virus software (were it want's to check the boot load), even that could be re-worked to install and reboot scheduled later. That's my 50 cents worth! :-D
Funny story. In the poshest mall in Toronto, there are an Apple store and, wait for it, a Microsoft store, quite close to one another. In the Apple store, acres of overpriced but functional hardware, overseen by movementarians, who, let's face it, are fighting off the fans with sticks. In the Microsoft store, a gallant attempt at imitation. And there, in the middle of the store, an RT device. Asking not to be turned off. Because it's installing updates. D'Oh. Illusion shattered. You couldn't make this stuff up. :laugh:
-
My work laptop I only ever put in sleep mode. I keep everything open so I don't have to spend the first 20 minutes of the day reloading my projects in Visual Studio and reloading all my scripts in SQL Server Management Studio. Rebooting kills me. :-P
Even I hate rebooting... keep the computer I use, on hibernate.. I had installed updates on my home laptop last week and was postponing the restart(until day before yesterday).. when I did restart it, it won't log on to my user! :wtf: even tried logging in from the safe mode, but no use. :( The other account was a local account so couldn't delete the files for my user and create a new one.. So, finally formatted it yesterday after taking a backup from the system recovery! :sigh:
.:>GSN<:.
-
I keep automatic updates turned off...every few months I let it update, reboot once and it's done. Automatic updates always choose the worst time to do their thing.
Exactly. I've had windows insist on restarting when I was just about to use Hauptwerk (simulated pipe organ) for a public performance, and because the windows 8 machine wasn't (and couldn't be) on-line, it locked during the update process and I had to use some crappy keyboard instead. I might be working away in a large project when it decides a restart is required, but - if this happens (and it did only last week) whilst I'm away from my machine talking to a client, instead of waiting for me to come back and say OK, it waits ten minutes and does it anyway. I always have my stuff set-up to autosave, so no work itself is lost, but it doesn't half waste some time (especially when the client has come along to view progress) whilst I re-open and re-initialise all the underlying VMs etc that got shutdown in the reboot! I notice that there are never unattended manadatory boots on the server OSs - if it's not important enough to force a mandatory, unstoppable reboot on Server 2012, why is it so important that my work has to be damaged or interrupted on a desktop OS - why couldn't a persistent reminder be used instead?
-
Heat of the moment. :-O :-D
The difficult we do right away... ...the impossible takes slightly longer.
-
Exactly. I've had windows insist on restarting when I was just about to use Hauptwerk (simulated pipe organ) for a public performance, and because the windows 8 machine wasn't (and couldn't be) on-line, it locked during the update process and I had to use some crappy keyboard instead. I might be working away in a large project when it decides a restart is required, but - if this happens (and it did only last week) whilst I'm away from my machine talking to a client, instead of waiting for me to come back and say OK, it waits ten minutes and does it anyway. I always have my stuff set-up to autosave, so no work itself is lost, but it doesn't half waste some time (especially when the client has come along to view progress) whilst I re-open and re-initialise all the underlying VMs etc that got shutdown in the reboot! I notice that there are never unattended manadatory boots on the server OSs - if it's not important enough to force a mandatory, unstoppable reboot on Server 2012, why is it so important that my work has to be damaged or interrupted on a desktop OS - why couldn't a persistent reminder be used instead?
Mike Winiberg wrote:
because the windows 8 machine wasn't (and couldn't be) on-line, it locked during the update process and I had to use some crappy keyboard instead.
I would at very least demote the coder/designer/project manager responsible for that to tea-boy. Errors don't get stupider than that.
I wanna be a eunuchs developer! Pass me a bread knife!
