Windows cannot unload your registry file

Around 200 users experiencing this problem on 2000
professional and XP Pro. Receive the following error at
logoff machine's take exactly 60 seconds ....

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)).

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

There are 2 solutions to this on microsoft website but
neither is appropriate. 1st solution is to do with
roaming profiles on NT servers, we do not use roaming
profiles. 2nd solution mentions fix in IE 5 SP1, we are
running IE6.

Control Panel|Add/Remove Programs if Q329170 is listed, try uninstalling it.
You don't need it unless this applies.

http://www.microsoft.com/technet/tr...in/MS02-070.asp

--
Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft MVP [Windows NT/2000 Operating Systems]

"Edd Casher" wrote:
> Around 200 users experiencing this problem on 2000
> professional and XP Pro. Receive the following error at
> logoff machine's take exactly 60 seconds ....
>
> 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)).
>
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
>
> There are 2 solutions to this on microsoft website but
> neither is appropriate. 1st solution is to do with
> roaming profiles on NT servers, we do not use roaming
> profiles. 2nd solution mentions fix in IE 5 SP1, we are
> running IE6.

Edd Casher wrote in news:263501c33f19$251c74a0$a401280a@phx.gbl:

> Around 200 users experiencing this problem on 2000
> professional and XP Pro. Receive the following error at
> logoff machine's take exactly 60 seconds ....
>
> 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)).
>
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
>
> There are 2 solutions to this on microsoft website but
> neither is appropriate. 1st solution is to do with
> roaming profiles on NT servers, we do not use roaming
> profiles. 2nd solution mentions fix in IE 5 SP1, we are
> running IE6.

See "Dave"'s tip first. It is often the problem.

In addition you can shorten the wait time in the registry. But that
is just a cosmetic fix. You can try (to see if it makes the
difference) stopping SPOOLER Service prior to logoff. You can try
SP4 (yet another SP that is supposed to fix this).

I have recently ran into this problem while running Star
Wars Galaxies Online. I only get this problem when it's
running, besides that my machine shuts down rather slowly.
I am not looking forward to doing what a clean install of
my system.

>-----Original Message-----
>I don't have the answer, but a fresh install with SP4
fixed this for me.
>
>I have read that this can be due to a driver or service
not releasing its
>hold on the user profile registry hive.
>I wish I knew. The problem sure is annoying.
>
>
>"Edd Casher" <edd.casher@uk.kcadeutag.com> wrote in
message
>news:263501c33f19$251c74a0$a401280a@phx.gbl...
>> Around 200 users experiencing this problem on 2000
>> professional and XP Pro. Receive the following error at
>> logoff machine's take exactly 60 seconds ....
>>
>> 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)).
>>
>> For more information, see Help and Support Center at
>> http://go.microsoft.com/fwlink/events.asp.
>>
>> There are 2 solutions to this on microsoft website but
>> neither is appropriate. 1st solution is to do with
>> roaming profiles on NT servers, we do not use roaming
>> profiles. 2nd solution mentions fix in IE 5 SP1, we are
>> running IE6.
>
>
>.
>