Launch issue.
-
I’m getting this launch issue when I try to start Falcon from the desktop or the start menu. The current “work-around” is to go into the Bin\x64 folder and launch it from there. This also forces me to launch IVC manually and all the fun that comes with that. I discussed this with my squadron last night during training and we couldn’t figure out what the deal is. Any thoughts???
I appreciate any responses.
-
What happens when you double-click on Hub.exe? Does it start?
-
What happens when you double-click on Hub.exe? Does it start?
It will launch via Hub.exe with the option of 32/64 bit however, “Configuration” is grayed out.
-
It’s a new one on me, but others who have seen it have pointed the finger at anti-virus software.
Are you (an unpaid beta-tester for Microsoft) using Windows 10, with Defender enabled by any chance?
-
It’s a new one on me, but others who have seen it have pointed the finger at anti-virus software.
Are you (an unpaid beta-tester for Microsoft) using Windows 10, with Defender enabled by any chance?
I do but I always have as well and hadn’t seen this until now. As long as IVC will auto launch from Hub.exe (which I think it will) I’ll work around it until I get the motivation to clean install.
Thank you for responding Darkman. Next pint is on me.
-
Ok so……Error Code 3: The system cannot find the path specified. [ERROR_PATH_NOT_FOUND (0x3)]
From what I’ve been able to find this error is generally caused by a corrupted registry or system file. Honestly Chaser the overall quickest fix to this problem would to be to back up your user folder in BMS and do a clean install. Here in the forum (somewhere) is a link for a download to a “BMS clean registry” exe file that will clean up the registry so you don’t have any residual conflicting bms registry files. Prob going to be your quickest fix all in all.
-
The right path take u must…
Step in to the light…
May the force be with u.
-
Ok so……Error Code 3: The system cannot find the path specified. [ERROR_PATH_NOT_FOUND (0x3)]
From what I’ve been able to find this error is generally caused by a corrupted registry or system file. Honestly Chaser the overall quickest fix to this problem would to be to back up your user folder in BMS and do a clean install. Here in the forum (somewhere) is a link for a download to a “BMS clean registry” exe file that will clean up the registry so you don’t have any residual conflicting bms registry files. Prob going to be your quickest fix all in all.
Roger that. Currently downloading Teamviewer so you can do it for me :uham: