bug report: WB5 [DOES NOT] kill some third party services [updated]

[update] The bug listed below no longer seems to be a problem with Synergy and the Spider issue turned out to be unrelated (or is no longer an issue with the latest WB5 release). I leave the posts below up as is in order to document my stupidity for all posterity. :) WB5 is causing a very odd phenomenon with both third party services programs I have tested. I first noticed this with the Station X Studios Spider render control software. It runs as a service in the background with a tray icon for access. If WB5 is loaded, not only won't the tray icon appear, but a check of the service itself shows that it cannot load automatically or manually. There is no problem running this service under WB4 (or earlier).

To test this further I grabbed another third party service program, Synergy, and tested with that. It will work if run in "log-on/startup" or manual mode, but if you try to enable it as a service, it fails entirely. It can be run neither automatically or manually.

Unloading WB5 allows both services to work properly.

I have tried to exclude both runtimes/exe's from WB5, but there seems to be no way to genuinely filter out services from WB5. And again, none of this is a problem in any way under WB4 or earlier. I have tested this under both Athlon and Intel machines under multiple graphics cards/generations of Nvidia products.

Any help would be appreciated. Thank you.
5,686 views 4 replies
Reply #1 Top
For Synergy issue, please have a loot at this thread: https://www.wincustomize.com/Forums.aspx?ForumID=166&AID=88502#713975

Not sure about the Spider render problem.

Try includding it in exlcuded list (From WB Config window, goto per application settings, click add per application setting and browse to the exe, click OK and from option menu select completely ignor this application) ...

BX
Reply #2 Top
I had tested the synergy issue throughout the early WB5 betas, but you are correct, it does not appear to work fine with the latest updates. Thank you.

And because this was a problem, I assumed that the Spider service was related (it may still be), but now I will try reinstalling Spider to see if that helps in any way. Note that I had mentioned in my post that excluding Spider from WB5 made no difference. Thanks for suggesting it though.
Reply #3 Top
update: reinstalling Spider solved that problem. So, all is well in WB5 land.

Thanks to PowerUser BX for pointing me in the right direction on Synergy, which helped me debug Spider seperately.
Reply #4 Top
My pleasure ...

BX