The dreaded "Cannot unload registry"

[Sen7inel]

I've been away from "scene" for some time. Now, in multi-user roaming-profiles environment there was this UserEnv-error:

Windows cannot unload your registry file. If you have a roaming profile, your settings are not replicated. Contact your administrator.

DETAIL - Access is denied. , Build number ((2195)).

When I last looked into it, this was the most popular question on microsoft.public.win2000 or whatever. No solution was available then. What about now?

 

[DanielKBates]

i've had this too. what does it mean and what problems does it cause.

 

[DanielKBates]

http://support.microsoft.com/suppor...not &rnk=3&src=DHCS_MSPSS_gn_SRCH&SPR=WIN2000

Go to the above link. This may help.

 

[Sen7inel]

SP1 didn't fix this, as we've never run the initial version of W2k and still had the problem. What was new to me in that KB article was the IE SP2 fix. For now, that fixed the problem.

 

[raptor85]

Hey, this might not work in your case; however, recently I noticed this problem on my systems every time I shut down. I managed to stumble on the Userenv.log which had the line Bla Bla failed due to open registry key. If you use Regedit much at all make sure you close out all registry trees that are open. Worked great for me, even saves 20 or so seconds of hang on shutdown.

 

[GaryRumson]

Symptom: 60 seconds additional delay in shutting down or logging off Win2K. The problem is described under this heading already, but it is appearing again (apparently) as a result of Win2K critical update Q329170, 12 December 2002. Work-around is as already noted:
Run gpedit.msc. In local computer policy, change "Maximum retries to unload and update user profile" to far less than its default 60. Find this setting under Group Policy Editor > Local Computer Policy > Computer Config > Admin Templates > System > Logon. I set mine to 5 tries (5 seconds).


This will work

 

[jonwilbanks]

For a long list of this problem and various resolutions go to

http://www.eventid.net

and search for event id 1000.