Rick Brewster

This is a rendering artifact that happens sometimes at non-integral zoom levels. (non-integral meaning not a multiple of 100%, e.g. 100%, 200%, 300%, etc.)
 
Nothing's wrong with your system or configuration. I looked into this awhile ago and I'm not sure it's possible to fix, but mostly it's just not a high priority right now.
 
So the workaround is to set your zoom level to the nearest integral zoom level. Usually pressing Ctrl + (zoom in) or Ctrl - (zoom out) will accomplish this.

There might be -- others may know of a plugin that can help here.
 
What you need is a version of Effects -> Color -> Quantize that lets you specify the palette. Quantization is performed in two steps: 1) palette generation, 2) quantization + dithering. All the plugin would need to do is skip the first part and use a palette you specify instead of one generated from analyzing the image.
 
The quantization and dithering code in Paint.NET is fast and high quality, it's (generally) better if a plugin doesn't roll their own solution. I can enable this scenario if a plugin dev is interested in this, by making Paint.NET's internal quantizer available for use by plugins (I may even already have this planned for the next big release (not 4.3.x), I think @midora was asking for it).

It says it's running out of memory.
 
I'd look into this program, which is hooking into the process. You probably don't need it. "Hook" programs can often cause all sorts of problems like this.
 
C:\Program Files\Huawei\PCManager\plugins\PerfWndMonModule.dll

For now everyone can install using the offline installer available here: https://github.com/paintdotnet/release/releases
 
You almost certainly want the "x64" installer unless you're on a 32-bit "x86" system. (It will let you know if you downloaded the wrong one, you can't actually cause any harm.)

Paint.NET uses 32-bits per pixel (8-bits per component) BGRA in straight alpha (not premultiplied alpha).

Are you sure you're using the latest version of Paint.NET?
 
Also, if you're trying to save as  PNG or JPEG, I don't think they can handle images that are 90,624 pixels tall. Limitation of the image format, not Paint.NET.
 

This is how it's supposed to work. The history counts as "unsaved changes" that you might not want to be throwing away. Paint.NET is making sure you're the one to make that decision intentionally, not accidentally.

A-Volute / Alienware Sound Center, which is listed in the crash log
 
ExplorerPatcher was the one at fault in the link
 
Anything that is a screen recorder, window manager / theme manager, anything that changes the Windows UI (like the Start button/menu), any kind of GPU overclocking or framerate display (EVGA Precision is the worst offender here), Discord overlay (haven't had any reports of that in awhile)

This is a result of JPEG's lossy compression. Saving an image as JPEG, then loading/opening it again, and resaving it, will cause this sort of artifacting.
 
Using PNG, PDN, TIFF, TGA or BMP will avoid this because they use lossless compression.
 
If you must work with JPEG, make sure the Quality slider is set as high as possible when you're in the Save Configuration dialog.

That looks like a corrupt app install. I would first run the repair process for the app, which you can do by going to Run (via WinKey+R, or right click on Start Menu -> Run) and then type in paintdotnet:/repair and press OK or Enter. You'll need to restart afterwards.
 

 
If that doesn't work, try downloading the app from the website and reinstalling (just double-click the install EXE and do the normal install process, it'll auto-uninstall even if it's the same version).
 
I would also run chkdsk to make sure nothing else on your system is corrupt, as well as sfc /scannow, both of which are easy to find information about online.

I figured this out -- the pixel offsets were off by 0.5 pixels
 
I can have a fix in the 4.3.9 update

Confirmed. This happens when the height is larger than the width.
 
I'll push out a 4.3.10 shortly to fix this. In the meantime you can workaround this by first using Image -> Rotate 90 Degrees, then do the resize, then Rotate 90 Degrees Counter-clockwise. It's silly but it works ...
 
Also, to be clear, this isn't a crash -- the exception is being caught and an error is shown to the user. No data loss.

It looks like the TGAs are being saved with transparency -- so this is an issue with your exporting software. Paint.NET is doing the right thing.

I'm planning to fix this up for the 4.4 release. cc @toe_head2001

I've already had an issue filed for this, targetting v4.4.x, but hadn't updated it with regards to Win11. Hopefully there's enough time/motivation to squeeze this in. Most of the work entails localization (translations) and getting that text into the right place in the right format.

This is pretty much what I'd do. I originally planned to have this in the 4.0 release but just ran out of time/energy (it was already a 5 year project). The complexity, iirc, came when you switched between the line vs. curve formats. Where do the nubs go when switching to a curve, modifying the handles, then back to line, modifying it, then back to curve? I just didn't have the runway to deal with that at the time.
 
I do have an issue to track this for the 4.4.x series of releases.

(I had to remove the build because of one final thing, but I just posted an updated build. It's ready!)

This has been fixed for the 4.3.3 release

So I looked at the trace you sent me, @stefanob and it's definitely using a lot of CPU time in the CreateFontPreview method (i.o.w. it's not some other red herring)
 

The highlights for the table and graph are synchronized (that's how WPA works). My CreateFontPreview method is using DirectWrite to render text, and it's spending almost all (99.83%) of its time in a function called VariationInterpolator::AccumulateInterpolatedTupleDeltas. So, something about font "variations" is causing this.
 
I searched for that function name and I found this, https://github.com/microsoft/cascadia-code/issues/319 . Someone was having performance problems with Visual Studio, on Windows Server v1607 (same as Win10 v1607), after installing the Cascadia font. I recommend reading through that issue, they may have some insight for you. However, ultimately, you need to install your Windows Updates, as this has probably been fixed. You may also have installed some fonts with "variations" (not sure what that is), and you might be able to uninstall/disable them to get performance working again. Or maybe just install a newer version of them (maybe it's the Cascadia font; that link is in the GitHub repo for it, they probably have a newer release).

If PdnRepair is also missing then you'll need to re-run the installer.
 
Just get the latest offline installer from here, https://github.com/paintdotnet/release/releases
 
You may need to use Microsoft's install/uninstall cleanup program if you're still getting errors during the install process: https://support.microsoft.com/en-us/topic/fix-problems-that-block-programs-from-being-installed-or-removed-cca7d1b6-65a9-3d98-426b-e9f927e1eb4d

You can't just install VS2022 ... ? It's free 

Looks like you're having some network issues
 
Are you able to download the installer directly from https://github.com/paintdotnet/release/releases ?

Paint.NET will use whatever you've configured your Documents folder for.
 
Right click on your Documents folder from This PC, select Properties. Then click on the Location tab. It will be pointing to your F drive. Just move it back to where it should be on D.
 
When you want to move the contents of Documents, just move the files. Don't change the location of the folder itself.

Yeah I'm seeing this behavior difference as well. I'll look into it. Thanks for reporting it.

4.3.2 is out with the fix: