Initial start up problem?

[Biz101782]

Hey, I have launchbox on 2 other PCs, been using for a while.

I just purchased a brand new mini PC with windows 11.  I downloaded launchbox like I normally did in the past.  However, when I try to open the LB app, nothing happens. I have tried rebooting my PC, uninstalling and reinstalling LB.  Any ideas?  Maybe a security setting on my new PC I need to adjust?

 

Thanks

[dragonjade]

My personal issue when I had this problem with start up app stalling, was Webroot. I disable webroot before launching LB. Additionally i noticed that when installing LB that it never seemed to actually complete the install, thus compounding the problem. So, I uninstalled LB, diasbled Webroot (Secure Anywhere) and LB completed the install just fine. However, on  occasion if I forget to diasble webroot before launching LB...LB works fine, other times it does not, weird. Disabling Webroot first, always works. You can re-enable Webroot after launching without issue.

[JoeViking245]

1 hour ago, dragonjade said:

on  occasion if I forget to diasble webroot before launching LB...LB works fine, other times it does not, weird. Disabling Webroot first, always works. You can re-enable Webroot after launching without issue.

If you're adamant about having Webroot on your system and have LaunchBox v13.1 or newer, you can user the feature under Tools < Options < General < Startup Applications to run an application at LaunchBox and/or BigBox startup.

In your case, the "Application" may be Webroot.exe (or whatever it is) and then some Command-line Parameters to disable it.  If it doesn't have the option for parameters to disable it, you could create a batch file (or an AHK or Python [or whatever your flavor] script) that will kill the process.

Then if you wanted, your script could then also "wait around" while LB/BB is still active, then when it's not (aka you exited LB/BB), have it restart Webroot.

Or... just remember to disable it before starting LB.  

 

I'm not familiar with anti-virus type apps other than MS's built-in Defender (which in most all cases is plenty sufficient). But I do know you can create 'exclusions' for them so they don't "freak out" about certain (specific) apps.  So if it's able to, create an exclusion for the LaunchBox folder structure (not just the app) and that should alleviate needing any of the above.