UPHClean v2.0 is a new version that tries to help with the following scenarios:
In v1.6 there is a timing issue with where the profile unload process stopped trying to unload the user profile hive before UPHClean finished its work. UPHClean finished its release of user profile hive handles but Winlogon had already proceeded without unloading the profile causing it to report a profile hive unload failure. This is now addressed by having Winlogon waiting until UPHClean has finished all of its work before proceeding.
Open file handles
Apart open registry handles that UPHClean v1.6 deals with open file handles to the user profile can have a bad influence on the profile load and unload process. Open references to profile files prevent the profile load and unload process from reconciling (copying files) from and to the roaming profile location. This prevents the deletion of the locally cached profile. Other symptoms of this is if the same user logs in again he or she gets a new profile with a name like username.000, username.001 etc.
UPHClean v2.0 takes care of these by releasing the handle to user profile files when the profile is unloaded. This is not without risk. Since UPHClean removes access to files or directories data that was cached by the application for the file is lost. This could cause the process to fail because it cannot read from the file. During testing this has not been found to be true but there is still a chance that it could happen. This is the reason why the file handle remap feature is disabled by default.
To enable the feature you have to set the following registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\UPHClean\ParametersSHARING_VIOLATION_REMAP REG_DWORD 0X00000001
Without enabling the remapping feature UPHClean automatically detects sharing violation during the user logoff and retries the failed operation for a small amount of time. You can control the amount of time using the SHARING_VIOLATION_DELAY value. This value is specified in millisecond and has a default value of 1000 millisecond.
In some cases a program might change file permissions or creates a new file/folder within the profile but incorrect permissions. This may leave the profile load/unload process unable to copy it or delete it. To resolve the issue you have to take ownership first before you can delete the file or folder. UPHClean takes care of those situations.
Real world problems
Here are actual scenarios that UPHClean v2.0 resolves:
It will be supported on Windows 2000 (all versions), Windows XP, Windows Server 2003, Windows Vista, Windows Server 2008. It will be available for 32 bit and 64 bit platforms. There are beta bit available for 32 and 64 bit platforms for all Windows 2000, Windows XP, and Windows Server 2003.
PingBack from http://lane.greatvideonews.info/uphclean.html
In the attachment below you will find the UPHClean v2.0 build 18.104.22.168 beta bits. See my blog post here
In the attachment below you will find the UPHClean v2.0 beta bits for operating system running on 64
Is there a UPHClean v2.0 GA release available or an ETA for when this release might be available?
i installed the latest v2.0 beta for x64 and have still the 255 char problem.
event id 1509 appears --> Filename too long
any ideas about that?
Upon installing this I receive ….
“This installation package is not supported by this processor type. Contact your product vendor.”
The UPHClean v2.0 beta bits for operating system running on 64 bit platform (AMD or Intel x64 -- not Intel Itanium).” So I verified my system properties of the server: Intel Xeon E5440 @ 2.83Hz w/ 8 GB RAM. What gives!!!
Keen on using this on our domain PCs as having the Java hsperfdata issue a lot and causing roaming profile not to unload completely. I notice this is an old thread, is an official non-beta release available yet for Win XP Pro SP3 32bit?
I could not find link to download Uphclean 2.0