An exclusive gaming industry community targeted
to, and designed for Professionals, Businesses
and Students in the sectors and industries
of Gaming, New Media and the Web, all closely
related with it's Business and Industry.
A Rich content driven service including articles,
contributed discussion, news, reviews, networking, downloads,
and debate.
We strive to cater for cultural influencers,
technology decision makers, early adopters and business leaders in the gaming industry.
A medium to share your or contribute your ideas,
experiences, questions and point of view or network
with other colleagues here at iVirtua Community.
Yes! Finally, this is what everybody's been looking for, when you leave your computer for 5 minutes to find it has rebooted, or it wont stop annoying you!
Almost anyone who has applied Windows Updates during their day has been annoyed by this issue. Once Windows finishes its update, it asks you to reboot. You click "later". Ten minutes later, a window pops up asking you to reboot again. If you're unfortunate enough to be in the middle of typing, this can actually trigger the "Reboot" button (the default is this button, so simply pressing the space bar while that window is in focus will do it) effectively losing whatever you've been working on.
There's a solution for this issue, which is that the length of time Windows waits before hassling you again is configurable. Colin Mackay has the details.
Quote:
I found this after a lot of Googling, so I'd like to share the solution. Yep, this may not be new or even advanced but it surely helped me...
Anyone who is running Windows XP SP2 know what I'm talking about. That stupid, annoying, most ill-designed dialog box ever invented in the history of the computer science that asks "Updating your computer is almost complete. You must restart your computer for the updates to take effect. Do you want to restart your computer now?"
And there are only two options: Restart Now/Restart Later. "Restart Later" means that this stupid thing will ask you again in 10 minutes. Yes, if you're willing to work for the next 4 hours until lunch before rebooting, this means you'll need to answer this question 24 times. Did I mention that the dialog steals the focus?
Now, to get rid of it: Start / Run / gpedit.msc / Local Computer Policy / Computer Configuration / Administrative Templates / Windows Components / Windows Update / Re-prompt for restart with scheduled installations
You can configure how often it will nag you (I re-configured it for 720 minutes, which means I'll be asked twice on a work day), or completely disable it.
Oh, I almost forgot: this setting is only loaded when Windows starts, so a reboot is needed. If that stupid dialog is on your screen now, just stop the "Automatic Updates" service (but keep it as Automatic, so it gets reloaded on the next start) and you won't see it again.
Hi,
this is one of the things that are really really annoying!
However, I can not access gpedit.msc, when I go to start, Run, gpedit.msc, it comes up with a message saying windows cannot find it.
I'm on XP Home SP2..
Hi,
this is one of the things that are really really annoying!
However, I can not access gpedit.msc, when I go to start, Run, gpedit.msc, it comes up with a message saying windows cannot find it.
I'm on XP Home SP2..
Hi,
this is one of the things that are really really annoying!
However, I can not access gpedit.msc, when I go to start, Run, gpedit.msc, it comes up with a message saying windows cannot find it.
I'm on XP Home SP2..
Ok, the gpedit.msc is the Group Policy Editor. What I said works with XP Professional.
Quote:
GPEDIT.MSC (Group Policy Editor) isn't available on XP Home Edition, partly because XP Home cannot join a domain by design. Although the took is designed to be used in an Enterprise environment running Active Directory, all it really does is making registry entries. So, the best alternative is to edit the registry using Regedit. Be aware that editing the registry incorrectly can make your system unbootable or cause other issues, so proceed carefully before diving in!
You will have to go start > run > regedit and edit the registry.
Be very careful editing registry.
Why not just restart? It's necessary, or else they wouldn't advise you to do so, would they? And if you hate it that much, why not switch to an OS that only makes you reboot after system-level updates?
Sometimes it's just impractical to do so man. I've been in the same situation so I know what he's talking about. You're working on some project and just losing focus or whatever just means The End so most deal with it. As for the OS? Blame Bill Gates, not us for that feature...
As Sam said, this trick only works with XP Professional.
By default once you close the reboot prompt and keep closing subsequent reboot msgs, once ignored for to long the machine will auto-prompt you with a 10 or something second countdown which you must cancel to abort a forced reboot. This is a great way to catch AFK users and sneak a reboot in.
While this is one thing I quickly disabled on my machine as I took offense at having all of my work abruptly lost or otherwise halted which I was in the middle of, the reboots are for a reason. If ignored long enough some programs or the OS itself will eventually go unstall and display odd behavior as the OS needs to be reloaded from the patching. It's a good tool, but use it wisely.
If you have Windows XP Home, the only way is trough Registry Settings:
Go to Start/Run
Run regedit
Search for:
HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\WindowsUpdate\AU
(if you can't find it, it's safe to create this entry)
There, you'll find two registry entries: RebootRelaunchTimeoutEnabled and RebootRelaunchTimeout.
RebootRelaunchTimeoutEnabled can be 1 or 0. 1 means enabled, 0 disabled.
RebootRelaunchTimeout is how long will it show. Right now, I'm as a user and can't create it to test it. Find out for yourselves.
I find this the worst when playing a game such as World of Warcraft fullscreen. You don't see it, then all of a sudden the computer restarts! Can get very frustrating when doing a quest.