J
JD
I have the latest version of UPHClean. The accompanying Readme states:
By default UPHClean takes action to allow profiles to unload. You can choose
to have UPHClean only report what processes it finds preventing profiles
from unloading. To do this, install UPHClean and use the registry editor to
set:
HKLM\System\CurrentControlSet\Services\UPHClean\Parameters\REPORT_ONLY to 1.
You can also have UPHClean log the call stack that is responsible for the
profile hive handle. This is necessary to find out what software is
responsible for the hive handle in processes used for many purposes (e.g.
svchost.exe, dllhost.exe, winmgmt.exe). To enable call stack logging use the
registry editor to set:
HKLM\System\CurrentControlSet\Services\UPHClean\Parameters\CALLSTACK_LOG to
1.
Logging the call stack is computationally and memory intensive. You should
use this option to collect information and then turn it off. To get more
accurate call stack logging it may be necessary to get symbols installed on
the computer. You can read about getting symbols at:
http://www.microsoft.com/whdc/ddk/debugging/symbols.mspx
I've made these registry changes, but am at a loss as to how to locate and
read the "log" that will identify the offending software.
Any help will be appreciated.
By default UPHClean takes action to allow profiles to unload. You can choose
to have UPHClean only report what processes it finds preventing profiles
from unloading. To do this, install UPHClean and use the registry editor to
set:
HKLM\System\CurrentControlSet\Services\UPHClean\Parameters\REPORT_ONLY to 1.
You can also have UPHClean log the call stack that is responsible for the
profile hive handle. This is necessary to find out what software is
responsible for the hive handle in processes used for many purposes (e.g.
svchost.exe, dllhost.exe, winmgmt.exe). To enable call stack logging use the
registry editor to set:
HKLM\System\CurrentControlSet\Services\UPHClean\Parameters\CALLSTACK_LOG to
1.
Logging the call stack is computationally and memory intensive. You should
use this option to collect information and then turn it off. To get more
accurate call stack logging it may be necessary to get symbols installed on
the computer. You can read about getting symbols at:
http://www.microsoft.com/whdc/ddk/debugging/symbols.mspx
I've made these registry changes, but am at a loss as to how to locate and
read the "log" that will identify the offending software.
Any help will be appreciated.