Please make Free Launch Bar compatible with Windows 10 - Printable Version +- Tordex Community (http://forum.tordex.com) +-- Forum: Free Launch Bar (http://forum.tordex.com/forum-5.html) +--- Forum: Free Launch Bar (http://forum.tordex.com/forum-21.html) +--- Thread: Please make Free Launch Bar compatible with Windows 10 (/thread-21916.html) |
Please make Free Launch Bar compatible with Windows 10 - enotar - 08-13-2017 I tried in Windows 10 SR3 and it just hang high high memory consumption and crash Windows explorer Taskbar and else badly after few second. I had to relaunch Windows Explorer with Task Manager. Not stable This is version 64 bits. Version 32 bits doesn't even work. Any TNA on new version compatible? This is really the only soft that does exactly what I want, just take a little space on taskbar. But it is good RE: Please make Free Launch Bar compatible with Windows 10 - Yuri Kobets - 08-22-2017 What is SR3??? RE: Please make Free Launch Bar compatible with Windows 10 - enotar - 08-27-2017 Windows 10 Fall Creators Update Redstone 3 ยท Version 1709 https://changewindows.org/milestone/redstone3 RE: Please make Free Launch Bar compatible with Windows 10 - VulcanTourist - 09-07-2018 (08-13-2017, 03:00 PM)enotar Wrote: I tried in Windows 10 SR3 and it just hang high high memory consumption and crash Windows explorer Taskbar and else badly after few second. I had to relaunch Windows Explorer with Task Manager. Not stableI can belatedly confirm this behavior. The effect for me is a continual "APPCRASH" and immediate restart of the explorer.exe Shell instance. This happens every few seconds to minutes, depending upon whether I am actively doing anything, like right-clicking on the Desktop, to trigger it sooner. Even when effectively idle the Shell restarts no more than every four minutes. Like you, I traced it eventually to FreeLaunchBar, which uninstalling cured the symptom immediately upon reboot. TrueLaunchBar does not cause the same Shell behavior, even when using the same toolbar configuration. There is something specifically different about TLB.DLL in TLB that prevents this Shell behavior, and that difference needs to be identified and incorporated into the limited TLB.DLL that is the entire substance of FLB. To not do so would be... indecent. |