- General
-
Bugs
0
Not a bug
Could not load library (4)
How does it means? Explorer crashes and the message "Could not load library (4)" is displayed.
Older versions do the same thing too.
Must be some kind of incompatibilty, I think, cause the 7TT works well until end of september. Can be NVidia drivers update? I'm lost!!
Using Win7x64.
Older versions do the same thing too.
Must be some kind of incompatibilty, I think, cause the 7TT works well until end of september. Can be NVidia drivers update? I'm lost!!
Using Win7x64.
Customer support service by UserEcho
No, no properties are set. Even setting to "Windows 7" alone didn't get the trick too.
Specifically (in case you have some WinAPI knowledge), it fails to call the GetProcAddress function, probably because the address is different in the tweaker's process and in the explorer's process.
I don't know why that happens. I know it can happen when enabling compatibility settings, but you've said that yours are disabled.
You say that the issue started after updating NVidia drivers. Could you try disabling, or temporarily removing them, and check whether they cause the issue?
The issue is caused by a program called I n k S a v e r who runs at startup installing itself under HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Run. Didn't go deeper but happy cause I found the culprit.
Putting 7TT startup entry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Run to make it run before that program does the trick.
I know this is not the correct approach to solve this, but, i'm the lone user on this machine. And works like a charm.
The problem is indeed caused by the InkSaver program. It injects code into the 7+ Taskbar Tweaker process (among others), and hooks the GetProcAddress function, which breaks the injection. I think you should report it as a bug to InkSaver, especially if you're a paying client of theirs.
http://rammichael.com/7-taskbar-tweaker/comment-pa...