Is that not the way your version works? If it doesn't do "handle
remapping," what does it do? How do YOU learn what program is the culprit?
My version closes the handles on the offending process. I.e. lsass.exe is
the culprit that I always see in my Event ID: 1201s. At least the ones that
I've bothered to read. ;-)
Event Type: Information
Event Source: UPHClean
Event Category: None
Event ID: 1201
Date: 7/30/2005
Time: 10:41:39 PM
User: MYPENTIUM450\Wesley P. Vogel
Computer: MYPENTIUM450
Description:
The following handles in user profile hive MYPENTIUM450\Wesley P. Vogel
(S-1-5-21-1708537768-15xxxx6667-1202660629-1003) have been closed because
they were preventing the profile from unloading successfully:
lsass.exe (436) HKCU (0x3f8)
------
Event Type: Information
Event Source: UPHClean
Event Category: None
Event ID: 1201
Date: 10/22/2005
Time: 3:44:07 PM
User: MYPENTIUM450\Wesley P. Vogel
Computer: MYPENTIUM450
Description:
The following handles in user profile hive MYPENTIUM450\Wesley P. Vogel
(S-1-5-21-1708537768-15xxxx667-1202660629-1003) have been closed because
they were preventing the profile from unloading successfully:
lsass.exe (440) HKCU (0x3c4)
------
For HKCU (0x3f8) & HKCU (0x3c4) HKCU is the HKEY_CURRENT_USER registry hive.
(0x3f8) & (0x3c4) must be the memory locations, just a guess.
I assume that for lsass.exe (436) & lsass.exe (440), (436) & (440) were the
PID #s for lsass.exe on those dates.
PID is Process ID or process identifier. These numbers change every time
you reboot. I think that they are just an arbitrarily assigned number.
Each process has a different number while running. A process can also have
a different PID if opened and closed, etc.
------
If
HKLM\System\CurrentControlSet\Services\UPHClean\Parameters\REPORT_ONLY
is set to 1, UPHClean will NOT take action to allow profiles to unload. All
it does is make a log somewhere.
Make sure that it is set 0 (zero).
I do not know its name or location, but I would guess that it's be in C:\ or
C:\WINDOWS or look at C:\WINDOWS\Debug\UserMode\userenv.log userenv.log
also seems to list Profile or registry hive load, unload, or deletion
failures. I think that you can only get userenv.log with Windows XP
Professional because it also reports on Group Policy.
--
Hope this helps. Let us know.
Wes
MS-MVP Windows Shell/User
In