This is a hotfix for 4.1.2 that fixes the crash that people were seeing on old DirectX 9 era GPUs like the NVIDIA GeForce 7000 series (not to be confused with the much newer GeForce 700 series). This release will fall back to software rendering for affected GPUs, although I’m hoping to reinstate hardware acceleration in the next update.
As a reminder, 4.1.2 (and 4.1.3 of course) addresses two security vulnerabilities. As such, administrators who managed deployments of Paint.NET are urged to begin the update process immediately. Everyone else is also urged to update as soon as possible, of course.
If you’re using the Windows Store release, you should get the update automatically within the next 24 hours. You can also force an update check by following these instructions.
For the Classic release, you can use the built-in updater by going to ⚙ Settings → Updates → Check Now. You can also download and install it directly from the website.
Change log:
- Fixed a crash when zooming due to missing pixel shader support on DX9 class GPUs (NVIDIA nForce, GeForce 7000 series, Matrox M9140, etc.)
Enjoy!
paint.net blog 
Sorry, but from the Documentation it is not clear for me, if .NET 4.7 is enough for this version, or we need a higher version? Thanks.
.NET 4.7 is required, but I recommend updating to 4.7.2.
The system requirements are laid out on the download page, https://www.getpaint.net/download.html
Also, if you try to install Paint.NET and you don’t have the right .NET version installed then it will tell you and then it’ll go ahead and install it. It’s intended to be easy 🙂
Yea, I know thanks. Was just curious, which is the minimum version that the software checks during the installation.
It checks for 4.7+, and will install 4.7.2 if it doesn’t find it.
The minimum requirement is still 4.7 because of various other reasons, like minimum OS for the Store version being tied to the .NET Framework installation. There’s no way to specify “this app requires Win10 v1607 and .NET 4.7.2″, you can only say “this app requires Win10 v1607”, and v1607 happens to come with 4.7. I’m not willing to bump up the minimum OS version for the sake of getting +0.0.2 on the .NET Framework.
How correct detect 4.8?
https://blogs.msdn.microsoft.com/dotnet/2018/09/17/announcing-net-framework-4-8-early-access-build-3646/
.NET 4.8 isn’t finalized yet, and probably won’t be required by Paint.NET for awhile. Once it is finalized, I’ll include it in the installer, assuming it doesn’t greatly increase the download size.
What about .NET Core (3)?
https://github.com/dotnet/core-setup/blob/master/README.md#daily-builds
https://blogs.msdn.microsoft.com/dotnet/2018/05/07/net-core-3-and-support-for-windows-desktop-applications/
Not yet, but I am definitely planning to look into this.
Also worth pointing out on that MSDN blog post:
“We have a version of Paint.NET running in our lab. In fact, we didn’t have access to Paint.NET source code. We got the existing Paint.NET binaries working on .NET Core. We didn’t have a special build of WPF available, so we just used the WPF binaries in the .NET Framework directory on our lab machine. As an aside, this exercise uncovered an otherwise unknown bug in threading in .NET Core, which was fixed for .NET Core 2.1. Nice work, Paint.NET!
We haven’t done any optimization yet, but we found that Paint.NET has faster startup on .NET Core. This was a nice surprise.”
I´m having problems using Warsaw software together with Paint.net. It’s a security software used on bank sites.
You addressed the solution to uninstall Warsaw, what would make my bank software not work. Will you look for a way to paint.net work together with Warsaw?
I’m sorry, but Diebold Warsaw hooks in deeply and is breaking the code in a place that logically should not be crashing (in other words, examining the code results in the conclusion “this is not possible”). Even if I find a way to work around it in that one place, it’ll almost certainly be broken somewhere else.
They need to fix it in their next update. There isn’t anything I can do about it. Please tell them about this so that it’s on their radar!
Someone did report to me that restarting their computer allowed Paint.NET to work. So, it may be that Paint.NET only crashes if you’ve been actively using Diebold Warsaw? I’m not familiar with it, and I don’t use it, and I’m not willing to install what is essentially a rootkit in order to debug it.
Yes, you´re correct, if I use Paint.Net before activate Warsaw (like, before using any bank software) it works. Hope somewhere between you two we´ll find a solution…