I assume that explorer crashes when the tweaker launches, right? Can you create and upload a crash dump using ProcDump? Run procdump64.exe -mp -e explorer.exe and trigger the crash. The dump will be written to a file, the details will be printed in the ProcDump console window.

There should be an error code after "could not load library", which code are you getting?

Please make sure that you're using the latest version of the tweaker, v5.12.3. If not, I'll try to understand what's going on by gathering more information.

Fixed in v5.12.3.

Thank you for the suggestion. Closing as a duplicate in favor of:

https://tweaker.userecho.com/topics/1175-option-to-remove-the-show-hidden-icons-arrow-from-the-system-tray

Please try the newly released beta version, v5.12.2.1.

That's tricky - depending on the program, running an instance of the program which was managing the closed window might not be enough. For example, most browsers have a "reopen closed window" option, but without being familiar with the specific browser, the tweaker won't know how to restore that closed window. Another example is Notepad - how would the tweaker know which document was open in the Notepad window which was just closed?

It worked by accident, and it became broken by accident. Keeping two customization tools that have no coordination compatible is quite tricky. I might look into fixing it later, but it's not a priority.

Regarding older versions, you can find them here:

https://www.dropbox.com/sh/mcbychsh0xc1dvu/AAC7NwQTQ-tOTNL2BUZ_CwUua?dl=0

That's a great question, the "taskbar wasn't found" message should never show up, unless maybe you have some other taskbar customization tool that might interfere with the tweaker. If you find a way to reproduce the error message, let me know. Meanwhile, I'm closing this topic since there's not much I can do with it without a way to reproduce the problem.

Thanks for confirming. The issue should be fixed in v5.12.1.1 beta.

I will look into it, but from a brief peek, my guess would be that turning off the fix_hang_reposition advanced option might work as a temporary workaround. Can you please verify that?