I having this show up as a warning in Event Viewer: Windows detected your registry file is still in use by other applications or services. The file will be unloaded now. The applications or services that hold your registry file may not function properly afterwards. DETAIL - 2 user registry handles leaked from \Registry\User\S-1-5-21-1105562303-4136911539-4224694939-1001: Process 2504 (\Device\HarddiskVolume2\Windows\System32\msiexec.exe) has opened key \REGISTRY\USER\S-1-5-21-1105562303-4136911539-4224694939-1001\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExts Process 2504 (\Device\HarddiskVolume2\Windows\System32\msiexec.exe) has opened key \REGISTRY\USER\S-1-5-21-1105562303-4136911539-4224694939-1001\Software\Microsoft\Windows\CurrentVersion\Explorer The computer seems to be running normally, but I'd still like to find a solution. Thanks.

Hi WaywardPlease see the following Knowledgebase Article for a description of this process.Event ID: 1530 may be logged in the Application log on a Windows Vista-based client computerHope this helps.Thank You for testing Windows 7 Ronnie Vernon MVP

I'm no longer getting the error related to msiexec.exe. Now it's with CTxfispi.exe. Windows detected your registry file is still in use by other applications or services. The file will be unloaded now. The applications or services that hold your registry file may not function properly afterwards. DETAIL - 1 user registry handles leaked from \Registry\User\S-1-5-21-1105562303-4136911539-4224694939-1001_Classes: Process 2676 (\Device\HarddiskVolume2\Windows\SysWOW64\CTxfispi.exe) has opened key \REGISTRY\USER\S-1-5-21-1105562303-4136911539-4224694939-1001_CLASSES

Hi Wayward A description of this subject goes back to the era of NT4, Windows 2000, Windows XP, and Windows Server 2003. The problems would occur when profiles were not fully unloaded because some process, which could be any driver, application, or service, would still maintain hooks into a users profile registry hive, when the system was shut down or a user logged off. It was mainly a problem that was seen in roaming profile situations, but it also happened on standalone systems. The result would be that the profile would be corrupted and the next time that user logged on they would receive a message similar to "Windows cannot log you on because your profile cannot be loaded." Microsoft developed a utility called UPHClean, which, when installed, runs automatically when a system is shut down or a user logs off. It checks for any service, application, or driver that may still have the users registry hive open and cleans them up, thereby letting a users profile unload cleanly. During the Windows Vista beta, a version (2.0) of UPHClean was being developed for Vista, but the decision was made to integrate this component into the system for better stability. The reason for this was that a user would not normally install this utility until after a problem occurred. You can read some of the history about this issue in the following KB article. You experience log off problems on a Windows XP-based, Windows Server 2003-based, Windows 2000-based, or Windows NT 4.0-based computer In your case, the msiexec.exe (Windows Installer Service) and the CTxfispi.exe (Creative Audio Driver) were the culprits. The bottom line is that seeing these warnings in the Event Viewer shows that this component is working to keep your system stable. I hope this information is useful. Thank You for testing Windows 7 Ronnie Vernon MVP