LaunchBox 13.25 Beta Thread

[Hanz]

59 minutes ago, MysterNybble said:

• Improvement: The Edit Game window now includes Next/Previous buttons, allowing you to quickly navigate through the list you opened it from

This is going to make my life so much easier.

[bundangdon]

10 hours ago, MysterNybble said:

Improvement: The Edit Game window now includes Next/Previous buttons, allowing you to quickly navigate through the list you opened it from

This is an excellent addition in the latest beta, and something I've been wanting for quite a while! Thanks a lot for adding this feature in there

[JoeViking245]

14 hours ago, MysterNybble said:

Improvement: The Edit Game window now includes Next/Previous buttons, allowing you to quickly navigate through the list you opened it from

Editing a game then navigating left/right saves changes without issue.  

When navigating in Edit, e.g. 3 games "to the right" and clicking "X" to close the window, the initial game in the Main panel is [still] selected.  But the last game that was in "Edit" is what's shown in the Game Details panel

Same scenario but clicking OK instead of "X" selects/shows the 'last game' in both panels.

[skizzosjt]

On 10/18/2025 at 12:13 PM, skizzosjt said:

LaunchBox gets stuck on "Loading Interface" every time I open the app for the first time after a boot of Windows.

I must end the process and try to open the program again. 2nd time and onward always works OK. so there is an issue with the first boot every time. started with at least v13.24 and continues to current 13.25 beta1. reverting to v13.23 this issue is not present. also, if I instead open Big Box first, Big Box boots fine. I can then open LaunchBox OK, even if it is the first time launching it on that boot. so to be more specific, LaunchBox gets stuck on Loading Interface after boot of Windows as long as Big Box has not been launched first.

It's not 100% of the time anymore as previously stated, but this happens far too often to just ignore this issue. Gets stuck on "Loading Interface..."

For ex, I opened LB fine this morning, update to the beta-3 version, and as the beta auto launches after updating it happens to get stuck on Loading Interface. It's anyone's guess as to whether this is going to happen if it's the first time LB is booted since booting into the OS or if it is multiple boots of LB once booting into the OS. 

As always when it does occur, I must force close and try again.

 

 

Progress tracking is now messed up for at least Steam games. I have many marked as "Done / Beaten". Now when I click on them they are all auto updating to "Active / In Progress" or "Active / Paused" depending on when last launched.  Actually all Steam games are auto updating in ways that no user would want. If I set a value, that's what I want it to be. The way it is currently working means I cannot ever use automated progress tracking and expect any Steam game to use a "Done / Beaten" value as they all get changed automatically against my intentions. This sure seems new to the beta, and I confirm by rolling back to beta-2 this behavior is not there. It's introduced right now in beta-3.

You have features within this progress tracking feature fighting with each other. I want automatic progress tracking, but it cannot fight me when I want to set something manually. 

Another example, Steam game has 100% achievements, and is being automatically updated to Done / Mastered. But maybe user wants it to remain on "Active / In Progress".....right now, this is also not possible. Automated system is too heavy handed in its current iteration.

 

 

Steam Trailers are not fully fixed. 

Unfortunately don't think this is really fixed. I'm still finding some games that cannot download trailers

Issues persist with some games with "new" trailers. Now, nothing shows up for those games for video download options. ie there is no "Steam Trailer Video" checkbox selection available for these games despite there being trailers on their page. Prior to beta-3 it gave the option, but would fail with an error. Here is another example... 

HITMAN WORLD OF ASSASSINATION (formerly HITMAN 3) just uploaded a new trailer for new game content released just now in December. Now this game cannot download any game trailer from within LB. It has no Steam Trailer Video option available when I click the download media button. Same goes for all previously mentioned games with more recent trailers. 

It is otherwise fixed for "legacy" games that are not impacted by having trailers recently uploaded. 

edit: I checked the games I personally mentioned, Tormented Souls 2, Mortal Kombat Legacy Kollection, HITMAN World of Assassination, all these games cannot download trailers as mentioned above. I thought afterwards to check some of the games the other fella mention, Marvel Rivals and Absolum come up empty still for example. But Ninja Gaiden Ragebound will give the option to download its trailer now. So, maybe fixed some of the games falling into this issue, but did not fix all all of them. 

Edited yesterday at 08:40 PM by skizzosjt

[Hedgecore024]

Just downloaded, but so far so good, Steam Trailers are working again, have not had any random crashes when clicking around, nor any metadata issues.

One suggestion, is there a way that the beta spotlight could be kept open while navigating LB? I'm an idiot, so it might be something I'm doing wrong, but it has to be closed to go back into LB. This would make it easier to go through and test the changes and bug fixes that are spotlighted. Not a big deal by any means, but would be a nice QoL feature.

Thanks for all you guys do.

[salofan]

Love the new features - especially the next/previous button in the edit window.

Second skizzosjt that the Steam Trailers are still not working 100 percent. They do not download automatically through the Steam import, and I get an error message. Though I can manually go into the games after they are imported and download the trailers one at a time. It also appears some Steam screenshots and Steam Posters are not downloading all of the time. 

I have also noticed that free to play games from Steam are not being found through the Steam import. This appears to be a new issue - maybe introduced with the other Steam issues? These are games that you "add to library" through Steam without a purchase. Where Winds Meet and Sonic Rumble are two FTP games in my library that LB cannot find through the Steam import wizard. Anyone else having this issue? I'd delete some older FTP games from library and try to re-import, but I'd rather not lose the games if I can't put them back.

Anyway, great new features, and am glad the Steam issues are being fixed. Thanks again for the great work.

[Fursphere]

I'm going to assume you don't support Windows 10 (Pro, 22H2) anymore, but in Beta 3 I'm seeing BigBox close (crash) after about 30 minutes of attract mode running, and i see this in the application logs:

Quote

Faulting application name: BigBox.exe, version: 13.25.0.3, time stamp: 0x68f20000
Faulting module name: ntdll.dll, version: 10.0.19041.6456, time stamp: 0x7ec9c15d
Exception code: 0xc0000374
Fault offset: 0x00000000000ff489
Faulting process id: 0x4364
Faulting application start time: 0x01dc686559cafa4e
Faulting application path: c:\launchbox\Core\BigBox.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: b1bcc452-4103-48b4-8f23-26ace07a54e1
Faulting package full name: 
Faulting package-relative application ID: 

Beta is running fine on my Windows 11 (Home / 25H2) machine.  

I'm getting ready to reload this machine with Windows 11, so this isn't an issue for me.  Just an FYI.   

Thanks.

[C-Beats]

10 hours ago, Fursphere said:

I'm going to assume you don't support Windows 10 (Pro, 22H2) anymore

I personally still run Win10 and have no desire to move to 11 so we definitely do our best to ensure it works. There are two error logs created when we crash, one simply states the app crashed and tells you what app and the other has the actual error. Looks like you grabbed the first, we'd need the second to be able to really nail down what is going on in your setup.

[salofan]

Unfortunately, as of this morning, LB will not start at all. Getting this weird error on startup:

Quote

The specified network resource or device is no longer available. : 'D:\SteamLibrary\steamapps\appmanifest_1003590.acf'.

App:     LaunchBox
Version: 13.25-beta-3
Theme:   NOT SET
Type:    System.IO.IOException
Site:    Int32 Read(System.Span`1[System.Byte])
Source:  System.Private.CoreLib

   at System.IO.Strategies.OSFileStreamStrategy.Read(Span`1 buffer)
   at System.IO.Strategies.BufferedFileStreamStrategy.ReadSpan(Span`1 destination, ArraySegment`1 arraySegment)
   at System.IO.Strategies.BufferedFileStreamStrategy.Read(Byte[] buffer, Int32 offset, Int32 count)
   at System.IO.StreamReader.ReadBuffer()
   at System.IO.StreamReader.ReadLine()
   at System.IO.File.ReadAllLines(String path, Encoding encoding)
   at Unbroken.LaunchBox.Windows.Integrations.Steam.GetInstalledAppIds()
   at RequesterTreeDic.RequestStaticCompressorStruct(RequesterTreeDic)
   at Unbroken.LaunchBox.Windows.Data.DataManager.ValidateCustomizableEnumeratorStack()
   at PoolProcessorRequester.RequestStaticCompressorStruct(Object, PoolProcessorRequester)
   at Unbroken.LaunchBox.Windows.Data.DataManager.DecodeViewerCalc(Boolean isvalue, Boolean isord)
   at AttributeEnumerator.RequestStaticCompressorStruct(Object, Boolean isvalue, Boolean isord, AttributeEnumerator)
   at Unbroken.LaunchBox.Windows.Data.DataManager..ctor(Boolean bare, Boolean settingsOnly)
   at Unbroken.LaunchBox.Windows.Desktop.App..ctor()
   at Unbroken.LaunchBox.Windows.Desktop.Program.Main(String[] args)

Recent Log:

   11:53:23 AM Exception

Was working fine until this morning. Not sure if this is a beta issue related to Steam or something else - I've never had LB log an error message like this on startup before.

[The Papaw]

On 12/7/2025 at 6:28 PM, MysterNybble said:

Improvement: Improved cloud sync accuracy

Has this "improvement" broke things with non-beta releases?

No longer syncing with v13.24. Now getting this: I can log into the db site without issues

I disconnect and reconnected, then I get this:

[salofan]

It actually looks like this is an issue with one of my SSDs where I keep my Steam games. So bigger issue for me, but not Launchbox. So disregard.