Rick Brewster

Seems worth considering, I've filed an issue to track this on GitHub

There's no preview window, nor plans to add one, but you can use Ctrl+B (shortcut key for View -> Zoom to Window) to toggle between the current zoom level and one that fits the image within the window.

Okay I figured out what was wrong and I fixed it. It'll be working again in the 5.0.3 update.

Some screenshots would help to point out any of the differences you’re experiencing. Posting a sample image would help a lot too, that way I can load it up in the current version and the older version and do some comparisons.
 
Are you using the Move Selected Pixels tool?
 
There can be differences because of the default sampling mode being upgraded from Bilinear to Bicubic. You can try switching to Bilinear and see if that helps get the look you want.

The incompatibility error usually comes from using a program or launcher that has not been updated or fixed to work with newer versions of Windows.
 
If you're launching the installer from Windows' built-in File Explorer, it'll work fine, but we've had reports of this type of error from people using various other launchers, shells, or start menu replacements.

You can already press Alt+R to trigger the Randomize button (notice how the R is underlined when you press/hold Alt?). The other stuff you can use Tab to switch between controls and then do the appropriate thing.

Unfortunately this isn't possible, as the printing UI is a Windows component. There's no way for me to make any changes to its UI -- I'd have to write a brand new printing UI and printing system from scratch. Someday...

Sorry, no. This information is not included in the file, and it's also not really appropriate to include user interface state like that in the file.

I was able to get 4x super sampling with no real reduction in performance, and it even improved temporary memory usage because it's not going through Direct2D's effects system, and because it's rendering directly to Alpha8 instead of going through a PBGRA32 intermediary.
 
I already had a very high-performance 4x Alpha8 downsampler which is used for the selection mask, so I just reused that.

Try the alpha I posted here, it's newer and has both fixes: 
 

The selection quality affects the selection. All drawing, including for the Pencil tool, is clipped to the selection, and will be subject to antialiasing at the edges of the selection unless you switch to pixelated (aliased) selection quality. In other words, this isn't really a setting for the tool so much as for the general drawing system.
 

Alright 5.0.1 is now out with full code signing. Let me know if you find something in there that isn't signed. 
 

Okay I did some more digging and I believe I've fixed it. What a weird bug. In my code I'm querying for the bounding boxes for the title bar and min/max/help/close buttons (via WM_GETTITLEBARINFOEX) and it was reporting that the Close button had a negative width equal to the whole width of the monitor. And then I was marshaling the data wrong, which resulted in a Close button with a positive width equal to the whole width of the monitor. Which means it was "covering" the draggable title bar area (so it thought that whole area was the close button), and causing that weird old school X button to show up.
 
It works fine now on my multi-mon Win10 tester box. The bug didn't ever happen on Win11.
 
Try this build:
 
Installer: https://www.getpaint.net/files/zip/test/paint.net.5.1.8418.38965.install.x64.zip
 
Portable ZIP: https://www.getpaint.net/files/zip/test/paint.net.5.1.8418.38965.portable.x64.zip

It sounds like you have disabled the Windows Image Acquisition(WIA) service.
 
Make sure it's enabled / running from the Services control panel (right click on Start button -> Run -> "services.msc")
 

I was getting a few different reports about this, and I think I found the culprit. It was a change in .NET 7.
 
PDN v5.0.1 should fix this. Let me know if it still behaves weirdly after the next update, in other words.

The first thing I'd do is make sure you have the latest version of your AMD GPU driver
 
The second thing I'd do is disable/remove Avast. It has been known to cause lots of problems. The built-in Windows Defender is all you need for antivirus.
 
The third thing I'd do is make sure you're caught up on all Windows Updates. Sometimes they break things, but then they fix them.

The workaround is to remove the metadata, which you can do with Select All (Ctrl+A) + Paste into New Image (Ctrl+Alt+V). This will remove all metadata.
 
5.0.1 will have a fix for this though so you won't need to do that.

Something like this usually happens because you have some other software on your system that's trying to perform "window management" duties. Stardock has a lot of buggy software like this, for instance.

How are you turning off pen pressure?
 
If you don't want pressure sensitivity,
 
Settings -> Pen & Tablet -> uncheck "Windows Ink"
 
I plan on adding a setting to control both the pressure sensitivity and the high-frequency input sampling, it's nice to be able to control them separately.

IIRC, we've looked at implementing this and it effectively stalled at the design stage. Basically, how should "Export As ..." remember (or not) the settings and file name/path used for saving. It's not difficult to implement, it just requires a fleshed out design for this. It could definitely go in as a 5.0.x feature within the next few months if this gets resolved and ironed out.

Alt activates the menus -- this is standard Windows behavior. Its expecting you to then press something like F to open File, E for Edit, etc.
 
If you press Alt again, then it'll resume the normal shape dragging stuff.
 
So, not a bug.

PNGs don't have the ability to encode this type of information. This isn't a Paint.NET limitation, it just isn't part of the PNG format.

Ctrl+Home is already use to scroll to the top-left of the image.

Yup I'm seeing this too.
 
There was a weird old bug I fixed here and it's still causing problems. I'll make sure it's fixed for the next build, but definitely keep an eye on this even then.

The MSIs are there