Teie kommentaarid
Please see my reply here:
https://tweaker.userecho.com/topics/1061-unable-to-load-dynamic-link-library107
Closing as a duplicate.
Please see my reply here:
https://tweaker.userecho.com/topics/1061-unable-to-load-dynamic-link-library107
Closing as a duplicate.
Please try the newly released v5.9.1.6 beta.
Please try v5.9.1.6 beta, I believe that it should fix the issue.
I believe that it wasn't related to hovering. In any case, I'm glad that you solved it.
Hi Jean,
Unfortunately, that's not possible, at least not without adding a complex code instrumentation system to analyze Explorer's code. The tweaker relies on internal offsets inside Explorer, which have to be updated once they change. Those offsets didn't change at all back in the Windows 7 days when the tweaker was created, but today things move quickly, and almost each new Windows 10 version, released twice a year, breaks the tweaker. The matter with insider builds is even worse. Not every new insider build breaks the tweaker, but it happens rather often.
add an option to force run at my risk
That's what already happens. Every time you see a "could not load library" error, that means that the tweaker actually tried to run, but failed. Sometimes it causes explorer to crash, and sometimes the tweaker can detect that something's wrong (e.g. an invalid pointer) and abort gracefully.
I use others explorer extensions and that other not break when windows insider update
The tweaker has deeper integration with Explorer, and relies on internals that other tools usually don't rely on.
I use the latest beta, i'm donator
Thank you for the support!
Good to know you found a fix.
Thanks for sharing the solution, perhaps it will be helpful for other users.
It works on my computer. Can you post a screenshot of your configuration?
Option 3 is similar to the option Middle click -> Close in the UI. Does that option work for you?
Thank you for the support and the generous donation Owen! I highly appreciate it.
I'm glad that you like the tweaker, and it's good to hear that you got it working.
Customer support service by UserEcho
False positives are common for beta versions, unfortunately. You'll have to add it to the exclusions, or contact Microsoft and wait for them to remove the detection.