Installer Location Problem

[Gadget]

We have group policies in place to prevent applications from executing under the %AppData% and %LocalAppData% folders, as a first-line defense against cryptolocker/cryptowall type trojans.

 

This creates a problem for a number of installers that extract a setup program to %LocalAppData%/Temp (or a folder with the company/program name) and execute the setup program from there.  Including the installer for Paint.Net.

 

Any way you guys can provide an installer that utilizes the Windows/Temp folder, or a user-defined extraction location instead of trying to run from %LocalAppData%?

 

 

 

 

[toe_head2001]

If you open up the 'paint.net.4.0.6.install.exe' file with your archive program (e.x. 7-Zip), you can extract the install files anywhere you want. Once they have been extracted, run the file called 'SetupShim.exe'. After the installation has completed, you can delete the install files.

[Gadget]

Thanks, Toe!

[Gadget]

Hmm.  That didn't actually work.

 

 

System.IO.FileNotFoundException: Could not load file or assembly 'PaintDotNet, Version=4.6.5693.28, Culture=neutral, PublicKeyToken=null' or one of its dependencies.  The system cannot find the file specified.

 

yadda

 

at PaintDotNet.Setup.SetupWizard.MainImpl(String[] args)

at PaintDotNet.Setup.SetupWizard.Main(String[] args) in d:\src\pdn\paintdotnet\src\SetupFrontEnd\SetupWizard.cs:line 923

 

 

 

 

Trying to just install from the PaintDotNet_x64.msi doesn't work, it just tells me that it has to be installed using the setup wizard.

[toe_head2001]

I do apologize. Perhaps it worked for me, because I had it previously installed.

[Rick Brewster]

The solution is to talk to your administrator and have them remove this restriction, or at least to white-list the paint.net installer or to deploy it directly or something.

 

Trying to force the installer to work in a way that it's not designed or tested for will probably not end well. Work with your system admins on this, don't try to go around them.

[Gadget]

Actually, I am the administrator.  Since the installer has the program version number in the file name, and these policy exceptions don't recognize wildcards, I would have to set a new policy exception every time you release a new version.

[Rick Brewster]

Are you trying to install on 1 system, or deploy across the whole network?

[Gadget]

1 System.  Not enough to justify mucking with the Group Policies.

[Rick Brewster]

Also not enough for me to modify the installer to accomodate this but you can do this,

 

1. Run the installer exe (e.g. paint.net.4.0.6.install.exe) on a system that does not have this restriction.

2. When the setup wizard pops up, don't click on anything.

3. Instead, copy the %TEMP%\PdnSetup folder to the system where you do want to install it.

4. And then, over on that 2nd system, run PdnSetup\SetupWizard.exe 

 

You'll have to do this for every update that comes out.