toe_head2001

This is just a setting in the Windows Registry. I assume Avast enable the setting, and it was never turned back off during the Avast uninstall. You can simply delete that setting from the Registry. https://answers.microsoft.com/en-us/windows/forum/all/your-virus-threat-protection-is-managed-by-your/279c6d56-927b-43bf-912b-99e1bdd608d4

Did you actually disable AVAST? It is known to cause this exact issue. https://forums.getpaint.net/topic/117318-cannot-save-png/

Is ByteFence or AVAST interfering with file saving? Can you disable these, and see if it makes a difference?

https://knowyourmeme.com/editorials/guides/where-are-all-the-images-with-hidden-words-coming-from-the-ai-enabled-trend-explained

Have you done a traceroute to see if the connection is making it all the way the server?

Umm, that's debatable. It is less blinding-white, if that's what you mean. A Dark Mode icon would be cool though. That doesn't sound related to a custom icon. Please post the diagnostic information found within paint.net. Settings -> Diagnostics -> Copy to clipboard.

https://getpaint.net/ <-- working https://www.getpaint.net/ <-- not working

We do have one, which is how I learned to do it back in the day. The images are ancient, but still mostly accurate. https://forums.getpaint.net/topic/4209-how-to-debug-your-plugin/

I don't really understand your question. I gave the steps for what AnneYusual is trying to achieve. The steps have nothing to do with working in CodeLab.

That filename sounds like it would be the VSIX source code for my templates. Which will be of no use to you. Once your plugin is compiled, ensure the DLL file has been copied into the Effects directory of Paint.NET. Then you can start Paint.NET with the Visual Studio debugger. Proceed to open your plugin from the Effects menu within Paint.NET. When your plugin is run, your breakpoints in Visual Studio will break. (assuming the code path is executed)

This is not a PNG file. The file opens in Paint.NET if the extension is corrected.

Project templates? I hope you're not referring to the ones I created many years ago. They are extremely outdated, and aren't even available anymore.

If your plugin isn't listed in the Effects menu, then you need to ensure was copied into the Effects directory. You can also look at "Plugin Errors" in the Paint.NET Settings.

Yes, that's the expected behavior. The compiler in CodeLab never uses Debug mode when building the DLL or running a UI preview.

I generated a spreadsheet to see all the Effects (and their descriptions) at the same time. https://docs.google.com/spreadsheets/d/1PPYQgkWzEeJdLos9dGe5ebH_rqMPleySX9rpRnJTNuM/edit?usp=sharing Enjoy.

In Paint.NET you can try pressing Ctrl+Shift+F8, which can restore the Colors window to the proper size and location.

Hi, If you want to play with it, here's some example code for you. string fullPath = @"C:\users\user.name\Documents\test.png"; string directory = Path.GetDirectoryName(fullPath); string fileName = Path.GetFileNameWithoutExtension(fullPath); string extension = Path.GetExtension(fullPath); int count = 1; string newFileName = fileName + count + extension; string newFullPath = Path.Combine(directory, newFileName); I can post a bugfix release of @TechnoRobbo's plugin sometime this weekend.

Please post the actual crashlog from the crash.

Please post the diagnostic information found within paint.net. Settings -> Diagnostics -> Copy to clipboard.

Please post a screenshot of your FileTypes folder.

You could also try using the Windows 10 Update Assistant. I've seen that tool work successfully when Windows Update when failed.

This is a pretty old version of Paint.NET. You should go into the Microsoft Store, and check for updates. If it doesn't update, perhaps you'll need to log into the Microsoft Store. This is now an unsupported version of Windows 10. (unsupported by Microsoft) You really need to run Windows Update.

Please post the diagnostic information found within paint.net. Settings -> Diagnostics -> Copy to clipboard.

I have posted a bugfix release (v1.2.6.4) to fix the issue with the dialog opening on some other monitor.

It only appears for Guests (people not logged in) and Newbies (members with 10 or less posts). Everyone else should know better, so no need to bother them with an obnoxious banner.