Rick Brewster

Please define what you mean by "larger image" and "smaller image" ... what is the actual size that you're talking about? In pixels, please. Otherwise this is just a wild goose chase. Also, a hang is absolutely not a crash. They are completely different things. This isn't a crash, as you say. It's a hang. Please don't conflate the two, it sends troubleshooting attempts down a blind alley. My guess is you're trying to work with enormous images but you don't have much RAM, therefore things spill out to the pagefile which is obviously going to be about 10,000 times slower than usual. So we also need the system info that @toe_head2001 pointed out.

I'm not sure this has anything to do with your copy of Windows being legitimate or not. However, I can verify that the Windows that I had in my virtual machine was "not" legitimate -- it wasn't activated, in any case. I don't activate Windows inside of the virtual machine because it's only a temporary installation for testing purposes and it would burn a license every time. If your copy of Windows isn't activated then it will say so in the System properties, towards the bottom: (this UI is from 10, but it's almost the same on 7 too)

(this is copied from the blog post I just made: https://blog.getpaint.net/2017/09/29/paint-net-is-now-available-on-the-windows-store/ ) Version 4.0.18, which I just announced, is now available on the Windows Store! The standard price is currently $8.99, but I’ve put it on sale for $5.99 $4.99 until the end of October. You can also make use of the 30-day free trial to get started. (It may take a little bit of time before you can search for Paint.NET on the Windows Store. I’m told that things take up to 24 hours to “propagate.”) Get it on the Windows Store: https://www.microsoft.com/store/apps/9NBHCS1LX4R0 Wait, it’s not free? Correct! The Store release of Paint.NET is not distributed free-of-charge. This allows many things to converge and solves a lot of problems, while still providing value for new and existing users (err, customers?). The “Classic” release will still be available and kept up-to-date on the same schedule as the Store release. … Well, I’m not gonna pay for it. That’s fine. Just use the “Classic” version like you always have. It’s worth checking out what the Store release has to offer though. Maybe you’ll change your mind, but if not … ¯\_(ツ)_/¯ And you can still send a donation if that’s your preferred way of providing financial support. This is actually more effective because Microsoft does take a 30% cut of every transaction that goes through their Store. There are some important advantages that the Store release comes with: Automatic background updating. The first advantage is a really big one, in my opinion. Paint.NET already has a best-in-class update experience (“Install when I exit”, thankyouverymuch), but having updates be fully automatic and transparent is much better. Now whenever you launch Paint.NET it will definitely be the latest version. No more procrastinating the update because you’re already busy with other stuff. No more bumping into a crash that was fixed yesterday or last week (or last year … *cough* ). The Classic release checks about once every 10 days for updates, so if you move to the Store release then you’ll probably have updates several days sooner than usual (on average). Easy Installation. The second advantage is that, once purchased, it’s really easy to get Paint.NET installed onto any new device. Everyone knows that installing “classic” desktop apps on Windows is a pain, especially when setting up a new PC. But for Store apps, it’s just so much easier: go to the “Store” app in Windows 10, click on the “…” at the top right, then click “My Library,” and then just click on the little download button next to Paint.NET (and on any other apps you need to install). Wait a little bit for the download and installation and you’re done. (There’s probably a better way to do this … it’s just the first method I found that I could verify quickly enough and be confident about.) (Store apps also come with the wonderful advantage that they can’t install browser toolbars. They can’t change your web browser’s home page. They can’t do all sorts of things that would pollute your system. Store apps don’t get to provide their own installers full of sneaky check boxes that may or may not install various crapware. Paint.NET has never and will never do anything like that, but for many other apps it has been a very slippery slope over the years.) Reliability. The Paint.NET installer and updater are based on Windows Installer (“MSI files”). Over the years this has proven to be an unreliable foundation. Every update I put out comes with a very small chance that a very small number of users will be unable to install the update, and that it will break their existing installation, and that they’ll be unable to reinstall – until they follow a set of crowdsourced troubleshooting steps that usually (but not always ) solves the problem. I’ve never been able to reproduce this, and I’ve never discovered the reason this happens. This problem goes away completely with the Windows Store release because of the way the package manager and application model works. So … why charge for it now? Over the years, I’ve been told over and over that I should be charging for Paint.NET and that people were willing to pay me for it. Accepting donations, the equivalent of a virtual “tip jar,” was a good way to accommodate this without having to develop or integrate a payment system along with serial numbers and piracy and all of that anti-fun. I’ve always been more interested in people having Paint.NET than ensuring that it has reached its full monetization potential (it’s been partly a lifestyle choice). However, statistically speaking, not very many people actually send a donation. The numbers are actually incredibly tiny, and it’s only because Paint.NET has such an enormous user base that I’m able to see much from this. This is totally fine though – the psychology and statistics of a system like this just lean heavily against it being very lucrative, and I had long ago made a lifestyle choice to not go down the other fork in the road towards business and marketing. Don’t get me wrong: getting donations is actually very rewarding! If someone likes Paint.NET so much that they’re willing to go to the PayPal website, punch in their details, and send me money, then that really says a lot about how much they appreciate it. I’ve had folks tell me that they promise to donate when they have money, and I’ve always told them to just tell all of their friends about it instead and to not feel indebted. I’ve wanted to put Paint.NET into the Windows Store for awhile, but I couldn’t determine a way to monetize it that fit in with the existing distribution philosophy. Microsoft won’t allow you to accept payments or solicit donations except through their billing system, which meant that the Help menu’s Donate link had to go. And, since updates are handled automatically in the background, the polite “Please donate!” link in the updater was effectively gone as well. So if I were to give away Paint.NET for free on the Windows Store, anyone who installed it from there would probably never even see the “tip jar” and be encouraged to contribute. So, I finally decided that I would just charge for the Store release. The Classic release will still be available and will continue to have a visible “tip jar” to encourage folks to provide financial support. And the Store release has some genuine advantages that you can pay for, if you choose. But what about plugins?! Oh! Don’t worry. Plugins are supported for the Store release. You just have to install them in a different location. Go to your Documents folder, create a folder called “paint.net App Files” (no quotes though), and then create a folder for each plugin type: Effects, FileTypes, and Shapes. And then put your plugins into each folder just like you’re used to with the Classic release. This does mean that plugins are installed per-user, mind you. This method of installation is also supported by the Classic release, by the way. If you’re a network administrator (or anyone really) who wants to disable this ability, you can do this with a registry key. In HKEY_LOCAL_MACHINE\Software\paint.net\, create a new string key called “Plugins/AllowLoadingPluginsFromUserLocations” (without the quotes) and set its value to “false”. Questions? Seriously, ask questions. This is a long blog post, but it’s new territory for myself and for Paint.NET and I probably missed something

I ran into this error one time while setting up a Windows 7 virtual machine. As best I could figure, it's related to a digital certificate authority or expiration or ... something. It really wasn't clear. The solution seemed to be to make sure that ALL Windows Updates were installed. Keep rebooting and installing until it stops saying there are updates.

You can't install the .NET Framework on Linux or Mac OS.

Also, once you've updated, and if you still see the error, please include screenshots of the errors.

Still, it's good etiquette to reply to a thread with your actual solution, not just "yay I solved it". Otherwise others who come across your thread, with the same problem, in need of the same solution, will be left hanging.

And what was your solution?

I think this is waaaaaaaaaaaaaaaaaaaaaaaaay beyond what we can help with. You'll need to contact Microsoft about this one.

You're doing it wrong ... and you're probably going to break a lot of things. Also, it sounds like you're trying to get a really old version of Paint.NET to work, since the latest version doesn't support any OS that can have an SP2 applied to it. We really can't help you -- you've hacked your OS to look like something it isn't so you can avoid installing something that will actually make things better (I will never understand this mentality), and we don't support older versions of Paint.NET anyway. At all.

Also, the paintdotnet: protocol launching now works for the Classic version, not just the Store version. I even verified that this works on Win7. It's not just a Win10 thing.

This update focuses on improving performance -- sometimes significantly! -- and fixing a handful of really important bugs. Special thanks go out to @Bruce Bowyer-Smyth for his contributions in this release. 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 should be offered the update automatically within the next week or so. You can get the updater soon by going to ⚙ Settings → Updates → Check Now. You can also download and install it directly from the website. Improved: Image -> Rotate should now complete almost instantly (thanks @Bruce Bowyer-Smyth!) Improved: Optimized a portion of the rendering engine for newer CPU instruction sets (SSE2, SSSE3, AVX2). Depending on zoom level, CPU type, and other factors, rendering throughput has been improved by 10-50%. Improved: Some performance optimizations for code that uses the indexers on the Surface class, which should improve effect plugin performance (thanks @Bruce Bowyer-Smyth!) Fixed: Shortcut keys for the Adjustments menu weren't working until after you opened the menu for the first time Fixed: Canvas checkerboard, used to indicate transparent regions of the image, now scales with DPI Fixed some of the more rare cases of the SEHException/AccessViolationException crash caused by Direct2D Fixed: A bug in IndirectUI was resulting in a crash when using @BoltBait's Level Horizon plugin Fixed: Per-user fonts no longer cause a crash for the Store version New: The paintdotnet: protocol now works for the Classic version Fixed: The paintdotnet: protocol should now work properly with paths that have spaces in them Fixed: Hardened security for loading Custom Shape plugins via XAML (thanks @Bruce Bowyer-Smyth!) Enjoy!

4.1.5 is now available and all of this should be fixed up

You want to pop it open like this? Press Alt+T. (I'm not sure if this is what you mean though)

Closing this thread -- new update incoming

This is a small update that fixes some important bugs and substantially improves plugin loading performance. Sorry for the random crashes -- it was actually a bug in Direct2D (a Windows component), and it took about a week to fully debug. 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 should be offered the update automatically within the next week or so. You can get the updater soon by going to ⚙ Settings → Updates → Check Now. You can also download and install it directly from the website. Changes in this update: Improved: Massive startup performance improvement when lots of effect plugins are installed Fixed a crash that would happen when closing an image, exiting the app, or sometimes just at random. This was happening due to a bug in Direct2D where ID2D1EffectContext does not honor the multithreaded initialization flag from its ID2D1Factory, and was thus corrupting its own internal data structures when released on the finalizer thread. Fixed: DirectX 9 GPUs can now utilize hardware acceleration again (in 4.1.3 they were forced to use software rendering) Fixed: The Black & White and Invert Colors adjustments no longer display an OK/Cancel dialog Enjoy!

Locking -- final release inbound

This build fixes the crash when using Image->Resize, as reported in the previous thread for build 6907. Direct download link: https://www.getpaint.net/files/zip/test/paint.net.4.105.6908.4572.install.zip

Here's an "effect" that Tom wrote. Basically what it does is let you write code that is compiled on the fly and that is then executed in the Paint.NET effect engine. This is the same plugin that we made available for Paint.NET v2.1, but it has been updated to work with Paint.NET v2.6 (and later). With this you can implement almost any type of effect you want if you have the programming and mathematical talent to do so. This plugin works by presenting you with a simple text editor that you can use to type in C# code that is then compiled and executed (rendered) as soon as you stop typing. Please note that this is experimental technology and is not meant to provide a robust development environment. It is perfect for rapid prototyping and very useful for educational purposes including teaching computer graphics. This plugin especially benefits from Paint.NET's extensive multiprocessor and multicore support. For instance, if you are interested in rendering high resolution fractals on an expensive workstation, this is the way to do it! The code you write is automatically multithreaded and the workload is spread across multiple CPU's resulting in near linear performance scaling (4 CPU's = almost 4x faster). Download: http://BoltBait.com/pdn/codelab/ Note: BoltBait is the current maintainer of CodeLab. Help file: http://BoltBait.com/pdn/codelab/help/ Help for non-programmers: If someone gave you a CodeLab script and just want to know what to do with it, read this: https://forums.getpaint.net/topic/111233-codelab-for-average-users-a-laymans-guide/ Tutorials: Overview Tutorial 1 of 4 Tutorial 2 of 4 Tutorial 3 of 4 Tutorial 4 of 4 Tutorial 5 of 4 Tutorial 6 Tutorial 7 Sample Code Russian If you speak Russian, download here: http://forums.getpaint.net/index.php?/topic/29995-a User ReMake maintains the Russian version. Post enhancement requests/bug reports of the Russian version on that thread. WinXP, WINE Users If you are stuck using Paint.NET v3.5.11 (for whatever reason), you can download CodeLab v1.8f here: http://boltbait.com/pdn/CodeLab/History.asp#v1.8f With CodeLab, you can... Work with complicated displacement filters: Parametric images: High resolution fractals:

Please upvote this in the Windows 10 Feedback Hub so that it gains some traction: https://aka.ms/AA3e1ed

Definitely a bug in Win10 v1809. It doesn't happen in v1803. If we're lucky they'll fix it someday.

Yup, this is a new WinForms or Win10 v1809 OS bug. I can get it to happen in LINQPad as well.

Okay this should be fixed up for v4.1.5 You should be able to use paintdotnet:"C:\something\with\spaces\in the filename.png" and it'll work great. Also, paintdotnet:"C:\file\first image.jpg" "C:\file\second image.jpg" should also work. To make this even better, and certainly easier to test, I think it's about time to add paintdotnet: protocol support for the Classic version as well.

I just confirmed: this does not happen in Win10 v1803, but it does happen in Win10 v1809. This might actually be a bug in the .NET Framework, from what I'm setting in the debugger. Jeez. They really screwed up A LOT of stuff in v1809. I've been facepalming on so many things for the last week that I keep bumping into that they broke. When are they going to rehire the testing department over there?!?!!?LKJSFJ?LK 😤🤯

You can install the beta for 4.1.5 which fixes this: https://forums.getpaint.net/forum/45-preview-center/ FWIW, the shortcut keys for the Adjustments menu do work, but only if you first open the Adjustments menu. So if you don't want to install the beta, just press Alt+A after opening the app for the first time. 4.1.5 (non-beta) should be out the door for everyone within the next half week or so.