Rebooted PC & Launchbox Lost All Content

[Starwind Amada]

What if I get a second PC and only have Launchbox on there? Maybe a mid-range gaming laptop and nothing else goes on it. Because this is ridiculous that nothing I've done works.

[JoeViking245]

1 hour ago, Starwind Amada said:

What if I get a second PC and only have Launchbox on there? Maybe a mid-range gaming laptop and nothing else goes on it. Because this is ridiculous that nothing I've done works.

I mean, that is an option.  Though would be nice to figure what's going on with your current system.

(Forgive me, but have to say...) I presume you've restarted the computer at some point during all this. 

• Open Windows explorer and navigate to F:\LaunchBox and double-click LaunchBox.exe.  This will eliminate any errant shortcuts.
• When you get the "Another instance of LaunchBox is already running" message box, click OK to close that window.
• Back in Windows Explorer, click once on the address bar, type in "cmd" (without quotes) and press Enter.
  
• This will bring up the Windows Command prompt window.
• Type in the following and press Enter.  This will tell you the full path to the LaunchBox.exe that "is already running".
  • powershell "Get-Process launchbox | Select-Object Name, Path"
• Run the command again, changing "launchbox" to "bigbox" (this will verify if it had attempted to be shelled)
  • powershell "Get-Process bigbox | Select-Object Name, Path"
• 

Hopefully this will shed some light on what's going on.

[Starwind Amada]

1 hour ago, JoeViking245 said:

I mean, that is an option.  Though would be nice to figure what's going on with your current system.

(Forgive me, but have to say...) I presume you've restarted the computer at some point during all this. 

• Open Windows explorer and navigate to F:\LaunchBox and double-click LaunchBox.exe.  This will eliminate any errant shortcuts.
• When you get the "Another instance of LaunchBox is already running" message box, click OK to close that window.
• Back in Windows Explorer, click once on the address bar, type in "cmd" (without quotes) and press Enter.
  
• This will bring up the Windows Command prompt window.
• Type in the following and press Enter.  This will tell you the full path to the LaunchBox.exe that "is already running".
  • powershell "Get-Process launchbox | Select-Object Name, Path"
• Run the command again, changing "launchbox" to "bigbox" (this will verify if it had attempted to be shelled)
  • powershell "Get-Process bigbox | Select-Object Name, Path"
• 

Hopefully this will shed some light on what's going on.

I'll try this when I get home from work tomorrow

[Starwind Amada]

22 hours ago, Starwind Amada said:

I'll try this when I get home from work tomorrow

Didn't work. Now it won't even give me the message about another instance. Of course not. This is a lost cause.

[JoeViking245]

1 hour ago, Starwind Amada said:

it won't even give me the message about another instance

This is good. Now we know for sure it's not running elsewhere.

Based on your subsequent comment, I presume it's not starting either. 
Does any kind of loading screen at least start to show?  Or just the spiny circle then nothing?

If the latter, run the Command Prompt command(s) again to be sure it's not hiding in the background from the previous attempt to start.  If it is, reboot the PC.

• Run the installer (LaunchBox-14.0.1-Setup.exe). 
• When asked where to install it, select the F drive.
  • Don't select F:\LaunchBox. 
  • This of course assumes your latest install is in F:\LaunchBox.
• Before clicking the final Install button, verify the path it tells you it's installing to is F:\LaunchBox.
  • At this point, you could edit the path (to e.g. F:\LaunchBox-Test) to create [another] brand new install, if you wanted, since we know another instance isn't running in the background to mess things up.
• Read all the prompts.
• Don't skip any supplemental prompts for items it may ask to install
  • The exception is for installing the optional K-Lite Codec Pack
  • (skipping this one is up to you and won't affect LB running)

This process will give you a fresh install (update) in you same location without undoing any of your settings or removing and of your imported platforms.  (Unless you edited the path)

At the end of this process, LaunchBox 'should' startup when it's done updating (or installing onto the new path).

[Starwind Amada]

It just says Name/Path with Launchbox under Name twice. No path.

I'm done. Nothing will fix this.