shortermemory
9th December 2008 11:15 UTC

Problem on system usage of Temp folder
Hi All,

I have a script here that I am using for some time now and it's working good, until earlier today. When I checked, the source of the problem is in our Anti-virus configuration. Our antivirus server has uploaded new policies that prevent execution of files (including DLLs) from the Temp folder.

I have no rights to disable that policy so now, I can't execute the installer that I have created. This is because the antivirus blocks the execution of system.dll from temp folder (See the attachment for the antivirus logs).

I don't think I have any control on where the system.dll (and other NSIS related files) is extracted during the initialization of the installer, or do I have?

If so, can you help me on that?

Thanks and more power to NSIS!

-Joel

Anders
9th December 2008 11:44 UTC

you could extract the plugin somewhere else and call it with callinstdll, but its probably better to bitch to the AV vendor and tell them its a stupid thing to do, or even better don't use mcafee

shortermemory
9th December 2008 11:58 UTC

Thanks Anders,

Maybe this will work.

I really don't like the idea on what they are doing with the policies of that AV. I don't have any control with regards to this AV thing. It's a company policy.
Honestly, I'd prefer avast rather than mcafee but I don't have a choice here.

Anyway, I'll post the result here once I got one.
Thanks again!

shortermemory
10th December 2008 06:54 UTC

Hi again,

The alternative didn't work. But I guess the reason is, I still haven't converted all the dll calls to CallInstDLL in all of the files including all the includes.

But guess what! They've removed/rolled-back the policy just today. After I've worked on this for almost 2 days! Maybe the AV server admin got sued by other people that has the same problems like me. 'bout time...

Anyway, thanks again! I'll just save all the resources I've got here in case the policy is once again implemented.

This link is almost related to this forum for reference: Click here
I think this one can be useful.

kichik
10th December 2008 21:49 UTC

If this ever happens again, a simpler approach of working around it would be to set $PLUGINSDIR on your own using the ChngVrbl plug-in.