Updated to 13.19 and ended up with a failed update

[tlmw2001]

updated from 13.16 to 13.19 and was greeted with this: https://imgur.com/a/pYzOS3B how do i fix this? ive tried to roll back but now im getting errors for dlls being blocked but there isnt any option to unblock them, this is on a dedicated arcade cabinet from extreme home arcades

[AstroBob]

Hi there,

Thanks for the report, and sorry for the issues you’re experiencing.

Unfortunately, it’s hard to determine the exact cause from the provided error, as much of it has been cut off. If possible, please copy and paste the full report so we can investigate further. However, based on what’s visible, it looks like the issue is related to a third-party plugin that hasn’t been updated for .NET 9.0, which is required by LaunchBox 13.19.

If you have any third-party plugins installed, please remove them from your LaunchBox\Plugins directory and check if the error persists. If removing them resolves the issue, you can reintroduce them one by one to identify the problematic plugin.

If you’re still seeing errors related to blocked .dll files, it’s possible that your antivirus software is being overly aggressive and placing locks on these files, which are required for LaunchBox to run.

To troubleshoot this:

• Check which specific .dll file is mentioned in the error.
• If it’s pointing to anything within the LaunchBox\Plugins directory (commonly affecting emulator integrations like ScummVM, Dolphin, MAME, etc.), try deleting the affected .dll files.
• LaunchBox will recreate them upon the next startup, which should hopefully remove any locks imposed by any antivirus software.

Let me know how it goes!

Cheers,

[tlmw2001]

so i deleted all the plugins as you said and the folders repopulated so i started aOmegaSettingsMenu.dlldding each file one by one until i hit the problem file which was "OmegaSettingsMenu.dll". You wouldnt happen to know what that file does or how to fix it would you? i bought this arcade from extreme home arcades if that helps https://forums.launchbox-app.com/applications/core/interface/file/attachment.php?id=119858&key=7cf6608415004e83e577ff1d32490076

Edited February 19 by tlmw2001

[AstroBob]

Hi there,

Thanks for the update, we've seen quite a few people who have this plugin installed have the same issue and also have one of the extreme home arcade builds. Unfortunately, we don't really know what it does, since it doesn't appear to be hosted on our forums, and if you've purchased a build from another source it's likely something that came from that seller.

Chances are, if you're unaware of what it does and if removing it doesn't have any impact on your usual LaunchBox workflows that it can be safely removed.

Hopefully, other users who use this plugin may be able to chime in on its usage here, but glad to hear you found the culprit.

Cheers,

[C-Beats]

I went ahead and decompiled the library attached. It looks like they are using that DLL to render your marquee. They are basically creating a WinForm window that is displayed in your marquee. The library allows you to change the settings for it. You could potentially look into the Third Screen Plugin found on the forums or just use Big Box's marquee view for marquee functionality.

[superrob3000]

5 hours ago, C-Beats said:

I went ahead and decompiled the library attached. It looks like they are using that DLL to render your marquee. They are basically creating a WinForm window that is displayed in your marquee. The library allows you to change the settings for it. You could potentially look into the Third Screen Plugin found on the forums or just use Big Box's marquee view for marquee functionality.

I wrote it. It automates some stuff for that drive like enabling/disabling scanlines in various emulators, backing up favorites, hiding/unhiding the mature platform, etc.. (nothing that can't also be done manually). On older versions of the drive it also handles marquees because it was back before BigBox had video marquee support.

P.S. I don't work for that company and I no longer even use that drive which is why I don't want to update the plugin (I wouldn't be able to test it out).

[mandydaws]

Thanks to superrob3000, he updated our plugin (OMEGA) so it works perfectly and installs the updated 6.0 version of 3rd Screen app so in one shot fixed all of our headaches...   Now the only problem is that ever other computer we test 13.19 on... 13.19 version of Launchbox Crashes after 1-2 seconds of clicking on it, NO Error Log, no Plugins in the plugin directory... a FRESH install of 13.19 and it doesn't get off the starting line.  Nothing to do with superrob3000's AWESOME plugin update, 100% a 13.19 Launchbox ERROR of some sort.  13.18 runs great on the exact same same computer... ARGH.

[superrob3000]

Here were the event viewer entries if it helps:

Faulting application name: LaunchBox.exe, version: 13.19.0.0, time stamp: 0x67580000
Faulting module name: KERNELBASE.dll, version: 10.0.19041.1503, time stamp: 0xb2acaea9
Exception code: 0xc0000602
Fault offset: 0x000000000010b382
Faulting process id: 0x604
Faulting application start time: 0x01db83d9c5d7042c
Faulting application path: C:\Users\Administrator\LaunchBox\Core\LaunchBox.exe
Faulting module path: C:\Windows\System32\KERNELBASE.dll
Report Id: 13915c48-25e5-4e3b-8a5c-2d7f4942e957
Faulting package full name: 
Faulting package-relative application ID: 

Faulting application name: BigBox.exe, version: 13.19.0.0, time stamp: 0x67580000
Faulting module name: KERNELBASE.dll, version: 10.0.19041.1503, time stamp: 0xb2acaea9
Exception code: 0xc0000602
Fault offset: 0x000000000010b382
Faulting process id: 0x2bd8
Faulting application start time: 0x01db83d97bbc825c
Faulting application path: C:\Users\Administrator\LaunchBox\Core\BigBox.exe
Faulting module path: C:\Windows\System32\KERNELBASE.dll
Report Id: ec7d79d7-ae97-49a5-a0c3-b558461f0f69
Faulting package full name: 
Faulting package-relative application ID: 

[mandydaws]

To all EHA Customers, you can use Rob's 3.1 Fix but ONLY if you do NOT have a H610i motherboard.

If you have H610i System Board (run Motherboard Identifier App on the Quick Launch ICONS on the bottom Left Windows START BAR) you cannot run 13.19 version of Launchbox (Yet) because it does not work with this motherboard for some reason (we will have it figured out soon)

 

If you have any other motherboard (besides the H610i) you can run this 13.19 Launchbox Update and after you get the error (close out all error windows) just run this file:

 

30.13 MB file on MEGA

 

[mandydaws]

Actually, after testing on a new B760i, and B660i, NEITHER will load even the simplest Vanilla Launchbox 13.19 Build.  Not sure what to do with this.  13.19 just does not run on certain motherboards, I'm sure the list will grow... Definitely need a fix to all this from Launchbox (Unbroken Software LLC)

[C-Beats]

Our application isn't written in something similar to assembly so the likelihood that a change in motherboard is the cause for this is highly unlikely. On the extremely unlikely event the motherboard IS the cause of some compatibility it'd be with one of the runtimes in use by the application, not the application itself. The runtimes in questions would be things like Visual C++ runtimes, Direct X, .NET 3.1, and .NET 9 runtimes. That is the code that is hitting at that level more so than ours and would need corrected. None of which are controlled by us so not something we'd be able to "fix". As I understand support has reached out to you and is willing to work with you regarding the issue. If the meantime if there are any customers of yours with any of these systems I'd suggest doing some of the following to help correct any issues on the OS level that could cause issues that would be perceived as a cause for this.

Ensure all drivers/BIOS are up to date for hardware (MOBO, CPU, GPU are the main ones, ensure Direct X is up to date can help as well)

Open powershell as admin and run the following: Dism /Online /Cleanup-Image /ScanHealth
(run this first. This checks that the comparison values of the next tool are correct and so ensures it works properly)

If any corruption is found you can run the following in that same elevated powershell window to correct: Dism /Online /Cleanup-Image /RestoreHealth
(if this step is needed a computer restart should be performed before the following)

Open command prompt as admin and run the following: sfc /scannow
(this command checks OS system files for corruption and attempts to clean up any issues found, if it finds and repairs anything please restart your computer before attempting to start LaunchBox again)

Verify your OS settings and your MOBO settings are playing nice. Win11 adds a lot of hardware level security settings and there being a mismatch in there can cause operation issues, especially when hitting the filesystem like we do.

If you do the above and it still doesn't work please perform the following:
Navigate to \\LaunchBox\Core and run LaunchBox.exe, allow it to crash
Open Task Manager and ensure it's no longer running in the background
Open Windows Event Viewer
Navigate to your application logs
Look for two errors back to back pertaining to the failure of LaunchBox
Send us BOTH error logs. One typically is far better use than the other and so having both just makes sure we get the one with more pertinent information.

A report of your hardware could also help. If you could run msinfo32 (press Win+R and then type it in run and press enter) and get a screen grab of the first summary screen it opens to that could help us gather more hardware specific information.

[mandydaws]

After a tip from SuperRob3000 (ROB IS AWESOME!) that this issue may have something to do with Windows Updates being paused/turned OFF on our systems.  We've found that after installing the latest Windows 10 updates that 13.19 of Launchbox now runs on these motherboards so that was the answer to this particular quandary...

The only issue now is testing everything to see what the Windows Updates may have now broken as far as the 100's of other emulation and utility software we use on these systems.  Fix One Thing and more than likely we have broken something else.  The Good News is that at least we found the culprit of Launchbox 13.19 NOT running on 3 of our tested motherboard types.  WINDOWS UPDATE - ARGH!