Paint.NET drops support for Windows 7, 8.1, and 32-bit operating system versions

Paint.NET will no longer support Windows 7, Windows 8.1, or any 32-bit version of Windows in the future. In the future, only 64-bit versions of Windows 11 and Windows 10 will be supported. This decision allows the program developer to spend time supporting the Creative Application on modern versions of Windows. As a reminder, Windows 11 is only available as a 64-bit operating system, so this change only affects older versions of Windows.

In the release notes for Paint.NET version 4.3.3, the developer explained why the app will only support 64-bit versions of Windows 11 and Windows 10 in the future.

It has become much more difficult and time consuming to support them lately, not many people use them, and I can no longer justify the cost and frustration of keeping the support afloat. Starting with Paint.NET v4.4, only Windows 10 and 11+ will be supported, and only 64-bit (x64 and ARM64). Once Paint.NET v4.3.3 is released, I will start working on v4.4 and only release v4.3.x updates when needed and until v4.4 is complete.

Version 4.3.3 migrates Paint.NET to .NET 6. This improves both rendering and application startup performance. Here is the complete list of new features, improvements and fixes in Paint.NET:

  • New: The app has been migrated to .NET 6, which has improved both rendering and startup performance
  • New translation: Catalan (ca)
  • New translation: Corsican (co)
  • New translation: Thai (th)
  • Changed: The installer / createMsi command has been removed. Instead, you can now download MSIs directly from the GitHub releases page.
  • Improved various UI controls for dark theme e.g. scrollbars (Win10 v1809 + only)
  • Fixed the appearance of various UI controls on Windows 11, for example buttons and dropdowns
  • Fixed View -> Zoom Window command when using keyboard shortcut (Ctrl + B), which was resetting itself instead of toggling zoom level
  • Improved performance during the “extract” stage of the installer by migrating away from Nullsoft Scriptable Installer System (NSIS)
  • Reduced download size on ARM64 by approximately 33%
  • Fixed rendering bug in Teeth and Polar Inversion effects, as shown here: -works- causing-unwanted-artifacts-was-it-intentional-change /
  • Fixed a memory leak in the selection renderer that consumed gigabytes of GPU memory, resulting in crashes. Thanks to @Zagna for finding this and testing the fix!
  • Fixed some GDI object leaks, especially with the Save Config dialog, which would eventually lead to a crash. Thanks @rechlin for finding and reporting this!
  • Fixed memory leak in Settings -> Tools. Thanks @otuncelli for finding this!
  • Fixed an issue that prevented new plugins from loading their native DLL dependencies as specified in their .deps.json file
  • Fixed app crash after an effect plug-in crashes when you choose to restart the app
  • Fixed a crash when drawing a selection, right-clicking on the History window before releasing the left mouse button, then clicking to redo a history entry, as shown here: https: // -plante-if-you-make-a-glitch-selection-and-then-history-jump-forward /
  • Fixed a text rendering bug in some parts of the UI, mostly in effects, as reported by @midora on -indirectui-control-in -filetype-shows-artifacts-after-scrolling /
  • Fixed the “untitled:” filename argument prefix, which prevented window breaks from being able to send a screenshot
  • Fixed some registry keys that were not deleted during uninstallation
  • Fix PdnRepair utility on Windows 7
  • Fixed some inconsistencies with MSI compared to v4.2.16 that caused issues for some deployments
  • Updated the bundled AvifFileType to v1.1.17.0, courtesy of @ null54, which updates the AOM version and fixes a crash when reading large EXIF ​​blocks. See its GitHub releases page for more information.

There are different ways to download Paint.NET. It’s available through the Microsoft Store for $ 7. This cost makes it possible to finance the development of the application. You can also get Paint.NET for free through the app’s website or GitHub.

We can earn a commission for purchases using our links. Learn more.

Source link

Comments are closed.