Please make Free Launch Bar compatible with Windows 10
Started by enotar


Rate this topic
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5


3 posts in this topic
enotar
Junior Member
**


0
2 posts 1 threads Joined: Aug 2017
08-13-2017, 03:00 PM -
#1
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
Yuri Kobets
Posting Freak
*****


8
6,181 posts 427 threads Joined: Jan 2002
08-22-2017, 12:44 PM -
#2
What is SR3???
The TORDEX Team
http://www.tordex.com
enotar
Junior Member
**


0
2 posts 1 threads Joined: Aug 2017
08-27-2017, 06:13 AM -
#3
Windows 10 Fall Creators Update

Redstone 3 · Version 1709

https://changewindows.org/milestone/redstone3
This post was last modified: 08-27-2017, 06:14 AM by enotar.
VulcanTourist
Junior Member
**


0
2 posts 0 threads Joined: Sep 2018
09-07-2018, 03:23 PM -
#4
(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 stable
I 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.
This post was last modified: 09-11-2018, 01:07 PM by VulcanTourist.


Forum Jump:


Users browsing this thread: 1 Guest(s)