Sign in to follow this  
moee

/createMsi not working for 4.0.8

Recommended Posts

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 title text of a progress window, which then automatically closes and the program ends. No signs of the extracted .msi-installers are found anywhere.

 

Command prompt was ran as administrator.

Share this post


Link to post
Share on other sites

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 support personnel or package vendor."

Should the .msi's include .NET Framework 4.6 installation?

Share this post


Link to post
Share on other sites

You must manage the installation of .NET separately from Paint.NET. That's always been true for all versions. The MSIs for paint.net have never included .NET.

The setup UI uses .NET so it makes sense that you'd have to install the right version of .NET before being able to use /createMsi.

If you're on Windows 8.1 then you may need to first catch up on Windows Updates before .NET 4.6.1 will stop being grumpy about installing. (Also, Windows 10 is a free upgrade. Please consider updating to it.)

I think Microsoft forgot to do some testing with the latest .NET installer ... it doesn't honor the /showFinal parameter (or whichever one is combined with /passive and means "do show an error at the end if there is one").

Share this post


Link to post
Share on other sites

Here's some more info: http://forums.getpaint.net/index.php?/topic/106705-paintnet-407-is-now-available/#entry509910

 

Look at the HTML file that Ishi posted: "The update corresponding to KB2919355 needs to be installed before you can install this product on Windows 8.1 or Windows Server 2012 R2."

 

This may or may not be the case on your system(s), but it shows that the .NET installer is just exiting instead of displaying the error message. *groan* Thanks Microsoft :(

 

The general formula seems to be 1) catch up on Windows Updates, 2) install .NET 4.6.1 if it isn't there already using the "web" installer, 3) install Paint.NET

 

The Paint.NET installer takes care of 2 automatically, which is then supposed to take care of 1 by way of at least showing an error message.

Share this post


Link to post
Share on other sites

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 compromise. The previously required .NET Framework versions have been, for what I've understood, rather widely built-in in the Windows OS's'.4.6.1. is not. I hope it's not just me hoping to see an up-to-date Paint.NET installer which a] supports <4.6.1 version of .NET Framework or b] includes the .NET Framework's required installation package (*)

(*) = Yup, the package is rather big as MB's (but as a separate installer it doesn't bother the rest of the users). Also I don't actually know if an unattended installation of .NET Framework is possible.

 

This is just discussion and suggestions, but the real thing is that at the moment I don't know how our environment can support the deployment of Paint.NET done as unattended installation.

Edited by moee

Share this post


Link to post
Share on other sites

I've deployed 4.6.1 to our enterprise via ConfigMgr.  Here is a HOW TO, just change the 4.5.2 to 4.6.1. However using ConfigMgr 2012 R2 Application Model, have run into an issue deploying the software. 
The command works fine when using elevated command prompt, and even when installed via the Catalog (user context), but when trying to install via System Context, it fails. Same results using psexec.exe (Installing as System).
Command Line: paint.net.4.0.8.install.exe /auto CHECKFORBETAS=0 DESKTOPSHORTCUT=0 CHECKFORUPDATES=0

Thoughts as to why Paint.Net does not install when using the SYSTEM account?

 

Update....
Using the CreateMsi Command (paint.net.4.0.8.install.exe /CreateMsi CHECKFORBETAS=0 DESKTOPSHORTCUT=0 CHECKFORUPDATES=0)
I've been able to to create the MSI files that do install as system.  This just means extra steps each time Paint.Net is released.  It was nice just downloading the .exe file and deploying that, which worked on either x86 or x64 machines, now I have to extract the MSI, create different deployments for x86 or x64.
But at least it works, and I can deploy with ConfigMgr.

Edited by gwblok

Share this post


Link to post
Share on other sites
The previously required .NET Framework versions have been, for what I've understood, rather widely built-in in the Windows OS

Sort of :) 

 

Paint.NET 4.0 through 4.0.6 used .NET 4.5 which is built-in to Windows 8+, but not on Windows 7.

Paint.NET 3.5 through 3.5.11 used .NET 3.5 SP1 which is built-in to Windows 7, but not on Vista or XP (which were still supported).

 

Previous versions of Paint.NET used .NET 2.0, or even 1.1 (for v2.1 and before). Here's the full .NET + Windows version history: https://en.wikipedia.org/wiki/.NET_Framework_version_history

 

I don't know how our environment can support the deployment of Paint.NET done as unattended installation.

.NET itself supports unattended installation so I'm not sure why this would be an issue? It's a good idea to keep up with .NET updates, just like it's a good idea to keep up with Windows Updates.

 

As for the PDN setup exe bundling the .NET 4.6.1 installer, I'm not sure what this would solve. Unattended installation of Paint.NET via MSI has never included installation of .NET, you've always had to deal with that separately. It's the setup EXE that does chaining of .NET + Paint.NET installation, and that requires showing a UI.

 

If you can push down the Paint.NET installer exe and run it with "/auto" (as described at http://www.getpaint.net/doc/latest/UnattendedInstallation.html) then that'll do .NET as well. You just can't do an MSI push and also get .NET installed.

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Sign in to follow this