Gadget

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

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.

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.

Thanks, Toe!

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%?