JaredN

Thanks @JoeViking245 ! I'll keep using the double-click workaround until the problem is actually fixed. It's no big deal! 😉

Hello! From what I can tell so far, when using VLC, I no longer experience any crashes—whether random or not—with or without error messages. I don't encounter any issues at startup, whether with LB or BB. Startup is fast and crash-free. Occasionally—though much more rarely—there are processes that haven’t closed and need to be terminated via the Task Manager, even though the shutdown window indicates that everything has closed. My browsing is smooth in both BigBox and LaunchBox, with no particular issues. When this beta was released, I grumbled a bit because it didn't fix a number of issues that I—and others—had reported. Nevertheless, looking back, and even though I’m sad to hear that some users are still experiencing major issues (I’m keeping my fingers crossed that things will get back to normal for them soon as well), I have to admit that aside from those few issues—which should be fixed in the next beta—everything is working almost perfectly on my system now. Great job, guys! Thanks My setup: i5-14400F, RTX 5060 Ti (16 Go), 32Go DDR5 (6000mhz) & Windows 11 Home. LB/BB is installed on a 4 To Crucial X9 external SSD with just over 1 To of free space. My collection has a little over 10,000 games. I don't use storefronts. Automatic import of ROMs, media, or content from stores at startup is disabled.

Thank you @Drybonz! English isn't my native language, so I sometimes miss certain nuances. 😅😉

Hi @faeran! What do you mean by an “edge case scenario”? Is it something related to Microsoft Edge settings? Do you have any ideas I could test? Don’t worry, it’s no big deal, and if I can’t fix it, I’ll just deal with it. But since I’m at it, I’d prefer to understand where it might be coming from! Otherwise, I see that the other issues I was having should be fixed in the next beta! That’s great! Thanks for your reply and for all your hard work!

Still the exact same behavior ... Nothing has changed ... This workaround addressed the issue of returning to BB when the B button was double-pressed. The problem is still present, as is the workaround. Hello, All in all, I have to admit that I’m rather disappointed with this Beta 4, which—aside from the issue with displaying manuals in BB—doesn’t fix many problems I reported in Beta 3. So, the previous reports are still entirely relevant to me. Thanks for your work anyway. I’m well aware that not everything can be fixed all at once!

Hi, A few details about the issue with reading the manual from the pause menu. It also seems to be a focus issue. When I select “Read Manual,” it does open the manual in a separate window, but BB doesn't release the focus, and Alt+Tab doesn't change anything. If I press it again, BB opens a new one, and so on. Closing the pause menu, however, does allow me to access the manual window (see video). On the topic of focus, there’s another issue: in what seems to me to be a random manner (though it likely isn’t), when I launch LaunchBox from Windows (not BB), it often doesn’t take focus, and I have to find it in the taskbar or use Alt-Tab to bring it up (see video). However, I have absolutely no issues opening or closing LB or BB—everything is fast and runs smoothly. I have a library of about 10,000 games with a strong focus on collections (300+ playlists and about 40 platforms). However, I don’t use the automatic ROM import or the automatic game import from storefronts (which I don’t use at all). I have both of these options unchecked. I don’t know if that helps. I have a “good” PC, but it's not exactly a “powerhouse” either. I have an Intel(R) Core(TM) i5-14400F (2.50 GHz), a GeForce RTX 5060 Ti (16 GB), and 32 GB of DDR5. LB/BB is installed on a 4 GB Crucial X9 external SSD (with about 1 GB of free space). And I'm running Windows 11 Home. Finally, here’s a video illustrating the issue with playlists in BigBox that don’t follow the display rule (release date in this case) I’ve chosen—a rule that is applied in LB. Thanks for your work anyway! Collections.mp4 Reader.mp4 Opening.mp4

Hi, I have the same problem and used the same temporary "solution": disabling the startup screen.

Hello, I use a lot of playlists, especially for collections where games are sorted by release date. In LaunchBox, there's no problem. However, in BigBox, they are no longer sorted by release date but by alphabetical order... Thanks again for your work!

Great! That's right—no more problems with the background music, whether using VLC or WMP! Thank you so much!

Hi @crusadeRGP ! Same issue for me.

And here's the same thing using WMP, since it behaves differently (the background music never starts). Thanks @MysterNybble ! LOG WMP.mp4 Debug 2026-07-01 06-50-47 AM.log MediaEngine 2026-07-01 06-51-30 AM.worker.log MediaEngine Client 2026-07-01 06-51-30 AM.log

Thank you @MysterNybble, When using VLC, here are the logs and a video I recorded at the same time so you can see exactly what I did. I hope this helps resolve the issue! LOG.mp4 Debug 2026-07-01 06-27-50 AM.log MediaEngine 2026-07-01 06-28-32 AM.worker.log MediaEngine Client 2026-07-01 06-28-32 AM.log

One more thing: when minimized to the taskbar, LaunchBox resists "Alt-Tab" (it just makes a "DONG" sound). It doesn't do this when you use "Alt-Tab" from within LaunchBox without minimizing it. Returning to LaunchBox via the taskbar doesn’t work on the first click either. The first click triggers a “dong,” and the second click brings you back to LaunchBox. I don’t know if this is the intended behavior, but it’s definitely strange... This “issue” was already present in Beta 2, but I hadn’t found the time to report it. LB.mp4

Hello, I'm having a problem with the background music. With VLC, when “Play video audio with background music” is unchecked, I don't hear any sound from the video or any background music. If I check it, both start playing as soon as the video begins. With WMP or FFMPEG, I don’t get any background music at all. If “Play video audio with background music” is unchecked, nothing plays. If I check it, I only hear the video’s audio... These issues weren’t present in Beta 2. However, Beta 3 completely fixed the choppy video issues I was having in LaunchBox and the responsiveness issues (such as a VERY unstable frame rate) I was having in BigBox, which made navigating the menus very hit-or-miss. Finally, just testing FFMPEG for a few minutes for this post was enough to crash BigBox. VLC, on the other hand, seems stable. And I haven’t retested WPM enough to give you a reliable opinion. A big thank you for your work! VLC.mp4 WMP FFMPEG.mp4

And by the way, since it’s nice to point out what we like—not just what we don’t—I really love how LB/BB handles startup and shutdown now! Thanks! 👍

Hello @faeran ! Is this update still planned? The way Launchbox currently detects ScummVM games prevents any game-specific settings from being applied via the ScummVM stand-alone too, other than global settings. Similarly, save files created via LB/BB do not point to the same ID and have names that prevent them from being detected by LB/BB, and vice versa. Personally, I’d like to be able to use ScummVM on a laptop that doesn’t handle LB/BB well and then transfer my saves to my main PC and LB/BB later. That’s impossible right now given how ScummVM games are handled. So for now, I’ve stopped using LB/BB for ScummVM games, which I’m running as stand-alone apps, but I’d like to be able to reintegrate them into my collection. Thanks for your great work anyway !

Thank you very much @Fursphere ! This confirms that the problem isn't caused by my settings and that it's a broader issue. I hope it will be fixed in the next beta releases. In the meantime, no crashes with WMP so far! It seems pretty stable.

Thanks @Fursphere ! WMP seems pretty stable on my end too. And honestly, as long as one of the video decoders works properly, I'm fine with that! But it's still very strange. I’ve had this issue with FFmpeg from the start, on my old PC (RTX 3060 Ti, Intel CPU, 16GB of RAM), a new machine (RTX 5060 Ti 16GB, different Intel CPU, 32GB of RAM), and on a Legion GO (AMD architecture). I haven’t retested on the old one (which I no longer have) or on the Legion GO recently, but it doesn’t seem to be a hardware issue. I’ve also tested with the files on an internal SSD, an external SSD, an SD card, with and without antivirus, with the default themes, without plugins... With the new installation, I started from scratch. I re-imported my ROMs, reconfigured LB and BB so they wouldn’t use my old config files… but no. Still random crashes with FFmpeg. AND sometimes with WMP, but less so. The only common factor across all of this is Windows 11 and certain settings shared between the machines. Windows is up to date and my drivers are up to date. And I tested it without applying scaling. And I’m well aware that not everyone is experiencing this issue and that the devs can’t reproduce it… so there’s something going on! But what? Fortunately, @faeran just confirmed that they haven’t tried to fix this issue in this beta yet, but that it’s in the works, so I imagine it’s coming! Thanks anyway for the suggestion, @Fursphere ! I’m sure some additional testing could help.

I spoke too soon... BB still crashes with FFmpeg, too. With FFmpeg, I'd say that LB and BB seem even more unstable than before. I'm switching back to WMP. I hope that goes better. 😕 BB 1.evtx

Launchbox is more unstable than ever with FFmpeg... 2 crashes in less than 5 minutes after the update. BigBox seems to be holding up better. To be confirmed. In any case, thanks for the update! 😉 LB 1.evtx LB 2.evtx

I'm also experiencing the same issues, which I've reported multiple times. I recently switched computers. My installation is “clean,” and I'm still having this problem. I had it before with an RTX 3060 Ti, and I still have it now with an RTX 5060 Ti (16GB) and 32GB of RAM. The CPUs for both setups were Intel. And I’m also having the same issues on a Legion Go with an AMD architecture... Windows 11 is up to date, and my drivers are up to date. And it crashes on all three machines, more often when using FFmpeg than WMP. The difference is that LB can crash with FFmpeg, but that hasn’t happened to me recently with WMP. BB crashes regularly with both, but more often with FFmpeg.

Hello @AstroBob Unfortunately, “unexpected” crashes are still a common occurrence for me in this version when I use FFmpeg. They've been happening ever since FFmpeg was implemented. On my old PC with an RTX 3060 Ti, on my “new” PC with a clean install—sharing no components with the first one—and an RTX 5060 Ti, and on my Legion GO, which shares NOTHING in terms of hardware or peripherals with my desktop PCs (AMD vs. Intel/Nvidia), with or without antivirus enabled (BitDefender). I also reinstalled LB “from scratch,” without using my old config files and by reimporting all my ROMs. I have no plugins installed other than those ‘required’ by LB/BB for emulator management, and I don’t use any “exotic” themes—only those provided by BB. Other than that, my system (Windows 11 Home) is up to date, as are my drivers. I’m using an external Crucial SSD on my desktop PC, but I also tried installing LB/BB on my main internal SSD (Samsung 990 PRO), and it didn’t make any difference! I’m switching back to WMP, which seems to be working pretty well for now. Thanks anyway for all your hard work ! BB.evtx

Hello! Thanks for this beta! As noted by @Rlad, the auto-import wizard launches at startup whether or not it's checked in the options. BUT if it's not checked, it doesn't seem to be “actually” active! It's brief, and in my case, it doesn't detect a ROM that's been added. On the other hand, if I check the option, it seems to perform a proper scan, detects the added ROM... and crashes for no apparent reason in that case. See attached video. And I didn’t look into it (the crash) further because that wasn’t the point. However, the added ROM was a different version (in another language) of a ROM that was already present. Maybe that’s related? As for the fanart backgrounds, I get the same crash as @Rlad when I try to view them in BB using the “View images fullscreen” option. No problem in LB, though. BUT I don't have this problem only with fanart backgrounds. Here is the log of an error that occurred with a Disc image, without any fanart background present : The calling thread cannot access this object because a different thread owns it. App: Big Box Version: 13.27-beta-4 Theme: VisioN Type: System.InvalidOperationException Site: Void <VerifyAccess>g__ThrowVerifyAccess|7_0() Source: WindowsBase at System.Windows.Threading.Dispatcher.<VerifyAccess>g__ThrowVerifyAccess|7_0() at System.Windows.DependencyObject.GetValue(DependencyProperty dp) at System.Windows.Controls.Image.get_Source() at Unbroken.LaunchBox.Windows.Controls.PixelPerfectImageScaler.InsertServerController() at RandomCompressorAggregator.ReadExplorerList(Object, RandomCompressorAggregator) at Unbroken.LaunchBox.Windows.Controls.PixelPerfectImageScaler.ResetScale() at PassiveDicAggregator.ReadExplorerList(Object, PassiveDicAggregator) at Unbroken.LaunchBox.Windows.Controls.PixelPerfectImageScaler.set_ScaleMode(PixelPerfectImageScaleMode value) at Unbroken.LaunchBox.Windows.BigBox.ViewModels.ImagesViewModel.AssembleReg() at AggregatorBuilderPredictor.SumCustomizableProgram(Object, AggregatorBuilderPredictor) at Unbroken.LaunchBox.Windows.BigBox.ViewModels.ImagesViewModel.ConvertRandomSubscriber() at ConverterDictionary.SumCustomizableProgram(Object, ConverterDictionary) at Unbroken.LaunchBox.Windows.BigBox.ViewModels.ImagesViewModel.OnRight(Boolean held, Boolean onlyRightPressed) at Unbroken.LaunchBox.Windows.BigBox.NavigationManager.OnRight(Boolean held, Boolean onlyPressed) at RemoteResolverAggregator.SumCustomizableProgram(Object, Boolean held, Boolean onlyPressed, RemoteResolverAggregator) at Unbroken.LaunchBox.Windows.BigBox.ViewModels.MainViewModel.OnRight(Boolean onlyRightPressed) at AggregatorTaskTransformer.SumCustomizableProgram(Object, Boolean onlyRightPressed, AggregatorTaskTransformer) at Unbroken.LaunchBox.Windows.BigBox.ViewModels.MainViewModel.InterruptDecorator(Guid setup) at (Object, Guid) at TransferableSetAggregator.SumCustomizableProgram(Object, Guid setup, TransferableSetAggregator) at Unbroken.LaunchBox.Windows.BigBox.ViewModels.MainViewModel.<>c__DisplayClass261_1.ReceiveGroupedObserver() at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state) --- End of stack trace from previous location --- at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state) Recent Log: 09:16:04 Exception --------------------- As for FFmpeg, it still seems just as unstable to me, since LB shut down without an error message a few minutes after I switched to FFmpeg instead of WMP. I haven't retested it in BB, but I imagine the problem must be the same. Thanks anyway for this update! Enregistrement de l'écran 2026-05-05 084028.mp4

More annoying bug: When I try to download logos, the download only starts for the first 2 or 3, or doesn't start, if I chose to limit the number of downloads for the category. If I don't limit it anymore, it works again. I only tested it for the Gamecube, the only platform I needed to update. Enregistrement de l'écran 2026-04-28 205047.mp4

Minor bug: The "Close" button in Manage Storefronts causes the app to crash. Closing the app without using the button does not. No target found for method Close. App: LaunchBox Version: 13.27-beta-3 Theme: Default Type: System.Exception Site: Void Invoke(System.Object) Source: Caliburn.Micro.Platform at Caliburn.Micro.ActionMessage.Invoke(Object eventArgs) at Microsoft.Xaml.Behaviors.TriggerBase.InvokeActions(Object parameter) at System.Windows.EventRoute.InvokeHandlersImpl(Object source, RoutedEventArgs args, Boolean reRaised) at System.Windows.UIElement.RaiseEventImpl(DependencyObject sender, RoutedEventArgs args) at System.Windows.Controls.Primitives.ButtonBase.OnClick() at System.Windows.Controls.Button.OnClick() at System.Windows.Controls.Primitives.ButtonBase.OnMouseLeftButtonUp(MouseButtonEventArgs e) at System.Windows.RoutedEventArgs.InvokeHandler(Delegate handler, Object target) at System.Windows.EventRoute.InvokeHandlersImpl(Object source, RoutedEventArgs args, Boolean reRaised) at System.Windows.UIElement.ReRaiseEventAs(DependencyObject sender, RoutedEventArgs args, RoutedEvent newEvent) at System.Windows.RoutedEventArgs.InvokeHandler(Delegate handler, Object target) at System.Windows.EventRoute.InvokeHandlersImpl(Object source, RoutedEventArgs args, Boolean reRaised) at System.Windows.UIElement.RaiseEventImpl(DependencyObject sender, RoutedEventArgs args) at System.Windows.UIElement.RaiseTrustedEvent(RoutedEventArgs args) at System.Windows.Input.InputManager.ProcessStagingArea() at System.Windows.Interop.HwndMouseInputProvider.ReportInput(IntPtr hwnd, InputMode mode, Int32 timestamp, RawMouseActions actions, Int32 x, Int32 y, Int32 wheel) at System.Windows.Interop.HwndMouseInputProvider.FilterMessage(IntPtr hwnd, WindowMessage msg, IntPtr wParam, IntPtr lParam, Boolean& handled) at System.Windows.Interop.HwndSource.InputFilterMessage(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled) at MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled) at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs) at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler) Enregistrement de l'écran 2026-04-28 145427.mp4