joeblowma Posted April 3, 2023 Share Posted April 3, 2023 (edited) It started for me after updating to windows 10 latest release from 1909 and initially I thought it was a problem that would work itself out somewhere along the way. Finally got sick of having to use the "open with other app" dialog today and did a dig into it, and came up with an interesting fix. After delving into keys for .jpg, .bmp and others and finding paintdotnet.exe already there I grew confused, until I stumbled into this answer on superuser: https://superuser.com/questions/1199648/strange-open-with-list-inconsistent-with-registry/1256482#1256482 The .ApplicationCompany key is missing for paintdotnet.exe in the mui cache, and creating it there got paint.net showing up in the open with context but it will eventually fade whenever windows decides to refresh this cache. From there I got out a resource hacker and looked into it, and there is no CompanyName specified in the version info resource which is what derives the mui cache keys. I don't know if this was removed recently, but for whatever reason windows 10 doesn't like it being absent and hopefully there aren't about to be a bunch of people with a cache refresh that breaks open with for them. Edited April 3, 2023 by joeblowma Quote Link to comment Share on other sites More sharing options...
Solution Rick Brewster Posted April 3, 2023 Solution Share Posted April 3, 2023 Well, I'll try adding this to the native EXE's resources and we'll see if that helps (once 5.0.4 is released). The company name is specified for all of the managed DLLs, but looks like it got missed for the EXE (which is native/C++ code). Quote The Paint.NET Blog: https://blog.getpaint.net/ Donations are always appreciated! https://www.getpaint.net/donate.html Link to comment Share on other sites More sharing options...
kreemoweet Posted April 3, 2023 Share Posted April 3, 2023 I bypassed all the endless drama with Windows 10 "Open With ..." menu simply by creating a shortcut to the Paint.net executable, and placing it in the Send To folder. I can send anything to Paint.net now, no muss, no fuss, no Registry fiddling. I can even send multiple image files - try THAT with the Open With ... menu! Quote Link to comment Share on other sites More sharing options...
joeblowma Posted April 4, 2023 Author Share Posted April 4, 2023 10 hours ago, Rick Brewster said: Well, I'll try adding this to the native EXE's resources and we'll see if that helps (once 5.0.4 is released). The company name is specified for all of the managed DLLs, but looks like it got missed for the EXE (which is native/C++ code). All I can say for certain is it used to work fine, maybe it was the 5.x upgrade that lost it? 6 hours ago, kreemoweet said: I bypassed all the endless drama with Windows 10 "Open With ..." menu simply by creating a shortcut to the Paint.net executable, and placing it in the Send To folder. I can send anything to Paint.net now, no muss, no fuss, no Registry fiddling. I can even send multiple image files - try THAT with the Open With ... menu! Definitely a great idea as a workaround, for the reason you state I might just wind up doing the same - multiple files at once. Thanks for sharing! Quote Link to comment Share on other sites More sharing options...
Rick Brewster Posted April 4, 2023 Share Posted April 4, 2023 12 hours ago, joeblowma said: All I can say for certain is it used to work fine, maybe it was the 5.x upgrade that lost it? 5.0 started using a custom .NET "apphost" EXE (that is, paintdotnet.exe) instead of the stock apphost EXE that comes with .NET. So that could definitely be it. Quote The Paint.NET Blog: https://blog.getpaint.net/ Donations are always appreciated! https://www.getpaint.net/donate.html Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.