Thanks to UPHClean, I’ve bee able to find out why my profiles are refusing to unload on shutdowns and reboots.
Log:
Event Type: Information
Event Source: UPHClean
Event Category: None
Event ID: 1401
Date: 9/9/2007
Time: 1:42:08 AM
User: COMPUTER\Administrator
Computer: COMPUTER
Description:
The following handles in user profile hive COMPUTER\Administrator (S-1-5-21-) have been remapped because they were preventing the profile from unloading successfully:
If Windows and all applications run on it functioned in a perfect fashion (which they obviously don’t) there wouldn’t be a need for UPHC.
I don’t know whether this is a bug in CFP, or something due to specific configuration; if it’s a bug in CFP, it’s not one that impacts all users (which makes it difficult to track and resolve).
What version of CFP are you running?
What other active security and utility software do you have running?
The log clearly states it is caused by Comodo. I have spoken with Microsoft and they have confirmed that it’s a Comodo issue. I have also confirmed that others are having the same issue, and it also occurs on other machines in my household.
Nice to hear that this bug has been confirmed by others as well. Hopefully v3 will have the fix and for those wishing to stay with v2 there can be a minor update to resolve the issue.
here’s the situation:
file a support ticket - Comodo staff pass it to the devs, but they’re all busy at CFP 3 right now
or
beta version 3 right now and see if it works for your computer
Also, this issue is affecting everyone that I’ve spoken with. Most users may not notice it with or without UPHClean. But if many people are posting about it then clearly there is an issue.
http://support.comodo.com/ You will need to create a login there; the forum login does not cross over. Also, you will have to navigate through the options to get to the Desktop Security Products and select Firewall; it does not default there.
Be sure to let them know that you have already been in the forums (providing them a link to this thread would be a good idea), and that a Moderator in the forums requested you file a ticket with Support.
Be sure to keep us apprised of their response, and be patient, as the majority of resources are going into finalizing v3 at the moment.
Is there a reason why this issue has been set to closed? Due to it being an ongoing issue, including in v3.0 of the firewall; I would think this should remain open.