I readed a solution on: http://forums.comodo.com/bug-report-cis/cu...l-t56839.0.html
Thanks D, I also looked at this but I guess I don't understand what the solution is? Granted I'm no programmer, but it's unclear to me what exactly the fix is? I get the uneasy feeling this is going to be a real pain in the neck to resolve.
He says in the post:
"I installed EMSI AntiMalware .... rebooted... still the message was gone!
I then installed Comodo Firewall... and boom the "Custom Dynamic Link" error returned only now it listed in the details StringCount 1 and pointed me to "C:\Windows\system32\guard64.dll" ... I finally had tracked it down!
I then found this thread and decided to post this here since my previous google searches didn't help me locate the cause!
So now at least I know its comodo doing it... but... if they are indeed using LoadAppInit_DLLs to inject it ... why is it still not defined in "AppInit_DLLs"?
Is this some leftover flipping of the flag that it no longer used by comodo?
Edit: upon closer inspection I found that "AppInit_DLLs" has a blank space inserted in there after the comodo install... is that the cause of all this? Perhaps the hook used to be injected in there and they removed it but left a space character (the official separator that is to be used in that key entry)"
Sounds like possibly removing the space he's referring to might be the solution? First I'll try to reinstall the latest version downloaded from Comodo and hopefully they've fixed it (though I'm doubtful). Thanks again. -- S