Unattended Paint.NET install fails (setupfrontend.exe)

Today I tried to do a companywide unattended install of Paint.NET with SCCM 2007. I was using the following command:

Paint.NET.3.5.8.Install.exe /auto CHECKFORUPDATES=0 DESKTOPSHORTCUT=0

However, over 50% of the installations failed on the clients. The eventlog on all the failed clients reported the following:

Log Name:      Application
Source:        Windows Error Reporting
Event ID:      1001
Level:         Information
Description:
Fault bucket , type 0
Event Name: CLR20r3
Response: Not available
Cab Id: 0

Problem signature:
P1: setupfrontend.exe
P2: 3.58.4081.24584
P3: 4d72ad90
P4: System.Windows.Forms
P5: 2.0.0.0
P6: 4a275ebd
P7: 48b9
P8: 9a
P9: System.InvalidOperationException
P10:

Attached files:
These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_setupfrontend.ex_c9eddcc15670ad89f3ac499ae465e29357788750_1037de30

Analysis symbol:
Rechecking for solution: 0
Report Id: e32740db-ded0-11e0-90ac-6c626d9a30f3
Report Status: 4

Many sources on the internet report that a re-install of .NET Framework solves the problem. However, that’s not a best practice if you have to install it on 200 clients. :-) You never know the consequences for other applications. Therefor I decided to use the /createMsi parameter. This creates an MSI-package from the original compressed .exe installer. The file will be placed on your desktop:

Paint.NET.3.5.8.Install.exe /createMsi

With the created MSI, PaintDotNet.x64.msi, I was able to distribute Paint.net to all desktops. No errors:

PaintDotNet.x64.msi /quiet

Note that in my case I used the x64 installer, because I have 64bit machines with a 64bit OS. If you’re running 64bits machines with an 32bit OS, use the x86 installer (PaintDotNet.x86.msi) instead!

Leave a Reply

1 Comment on "Unattended Paint.NET install fails (setupfrontend.exe)"

Notify of
avatar
Sort by:   newest | oldest | most voted
Nick
Guest

Thanks
Very helpful

wpDiscuz