UPHClean fails to install on Windows Vista and Windows Server 2008. This happens because the User Profile service included with those operating system includes the functionality of UPHClean v1.6 built in. There is no point in having UPHClean perform its monitoring work when the profile service does all necessary work to prevent user hive fails from occuring.
Whereas UPHClean logs event 1401 to indicate that it took action to resolve a problem that would have prevent a user profile hive from unloading, the User Profile service logs event 1530. It looks like this:
Log Name: ApplicationSource: Microsoft-Windows-User Profiles ServiceDate: 2/28/2008 2:56:52 PMEvent ID: 1530Task Category: NoneLevel: WarningKeywords: ClassicUser: SYSTEMComputer: RCARON-PCDescription:Windows detected your registry file is still in use by other applications orservices. The file will be unloaded now. The applications or services thathold your registry file may not function properly afterwards.DETAIL -1 user registry handles leaked from\Registry\User\S-1-5-21-2641105361-2081720548-7543625-1000:Process 896 (\Device\HarddiskVolume1\Windows\System32\svchost. exe) hasopened key \REGISTRY\USER\S-1-5-21-2641105361-2081720548-7543625-1000
This event is letting you know that when the profile was being unloaded svchost.exe with process id (PID) 896 had a registry key handle to the profile hive for the user with SID S-1-5-21-2641105361-2081720548-7543625-1000.
The event is there so you know that the system took action. That way you could know that if the application fails in some way you can investigate whether this action might be involved in the failure. Generally my advice for this (as for UPHClean event 1401) is to ignore it.
I am working on UPHClean v2.0. This version will address many more user profile problem scenarios. This version will likely install on Windows Vista and Windows Server 2008. It is in beta but currently the beta bits do not yet install on those operating systems.