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.
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!
-
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!
Exactly - and very embarrassing it was too! 8) Windows 8.1 has improved matters greatly, although there are still a number of - insert current name of Windows Metro UI here - applications that fail when not on-line. On the first release the Kindle app (RT) version wouldn't allow you to turn a page if you weren't on-line - very handy when trying to read on the train etc! That's what happens when you live and work in a tech bubble where fast, reliable broadband is present everywhere you go - those of us (ie the majority of people worldwide) who don't have continuous, hi-speed WiFi/Mobile services available are - as always - completely forgotten or dismissed out of hand. Something, I must say, which is now happening here, with the UK Gov. insisting that things must be done on-line, whilst a large proportion of the population do not have reliable (or even any) access to decent broadband. A fifty-mile circle around where I live covers nearly 25% of the UK population, and yet I have only a relatively slow BB connection, (superfast having been postponed yet again!) and no reliable mobile signal from any of the operators that supposedly cover this location. Where I work in the City of London, superfast broadband is not available, despite the building having two fibre-optic cables coming in, one of which is from BT! Joined up thinking? No chance!
-
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 always reboot my development machine after updates. Like nuking the site from orbit, it's the only way to be sure.
Software Zen:
delete this; -
Wel obviously you are a fan. (Why else have a name with x64 in it) ;P
Loading signature... . . . Please Wait . . .
CBadger wrote:
Why else have a name with x64 in it)
So x64 means Microsoft to you? I thought it was simply the name of a CPU architecture.
The difficult we do right away... ...the impossible takes slightly longer.
-
CBadger wrote:
Why else have a name with x64 in it)
So x64 means Microsoft to you? I thought it was simply the name of a CPU architecture.
The difficult we do right away... ...the impossible takes slightly longer.
-
Here is what the first result says:
Quote:
x86-64 (also known as x64, x86_64 and AMD64) is the 64-bit version of the x86 instruction set.
You'll have to show me a specific post that says that x64 means Microsoft if you want me to believe it.
The difficult we do right away... ...the impossible takes slightly longer.
-
Here is what the first result says:
Quote:
x86-64 (also known as x64, x86_64 and AMD64) is the 64-bit version of the x86 instruction set.
You'll have to show me a specific post that says that x64 means Microsoft if you want me to believe it.
The difficult we do right away... ...the impossible takes slightly longer.
-
I rest my case. :-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?
-
I rest my case. :-D
The difficult we do right away... ...the impossible takes slightly longer.
