Cannot install/upgrade 5.0.6

[Kompiler]

Hi,

 

Have been running Paint.net perfectly fine for many years and absolutely love it.

Recently it attempted to automatically update to 5.0.6 and it failed due to an internal crash in .NET

 

As a software developer, I already have the .NET 7 SDK installed (along with Visual Studio 2022 etc).

 

I use multiple machines and the exact same issue has happened on all of them

 

I've attempted to use the web installer, MSI installer, x64 installer directly, all of which fail.

I have ensured there is no trace of Paint.net installed anywhere.

 

The error reported from the downloader is "Installation of paint.net failed (-1073741819, 0xC0000005)

 

Looking in the Event Viewer, shows 2 entries.

1. .NET Runtime

Application: SetupFrontEnd.exe
CoreCLR Version: 7.0.523.17405
.NET Version: 7.0.5
Description: The process was terminated due to an internal error in the .NET Runtime at IP 0x00007FFDD621FEAE (0x00007FFDD6180000) with exit code 0x80131506.

 

2. Application Error
Faulting application name: SetupFrontEnd.exe, version: 5.6.8544.33530, time stamp: 0x641de100
Faulting module name: coreclr.dll, version: 7.0.523.17405, time stamp: 0x641ddad2
Exception code: 0xc0000005
Fault offset: 0x000000000009feae
Faulting process id: 0x83c4
Faulting application start time: 0x01d99a6862422da2
Faulting application path: C:\Users\xyz\AppData\Local\Temp\2\7zS03063431\x64\SetupFrontEnd.exe
Faulting module path: C:\Users\xyz\AppData\Local\Temp\2\7zS03063431\x64\coreclr.dll
Report Id: 9bbc1838-1756-462e-8c34-fedfa3f4199d
Faulting package full name: 
Faulting package-relative application ID: 

 

I have uninstalled the .NET 7 SDK and reinstalled it to no avail.

 

I suspect this is caused by my machines being development boxes? Any help would be appreciated.

 

Cheers

 

[Rick Brewster]

This has nothing to do with the .NET 7 SDK being installed. Paint.NET uses Self-Contained Deployment which means it uses a local copy of .NET that it comes with.

 

As for the error, I have no idea. It's come up a handful of times (search the forum for 0xC0000005). It's probably some rare/niche system or hardware configuration issue that Microsoft doesn't know about. My guess would be you have some other software installed that's interfering with things.