On_fire

Yeah, that's pretty much what I figured. I really meant more of some path hardcoded in a config file or something, probably caused by something I did, though I guess that wouldn't explain it not working from before I could change any settings...

I am running Windows 10 (64 bit) and have the following drives: C:\ - 120 GB SSD - OS Only E:\ - 3 TB HDD - Programs F:\ - 2 TB HDD - Data I tried installing LaunchBox 8.1 into E:\Program Files (x86)\LaunchBox and it would crash every time as soon as it opened. So, I installed it in the default location (C:\users), and it worked fine. Then I tried moving the working installation to: E:\LaunchBox and it broke again. So I moved the same installation to C:\LaunchBox and it started working again. Then I moved it to F:\LaunchBox and it's still working... Any idea why it just refuses to run on E:\? Also, the Logs folder is empty, so I don't really know what other relevant information I can provide, let me know if I've missed something,,, (I'm sure I probably have, lol.) UPDATE: I deleted the copy from C:\LaunchBox And my working copy in: F:\LaunchBox Stopped working... I feel like something is hardcoded to C:\ but the weird thing is it works in 2 separate folders on C:\ just fine... Also, I tried looking in Settings.xml for "C:" and wasn't able to find anything... UPDATE 2: I was able to get it working by making a hard link from C:\LaunchBox to E:\LaunchBox by running the following command in an elevated command prompt: mklink /J C:\LaunchBox E:\LaunchBox The weird thing is that the Start Menu shortcut has to point to the actual copy (E:\LaunchBox), if it is pointed to C:\LaunchBox, it crashes as if it was launched without the link in place... Still not sure if this is a bug, or something REALLY weird with my computer...