moee

You are probably right at every aspect for what you said. I don't think I'm the only user representing the group of enterprise environment users with the following situation: 1. does not support W10 2. does not allow updating to W10 3. does not push/force installation of .NET Framework 4.6.1 ... + 4. loves to use Paint.NET This causes usability issues for a minor(/major) group of users - considering the .NET Framework isn't pre-installed the Paint.NET can't either be installed as unattended installation. As .NET Frameworks are quite rigid I'd say this would require some sort of com

After manually installing the .NET Framework 4.6 & re-booting, then running the /createMsi, the command succeeded as expected. This leads to next issues: The now required .NET Framework 4.6 is however now causing issues with silent installation I'm doing with the .msi's. The installation turns out as failed if the computer doesn't already have .NET Framework 4.6 installed. When running the .msi manually (attended), the installer fails with an error "There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your suppor

As posted on the blog post of 4.0.8 release: I’ve previously extracted the .msi-installers with “paint.net.x.y.z.install /createMsi” -command, but that doesn’t seem to work with this (using W8.1). Apparently the .msi is available also manually extracting the .msi so not a big issue. Just wanted to point out in case the feature was supposed to work. Actually what happens is that the installer seems to start and a prompt will appear as following: "The following will be installed: * .NET Framework 4.6.1 * paint.net" By clicking "OK" the program seems to do some extracting based on the