- General
-
Ideas
Automatic support for new windows insider builds
Hello, there is a way to make this work automatically on new windows insider build?
I'm a insider and every time windows update your app stop work (Could not load library)
There is a way to recompile dll or add an option to force run at my risk, something like this?
I use others explorer extensions and that other not break when windows insider update.
I use the latest beta, i'm donator.
Thanks in advance.
Answer
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!
Customer support service by UserEcho
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.
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.
The tweaker has deeper integration with Explorer, and relies on internals that other tools usually don't rely on.
Thank you for the support!