4.0.20 and .NET 4.7

Just a quick heads up: the next update, version 4.0.20, will start using and requiring the .NET Framework 4.7 (previously, .NET 4.6 was required). If you’re using a supported version of Windows then the Paint.NET updater will automatically install .NET 4.7.1 if you don’t yet have .NET 4.7 or .NET 4.7.1 installed already.

This does mean that the list of supported operating systems is changing slightly because of .NET 4.7’s updated system requirements as compared to .NET 4.6.

Windows 10 support will now require the “Anniversary Update” (1607) or newer. “RTM” (1507) and “November Update” (1511) will no longer be supported.

Windows 8.1 is still supported.

Windows 8 is no longer supported because .NET 4.7 won’t install on it. If you have Windows 8 and haven’t yet updated to 8.1, then 1) please just install the update already, and 2) why on Earth haven’t you already updated Smile (it’s been more than 3 years!). You can also just keep using Paint.NET 4.0.19. But, seriously, just install the 8.1 update already. Even better, upgrade to Windows 10.

Windows 7 SP1 is still supported.

For more information on the .NET Framework’s system requirements with respect to supported Windows OS versions, check out Microsoft’s page on the subject.

I expect to publish 4.0.20 within the next few weeks. It will have, as usual, some important bug fixes. Oh, and Explorer thumbnail support for DDS and TGA files.


18 thoughts on “ 4.0.20 and .NET 4.7

  1. Mustafa says:

    I like the fact that you keep using newer libraries. Newer libraries generally means better security and better technology. I still don’t understand why people don’t upgrade. Most people do not have a reason not to upgrade.

    • peterfnet says:

      Me too. If relying on pre-built libraries that others make, rely on their reasoning for releasing updates and new-product releases.

    • Rafael Romero says:

      To be honest, I prefer a thousand times to have either Windows 7 last Service Pack or Windows 8.1 (still prefer Win7), to have a full of bugs SO like Windows 10. It’s been 2 years and Windows 10 is still failing, maybe it’s me, but Windows 10 is a No-No-No. I’m happy to be included in this update with my beautiful and stable Windows 7 🙂

  2. II ARROWS says:

    Hi Rick!
    Is pen support still on the roadmap?

    Today I scribbled something, and a friend is making observation that some characters are not clear… And it was difficult to use.

    • Rick Brewster says:

      Yes. I’m currently working on a Dark Theme for 4.0.20, and will probably have an update or two afterward for bugfixing it.

      After that, my next priority is a series of releases focused on the brush system. More brush shapes, then custom brushes, and then hopefully culminating in pen and pressure support. Which means I’ll be shopping for a Surface … probably the SB2 with the quad core i7-8650U.

      • iiarrows says:

        Thank you.
        My advice is to start thinking of pen support from the beginning, in order to include it in the base brush class, because inclination and pressure can change the shape and other properties.
        It’s easier to build a consistent experience if you build from the ground up with that in mind, instead of adding it afterward and revisiting every brush.

  3. eso says:

    My favorite thing about this post is that you encourage people to update from 8 to 8.1 (and possibly 10) without urging the same to windows 7 users.

    It’s nice to see implicit acknowledgement from a developer that reasons for sticking with windows 7 might be stronger than reasons to stick with 8.0.

    • Rick Brewster says:

      Well, Win7 users should already be on Win7 SP1, which is required for Paint.NET. Win8.1 is really “Win8 SP1” 🙂 Win8.0 is already out of support and deprecated by Microsoft, but 8.1 will still be supported for awhile.

  4. Patricia Abete says:

    I love PAINT.NET, thank you so much for everything, Rick! ❤ I used it for years (donation coming soon yes!!)

    By any chance, will you ever incorporate a way to edit text once made? It is like it becomes an image itself and I can't re adjust the font/size etc.


  5. Jesus Altamiranda says:

    thanks for so much work! I would like to see more options for the layers, that the opacity and overlay option show directly in the layers window, that I can add effects and filters to the layers without losing the original image and that the layers can be grouped!

    Thanks for such a wonderful job

  6. Kyuu Eturautti says:

    Unfortunately I’m having trouble with Windows 10 LTSB 2016 versions (build 1607). The required .net version is there, however neither Ninite or the program’s internal update work. It’s complaining that the right .net version isn’t installed, despite it being installed.

    I’ve verified this so far on 30+ different computers, all with the same Windows version. Our nonprofit has a bunch of loan laptops for culture events and such, and we were just doing updates on them.

  7. Erica says:

    In fact, netfx47 can be installed on any Windows NT 6.2 platforms.

    However only Windows Embedded 8 Standard and Windows Server 2012 are officially supported.

    PS. For NT 6.1&6.2, d3dcompiler_47 dependency update is included in Windows Monthly Rollup June 2017 and later Windows Monthly Rollup, the dependency updated also included in netfx471 offline standalone setup (expand the setup file you will see KB4019990), or provided as KB4019990 independent standalone package in Microsoft Update Catalog.

    • Erica says:

      But I think it seems that only a few people will run picture editing software on the Embedded and Server platforms 🙂

Comments are closed.