avionixx Posted January 8, 2016 Share Posted January 8, 2016 We use Paint.Net in an enterprise environment and use the MSI to for deployment and have never had a problem with it in the previous version we were using (4.0.6), but the latest version produces the "to install this product, use the setup wizard" error. The MSI was generated using the /skipConfig /auto /createMSI switches like we've done with the past and the MSI is installed using the /i /passive switches. Thank you in advance for your help! Quote Link to comment Share on other sites More sharing options...
Rick Brewster Posted January 9, 2016 Share Posted January 9, 2016 I just tested and it's working fine here ... /createMsi is used by itself though. It doesn't go along with /skipConfig and /auto. (and /auto is a superset of /skipConfig) Quote The Paint.NET Blog: https://blog.getpaint.net/ Donations are always appreciated! https://www.getpaint.net/donate.html Link to comment Share on other sites More sharing options...
avionixx Posted January 9, 2016 Author Share Posted January 9, 2016 Just out of curiosity, what version of Windows are you running? We're using Windows 8.1. I tried using only the /createMSI, but it still gives the same message. In Event Viewer, it says error 1603 when attempting a silent install with the MSI. Quote Link to comment Share on other sites More sharing options...
Rick Brewster Posted January 9, 2016 Share Posted January 9, 2016 I was using a mostly fresh and empty Windows 7 SP1 virtual machine. Are you uninstalling 4.0.6 before running the new installation of 4.0.9? Quote The Paint.NET Blog: https://blog.getpaint.net/ Donations are always appreciated! https://www.getpaint.net/donate.html Link to comment Share on other sites More sharing options...
Rick Brewster Posted January 9, 2016 Share Posted January 9, 2016 Another card you can have up your sleeve is to try applying the MSI property USINGWIZARD=1. (I'm rusty in this area, I don't remember if you have to bake this into the MSI or if msiexec can be told to do this) Quote The Paint.NET Blog: https://blog.getpaint.net/ Donations are always appreciated! https://www.getpaint.net/donate.html Link to comment Share on other sites More sharing options...
avionixx Posted January 9, 2016 Author Share Posted January 9, 2016 In past deployments, we did not uninstall the previous version; the updated version just installed right on top of the existing one. Though I have tried uninstalling the previous version first and running the new MSI again, but same issue. As per the Unattended Install docs, I used /createMSI USINGWIZARD=1, but still getting the same message. Quote Link to comment Share on other sites More sharing options...
avionixx Posted January 18, 2016 Author Share Posted January 18, 2016 Just wanted to add the solution to this problem. The DotNet 4.6 installation launched by the Paint.Net installer was not completing successfully because it required a reboot to finish and this prevented the creation of working MSI files. The solution was to download the offline DotNet 4.6 installer from Microsoft, install it, then run the Paint.net installer again and it will skip the DotNet install completely and go straight to MSI creation. Client computers will still need DotNet 4.6 installed before Paint.Net will install using the created MSIs. Quote Link to comment Share on other sites More sharing options...
Rick Brewster Posted January 19, 2016 Share Posted January 19, 2016 Oh, it's always been the case that you had to manage .NET's installation separately. MSI installation doesn't auto-install .NET, that's a function of the SetupShim.exe chainer. Sure is a weird error message to be showing though. Quote The Paint.NET Blog: https://blog.getpaint.net/ Donations are always appreciated! https://www.getpaint.net/donate.html Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.