Using v13.2 in Windows 10 Pro
I get this message when selecting Edit with 3D Paint from right click menu.
Error 0xeedfade in Thread 0x1d84 at 0x00007FFA82A6CF19
Does the same thing with the same file work in File Explorer?
Which process is crashing, 3D Paint or Opus?
Opens fine in Windows Explorer
Also opens if I select 'open with > 3D Paint'
It's a Directory Opus error message
Is Opus actually crashing, or is it still there after showing the message?
Is Paint 3D opening at all? If so, is it closing/crashing after the message, or still there?
Can we see a screenshot of the message, please?
FWIW, we've tested on our own machines, both Windows 10 and 11, and not seen any errors so far.
This morning it worked OK but let's see what happens in the coming days
Thanks for your help
It's been happening again over the last dew days
I attach the original error and the 'new' one
Abort closes DOpus down (in v11 it would then reopen but not in this version)
Retry / Ignore does nothing but any further attempt to open file also does nothing
After several attempts it finally works for that session
If you paste /temp/DOpus.Minidumps into the path field in Opus and push return, are there any files there that correspond to the date and time of the crashes?
The 0xeedfade code only seems to come from Delphi and .Net components, which Opus itself doesn't use, so the bug is likely inside 3D Paint's context menu handler, but the minidumps may reveal more information.
Please send them to us. Automatic crash logs (for bug reports)
The crashes are caused by this shell extension:
C:\Program Files (x86)\TLH3\ShellExt\TLHShellExt64.dll
It's not one I recognize, and Google doesn't know what it is either, but it's what has caused all those crashes.
The date on it is 2022 so it may have an update which fixes the crashes. If not, either uninstall it (if you don't need the program it's part of) or block it using ShellExView x64 (or Preferences / Miscellaneous / Shell Extensions, in Opus 13).
This just now, right click open with Flash Renamer:
Same cause: TLHShellExt64.dll
Just renamed the .dll to .old and following a reboot everything seems to be hunky dory
I'll see how I go on in the next few days
Out of interest, what is that TLH app?
Traders little Helper - this being v3 beta.
I've renamed the dll and it seems to function
I also have v2.84 installed that has no dll files at all.
1 Like
This looks much more like a third-party shell integration conflict than a native Paint 3D bug.
The key clue here is that the error only appears when using “Edit with Paint 3D” from the right-click menu, not when launching Paint 3D directly. That strongly suggests something is intercepting or modifying the context-menu call before Paint 3D even fully starts.
In your case, Trader’s Little Helper v3 beta fits that pattern perfectly. Shell extensions and DLL-based helpers often hook into right-click actions, and beta versions are especially prone to throwing unhandled exceptions when another UWP app is launched through Explorer. The fact that renaming the DLL resolves the issue basically confirms it’s the trigger.
The reason v2.84 works fine is also telling — it doesn’t use DLL-based shell hooks, so there’s nothing interfering with the Paint 3D launch process.
A few important takeaways for anyone else hitting this error:
Error 0xeedfade commonly appears when a process crashes before proper exception handling kicks in
Paint 3D itself is usually not the root cause
Context-menu integrations are a frequent culprit, especially beta or preview builds
If Paint 3D opens normally from the Start menu, the app installation is healthy
Best practice here would be:
Disable or remove the beta version of the third-party helper
Stick with the stable release until compatibility is confirmed
Avoid Explorer-level hooks unless they’re strictly necessary
We’ve seen similar Paint 3D right-click issues reported by users, and in almost every case the fix involved removing or disabling a conflicting shell extension rather than repairing Paint 3D itself. Some common troubleshooting patterns around this are documented on www.thepaint3d.com, especially for launch and context-menu related problems.
Bottom line:
Paint 3D isn’t crashing on its own — it’s being tripped up by a third-party DLL hooked into Explorer. Your workaround is valid, and the cleanest fix is avoiding the beta shell integration altogether.
If you want, I can also rewrite this as a short confirmation reply or a more technical root-cause explanation for admins.
1 Like
Please don't post AI-generated slop on the forum.
This was solved a long time ago.
Please mark as solved/closed.