-
Howdy! Welcome to our community of more than 130.000 members devoted to web hosting. This is a great place to get special offers from web hosts and post your own requests or ads. To start posting sign up here. Cheers! /Peo, FreeWebSpace.net
Win2K shutdown
- Thread starter Wojtek
- Start date
Check if in the event viewer (under Start/Programs/Administrative Tools/Event Viewer) under Application Log you have "UserEnv" errors with a description of: "Windows cannot unload your registry file. If you have a roaming profile, your settings are not replicated. Contact your administrator."
If so the problem is caused by Windows not being able to unload a part of the registry hive that contains your registry settings. If it's unable to unload it the first time it will try again for 60 seconds at a rate of once every second. This can happen when a program opens a registry key but doesn't release it nicely when it's shut down.
There are a few solutions and also a couple of work arounds you can try. First of all if you don't have SP3 installed yet go download and install it and see if that fixes the problem. Just choose to "log off" instead of "shut down"/"restart". It will keep the waits to a minimum.
(Don't get too happy if at one point it'll log off instantly because I had that happen too but try it at least three times to be sure).
If you already had SP3 installed or it didn't work check the Add/Remove programs window and see if you have any Pre-SP4 hotfixes installed, specifically look for hotfixes Q328310 and Q329170. Uninstall Q328310 first if it's there and reboot, then uninstall Q329170 and reboot. Now try logging off again and see if it's fixed (this worked for me). You can apply hotfix Q328310 again if you need it (the WM_TIMER causes etc etc) and Q329170 as well (in that order) but on one machine it worked but on the other right after reinstalling Q329170 it "hung" on log off again.
If none of the above worked then try disabling the printer spooler service before logging off (open a command prompt and type: net stop spooler). For a lot of people this made it stop "hanging". If you don't have a printer attached to that computer you can set the service to disabled to prevent it from starting (Control Panel/Administative Tools/Services.. right click the Print Spooler and set it to Disabled).
If you do have a printer you can make a logon/logoff script that will start/stop the service each time you log on/off if you know how to do that, that's the first workaround.
Otherwise Start/Run and then: gpedit.msc to access the Group Policy Editor. Go to Computer Configuration/System/Logon/Maximum retries to unload and update user profile. You can look at the explain tab to see what it's used for. Basically it tells Windows how many times it should retry unloading your part of the registry hive. (One try is one second). Set it to Enable and then 5 tries. Press OK and then close the group policy editor and reboot. I'm not sure if the change happens instantly or not but it should be alright after the next reboot.
One of the things I said should work hopefully.. best of luck
If so the problem is caused by Windows not being able to unload a part of the registry hive that contains your registry settings. If it's unable to unload it the first time it will try again for 60 seconds at a rate of once every second. This can happen when a program opens a registry key but doesn't release it nicely when it's shut down.
There are a few solutions and also a couple of work arounds you can try. First of all if you don't have SP3 installed yet go download and install it and see if that fixes the problem. Just choose to "log off" instead of "shut down"/"restart". It will keep the waits to a minimum.
(Don't get too happy if at one point it'll log off instantly because I had that happen too but try it at least three times to be sure).
If you already had SP3 installed or it didn't work check the Add/Remove programs window and see if you have any Pre-SP4 hotfixes installed, specifically look for hotfixes Q328310 and Q329170. Uninstall Q328310 first if it's there and reboot, then uninstall Q329170 and reboot. Now try logging off again and see if it's fixed (this worked for me). You can apply hotfix Q328310 again if you need it (the WM_TIMER causes etc etc) and Q329170 as well (in that order) but on one machine it worked but on the other right after reinstalling Q329170 it "hung" on log off again.
If none of the above worked then try disabling the printer spooler service before logging off (open a command prompt and type: net stop spooler). For a lot of people this made it stop "hanging". If you don't have a printer attached to that computer you can set the service to disabled to prevent it from starting (Control Panel/Administative Tools/Services.. right click the Print Spooler and set it to Disabled).
If you do have a printer you can make a logon/logoff script that will start/stop the service each time you log on/off if you know how to do that, that's the first workaround.
Otherwise Start/Run and then: gpedit.msc to access the Group Policy Editor. Go to Computer Configuration/System/Logon/Maximum retries to unload and update user profile. You can look at the explain tab to see what it's used for. Basically it tells Windows how many times it should retry unloading your part of the registry hive. (One try is one second). Set it to Enable and then 5 tries. Press OK and then close the group policy editor and reboot. I'm not sure if the change happens instantly or not but it should be alright after the next reboot.
One of the things I said should work hopefully.. best of luck
Not meaning to dig up old threads deliberately, but I thought I might share some personal experiences for anybody else who wants to find the solution to the shutdown problem.
If you, like me, simply gave up after seeing carebear's post, fear no more.
It's easier than you might think. All you gotta do is uninstall hotfix Q329170 (some very minor security fix that shouldn't be of concern to most users) and you're shutting down faster than you can write Windows 2000 Professional on paper.
PS... most likely, a warning will appear when you attempt to remove the hotfix, listing programs that it says might not function properly if you continue with the uninstall, but I can assure you, nothing will be affected. In the worst-case scenerio, if a particular program really stops working after uninstalling the hotfix, relax... all you have to do is install it again from windows update, and it should be fixed.
*coughs* That's mentioned in my post as well!Originally posted by LeX
If you, like me, simply gave up after seeing carebear's post, fear no more.
It's easier than you might think. All you gotta do is uninstall hotfix Q329170 (some very minor security fix that shouldn't be of concern to most users) and you're shutting down faster than you can write Windows 2000 Professional on paper.
I just included everything since not every fix works for everyone
Yes, I know it's in your post, but you mentioned about a billion methods that I wan't even willing to try.Originally posted by CareBear
*coughs* That's mentioned in my post as well!
I just included everything since not every fix works for everyone
I browsed around the net and found a couple of discussions about this little bug, it's even acknowledged by Microsoft (they say they will fix it in the next SP, and if you really want the patch, you have to call them up...). The cause of this problem was narrowed down to hotfix Q329170, and since it worked for me, I thought I would let others know.
No need to get rid of your printer spooler or whatever else was mentioned ...
mine is 809mb and saves settings in 15 sec
I get this in the event viewer
"Event Type: Warning
Event Source: Userenv
Event Category: None
Event ID: 1517
Date: 29/03/2003
Time: 1:36:32 p.m.
User: NT AUTHORITY\SYSTEM
Computer: WEAPON
Description:
Windows saved user WEAPON registry while an application or service was still using the registry during log off. The memory used by the user's registry has not been freed. The registry will be unloaded when it is no longer in use.
This is often caused by services running as a user account, try configuring the services to run in either the LocalService or NetworkService account.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp."
and now my pc takes ages to shut down too, this only started happening last week so I have no idea whats causing it, anyone know? my profile is only like 120mb big
"Event Type: Warning
Event Source: Userenv
Event Category: None
Event ID: 1517
Date: 29/03/2003
Time: 1:36:32 p.m.
User: NT AUTHORITY\SYSTEM
Computer: WEAPON
Description:
Windows saved user WEAPON registry while an application or service was still using the registry during log off. The memory used by the user's registry has not been freed. The registry will be unloaded when it is no longer in use.
This is often caused by services running as a user account, try configuring the services to run in either the LocalService or NetworkService account.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp."
and now my pc takes ages to shut down too, this only started happening last week so I have no idea whats causing it, anyone know? my profile is only like 120mb big
