I’ll summarize the issue:
If you modify “firefox.exe” with a Resource Editor (e.g. change the version or icons), the file is no longer signed and Avast loads tens of extra DLLs when running the file (you can see those DLLs by creating a dump file).
I’m looking for a way to make Avast treat the modified unsigned “firefox.exe” as it treats the original signed “firefox.exe”.
A rep from Avast support hasn’t been able to help me, but sometimes a clever user might think of a good solution.
I currently don’t have Avast installed.
If you reply, may I ask you to test your suggestion yourself? - I’d highly appreciate that.
I honestly don’t see why you would want to start this new topic and have people flip flop back and forth to get information - if this is related to the original topic.
It seems the problem is more general: a difference between signed and unsigned executable files.
I assume the same issue is relevant to Chrome as well.
If you still think it’s better to unite the topics, I’ll do that.
It is just if ‘you’ feel they are somehow related - if that is the case (and I don’t have that issue on my system) then those whom it does effect would benefit from the information being combined.
