Jason Carr

That's confusing. It shouldn't need to download .NET Core 3.1.6 again. Maybe the .NET Core install didn't finish properly the last time?

I see, thank you very much. I have reports from 4 different people who are having issues, and I'm not sure if they're all having the same issue, but that's certainly a lead.

Thank you guys. Are either of you interested in continuing to help me troubleshoot this? If so, can you try deleting your LaunchBox\ThirdParty\CefSharp folder (only the CefSharp folder) and then re-installing 11.3? I think I might be onto what the issue is, but I need to confirm.

Interesting, that's telling. So you're up and running then on 11.3? Do you remember what the specific error was that you got?

Also, if you would, let me know what version of Windows 10 you're running. You can get to that by searching for winver in your Start menu:

Okay, apologies for the trouble @im_etten. I've reverted the official release for now back to 11.2, because four people have run into this and reported it. At this point I have no idea why it's happening only on certain systems, and I haven't been able to replicate it. For now, you should be able to downgrade back to 11.2 by just installing it over the top (just make sure you install it to the correct folder, and not a folder inside of your LaunchBox folder). If you need a copy of 11.2, you can download it here: https://www.dropbox.com/s/cg7fteljnwf0s9r/LaunchBox-11.2-Setup.exe?dl=0

@jeffbini Sorry to hear. My best guess at this point is that the issue is caused by a corrupt .NET Framework install. Can you both try downloading and running this: https://www.microsoft.com/en-gb/download/details.aspx?id=30135 Let me know if that helps. You may need to reboot the PC after the running the tool.

Okay, the specific error that @luvablemarmot reported above seems to be the result of a corrupted .NET Framework issue. Can you both try downloading and running this? https://www.microsoft.com/en-gb/download/details.aspx?id=30135 You may also need to reboot.

Hi Boomerps2, sorry for the trouble. Can you try rebooting, and then re-running the LaunchBox 11.3 installer from the LaunchBox\Updates folder?

Also, do you have any anti-virus or anti-malware apps running?

Can you try running LaunchBox\Core\LaunchBox.exe to see if that works?

Hi etten, as far as we know, the new update should be working properly. What version of Windows are you running? Were you prompted to download and install .NET Core?

Just updated the main post and script for the official 11.3 release. Hopefully more folks will be here soon, since we're going to heavily feature it for the 11.3 release.

Yes, even Windows Defender was getting in on the false positive action. I just finally put out the official 11.3 release, and it shouldn't trigger any false positives. Only took me 4 hours to screw around trying to get past them all. Hopefully 11.3 is a stable release.

It is possible that the most recent beta had a false positive. I'm in the middle of putting out the official release and I'm running into awful issues with false positives, so I'm guessing that's what happened. I'm surprised that I can run Windows Defender and create the EXE without issues, and then later gets triggered, but it is what it is I guess.

What version are you running? I use Windows Defender myself and none of the releases have been flagged for me. It is possible though that you do have a virus on your system that went out and infected other EXEs.

I was planning on releasing today (I even have it all uploaded), but unfortunately it turns out I can't because so many files are falsely being triggered by anti-virus engines. Bane of my existence. For some reason this time around it's so bad that I'm going to have to re-code some things just to be able to release. One of the engines that's being triggered is Symantec (what a terrible piece of software, sigh), but it's so commonly used that I really can't just put it out anyways. Back to the drawing board...

I see. I'm still puzzled on this, as I can reproduce any of it. It is interesting that it's happening with both VLC and WMP. To me, that means that it's not likely video related. Also puzzled here, and running out of ideas. All I can figure is maybe a corrupted .NET install, or something of that nature (or maybe anti-virus interference?). This would have to be some sort of stray controller or device, as the movement would have to be triggered by something.

I see. I don't ever recommend using Windows Media Player, but does the problem go away if you switch to the Windows Media Player video playback engine?

Thanks for the video and the logs. The logs unfortunately don't give me anything useful, but the video is helpful. It's strange though because I've never seen Big Box lock up like that while just in the middle of video, with nothing else going on. To be honest, I do wonder if you're having some sort of system stability issue. I can't be certain, but that would be my guess here.

Do you have debug logging enabled? Can you send me some log files of the Big Box startup process with CriticalZone Default?

Good going @jedigu! Sorry I've been distant in this thread; been busy resolving bugs so we can get this release out. I'll be diving back in here soon to see what we can improve.

@Wanderer189 You're seeing issues with the default CriticalZone theme as well? I can't seem to replicate that myself. I'll test Blue Box. I actually didn't change anything in these themes for this release.

I'm puzzled then. I assume it's Windows 10?

This is a Windows error that means it's running out of resources. I'm not sure that there's anything we can do to fix that, unfortunately.