Main Area and Open Discussion > General Software Discussion

XP "Automatic Update" / "Restart Later" super annoying dialog

(1/2) > >>

Armando:
Yes I'm still using XP.  :)

I thought this annoyance had been discussed in the past, but i can't find it. Anyway, here are some solutions I found:

XP Automatic Update Nagging

Of both solutions proposed in the article, the second one allows more control over the dialog.

If you're on XP pro, you can just do as described in the article. If you're on XP Home, you won't be able to use the "Group policy settings" editor/dialog (what you could then do is try to hack XP by following these guidelines : Windows XP Home Edition: gpedit.msc (group policy) editing via registry . It's probably not legal though.)

What you can also use WhyReboot? to check out whether you should reboot or not.

And there's this little app that become handy : DontSleep
I don't think it's ever been reviewed here.

Anyhow. :)

Armando:
For XP Home users, you could also enter these lines in the registry :

http://www.xiven.com/weblog/2004/05/01/WeHaveWaysOfMakingYouRestartYourComputer

Badge (2005-08-15 18:20:18 UTC)

For the guy with Windows XP Home...

1. Copy the text below into Notepad. Save it with a .reg extension. Open and confirm that you want to copy the data into your registry.

==>
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU]
"RebootRelaunchTimeoutEnabled"=dword:00000000
"NoAutoRebootWithLoggedOnUsers"=dword:00000001
--- End quote ---

Armando:
Note that group policies aren't updated until a... system restart. :) so your changes won't be perceptible right away.

You might want to try a GPUPDATE.exe (command line on XP pro) or just stop the automatic update service for a while... until your next reboot.

mwb1100:
I like the


--- Code: Text ---net stop "automatic updates"
solution.

I'd get a notification that a reboot is necessary, but it would stop nagging.  After rebooting, automatic updates would be active again as normally configured.

Makes for a nice little one-liner batch file - maybe call it "stopnag.cmd" or something.  And no clicking about in some service management GUI, no mucking about in the register (or even worse, Group Policy editor settings that I can never find again 6 months later).  Best of all worlds as far as I'm concerned.

tomos:

there's also a quick-fix Armando, killing the update exe, which can be implemented via FARR
but I'm damned if I can remember how it goes :-[ (hoping someone else will remember..)

- I have the excuse of being on win7 now

Navigation

[0] Message Index

[#] Next page