Could not output file LavishCrashMobile.exe

[fireymerlin]

I'm unable to launch Innerspace.exe this morning. I keep getting a popup window with the message: Could not output file LavishCrashMobile.exe.
I'm having to reboot my PC to get rid of that message.

[MiRai]

I'm unable to launch Innerspace.exe this morning. I keep getting a popup window with the message: Could not output file LavishCrashMobile.exe.

There was a patch for Inner Space recently and something is probably "stuck." You can likely just re-run the latest installer over the top of your current install to fix this.

I'm having to reboot my PC to get rid of that message.

You can likely kill any Inner Space processes in the Task Manager rather than rebooting. You didn't mention whether you had or hadn't tried this already, so I'm just throwing it out there.

[fireymerlin]

I uninstalled/reinstalled the ISBoxer bundle, but still have the problem.

One big issue, is that I can't find a way to get rid of the popup message other than to log off or reboot the PC.

[fireymerlin]

I just tried to install overtop of the current install. Same issue.

For me, my virus scanner (F-Secure) picked up said file this morning and threw a hissyfit, and indeed caused an endless loop I could only interrupt by rebooting. I ended up making an exception for that particular file and also submitted it as I suspect it to be a false positive. Perhaps anti-virus software is causing the same issue for you?

[fireymerlin]

I use BitDefender antivirus.
I rebooted, disabled BitDefender, re-installed isboxerbundle and now it is working.
Thanks.

Teriffic, glad to hear it!

I was having the same problem. I turned off Ad-Aware Anti-virus and it patched and the started as it normally does. I had to reboot and turn it off prior to starting it up. I am not sure if I will need to keep it off until after I start the program every time, but for now it gets around the problem.

[lax]

LavishCrashMobile.exe has not been updated since Nov 11. If you've patched Inner Space since that time, and it's downloading this file, it's probably because your AV quarantined it based on a false positive -- sometime between the time you last restarted Inner Space and this time. Sounds like F-Secure and Bit Defender got an update probably in the last 24 hours or so (first reported to me yesterday) that includes this new false positive.

Funny thing is, it was specifically updated on Nov 11 in order to introduce digitally signed binaries for Inner Space. Part the reason for digitally signing is so that AV programs like these should no longer have these false positives.

I had actually read about you doing that in another post, yes, which made this a rather surprising turn of events. In any case, as I mentioned earlier in the thread, I have submitted the file to F-Secure, so hopefully they'll put it back into the "cool and groovy" category.