This was an issue I experienced a lot more often in Windows XP. I thought I would be rid of now, but I was wrong. It appears some applications, specifically ones related to services, in our case Symantec Endpoint Protection, fails to properly release handles to the registry keys. Obviously nothing new. And no, I do not use BitLocker in this instance and I am pretty sure we have not enabled tamper protection (it is not a BIOS default and we are lazy like that). It appears UPHClean might not be supported on Windows 7 at all. Is there some other way to force registry handles to get shut off?

link|improve this question

59% accept rate
feedback

2 Answers

This is a really interesting issue because theoretically UPHClean is not necessary. The functionality of UPHClean is included in the Windows Vista and Windows Server 2008 User Profile Service as said here.

link|improve this answer
feedback

Procexp can close handles. Use Find->Find Handle or DLL to find the one you want, click it (it will appear in a list in the bottom pane) and right click->close.

link|improve this answer
Not sure how that will programmatically during shutdown, but thanks. A while back, I though of just using though super-badass handle utility to solve that problem, but how it operates requires a lot of scripting to determine the right PID's to operate on. – alharaka Feb 16 at 8:28
Ah, programmatically close the handles - thought the question seemed a little easy :) The handle tool would have been my next suggestion but I imagine one would indeed have to be quite the batch ninja to fix your problem in a script. – Matt Lyons Feb 17 at 11:47
Tell me about it, hence I gave up. Users are confined by Windows, admins roll their eyes and thank God Linux is an alternative for people who need fuctional computers on their own terms. Haha. – alharaka Feb 19 at 8:15
feedback

Your Answer

 
or
required, but never shown

Not the answer you're looking for? Browse other questions tagged or ask your own question.