Investigation
List View Column Headers Missing After Restart
📌 Summary We’re aware of an issue where column headers in List View may appear blank after starting LaunchBox. This occurs if LaunchBox is closed while in List View. When reopening the application, the column headers at the top of the list may be empty, even though the rest of the view loads correctly. 🔎 How to Reproduce Switch LaunchBox to List View Close LaunchBox completely Reopen LaunchBox The column headers will appear blank. 🛠 Workaround Switch to Image View, then switch back to List View. This will refresh the view and restore the column headers. 🗓 Additional Notes This is a longstanding List View issue. While it does not impact core functionality, we understand it can be confusing or visually disruptive. We’re planning broader improvements to List View behaviour and performance, and this will be reviewed as part of that work.
AstroBob 8 days ago
Investigation
List View Column Headers Missing After Restart
📌 Summary We’re aware of an issue where column headers in List View may appear blank after starting LaunchBox. This occurs if LaunchBox is closed while in List View. When reopening the application, the column headers at the top of the list may be empty, even though the rest of the view loads correctly. 🔎 How to Reproduce Switch LaunchBox to List View Close LaunchBox completely Reopen LaunchBox The column headers will appear blank. 🛠 Workaround Switch to Image View, then switch back to List View. This will refresh the view and restore the column headers. 🗓 Additional Notes This is a longstanding List View issue. While it does not impact core functionality, we understand it can be confusing or visually disruptive. We’re planning broader improvements to List View behaviour and performance, and this will be reviewed as part of that work.
AstroBob 8 days ago
Completed
Section Sidebar Cannot Be Shown or Hidden
Status: Known Issue Affects: LaunchBox for Windows 13.25 Summary The section sidebar cannot be toggled on or off using the menu option or the Ctrl + S shortcut. Details In LaunchBox 13.25, the option to show or hide the section sidebar no longer responds when triggered via: The menu option The Ctrl + S keyboard shortcut As a result: Users who previously had the sidebar hidden are unable to turn it back on Users who always had the sidebar enabled may not notice the issue Other similar UI toggles (such as the Game Details pane) continue to work as expected The issue is reproducible on the 13.25 release and does not occur in 13.25 Beta 3. The root cause has been identified as an internal logic error introduced during code cleanup work prior to release. 🔧 Temporary Workaround (Advanced Users) If you are currently stuck without a sidebar, you can force it back on by manually editing the LaunchBox settings file. Close LaunchBox completely Navigate to your LaunchBox folder Open Settings.xml Locate the following line: false ensure it is set to true Save the file and relaunch LaunchBox ⚠️ Only edit this file if you’re comfortable making manual changes. We recommend backing up the file first. Next Steps The issue has already been fixed internally and is going through code review. The fix is planned to be included in the next hotfix or hotfix beta.
AstroBob About 1 month ago
Known Issue
Completed
Section Sidebar Cannot Be Shown or Hidden
Status: Known Issue Affects: LaunchBox for Windows 13.25 Summary The section sidebar cannot be toggled on or off using the menu option or the Ctrl + S shortcut. Details In LaunchBox 13.25, the option to show or hide the section sidebar no longer responds when triggered via: The menu option The Ctrl + S keyboard shortcut As a result: Users who previously had the sidebar hidden are unable to turn it back on Users who always had the sidebar enabled may not notice the issue Other similar UI toggles (such as the Game Details pane) continue to work as expected The issue is reproducible on the 13.25 release and does not occur in 13.25 Beta 3. The root cause has been identified as an internal logic error introduced during code cleanup work prior to release. 🔧 Temporary Workaround (Advanced Users) If you are currently stuck without a sidebar, you can force it back on by manually editing the LaunchBox settings file. Close LaunchBox completely Navigate to your LaunchBox folder Open Settings.xml Locate the following line: false ensure it is set to true Save the file and relaunch LaunchBox ⚠️ Only edit this file if you’re comfortable making manual changes. We recommend backing up the file first. Next Steps The issue has already been fixed internally and is going through code review. The fix is planned to be included in the next hotfix or hotfix beta.
AstroBob About 1 month ago
Known Issue
Completed
Big Box Platform Wheel Not Rendering Until Scrolling
Status: Known Issue Affects: Big Box, LaunchBox 13.25 Workaround: Scrolling forces the wheel to render Summary In some Big Box themes, the platform wheel may not appear when entering Platform View and only becomes visible after scrolling. Details This issue: Only affects older vertical coverflow style wheels Does not affect horizontal wheels Does not affect the newer styled coverflow wheels The issue occurs during initial view load and impacts how these legacy wheel elements initialise. Next Steps We’re actively testing a fix and expect this issue to be resolved alongside the background image fix in an upcoming hotfix.
AstroBob About 1 month ago
Known Issue
Completed
Big Box Platform Wheel Not Rendering Until Scrolling
Status: Known Issue Affects: Big Box, LaunchBox 13.25 Workaround: Scrolling forces the wheel to render Summary In some Big Box themes, the platform wheel may not appear when entering Platform View and only becomes visible after scrolling. Details This issue: Only affects older vertical coverflow style wheels Does not affect horizontal wheels Does not affect the newer styled coverflow wheels The issue occurs during initial view load and impacts how these legacy wheel elements initialise. Next Steps We’re actively testing a fix and expect this issue to be resolved alongside the background image fix in an upcoming hotfix.
AstroBob About 1 month ago
Known Issue
Completed
Big Box Background Images Not Appearing in Platform View
Status: Known Issue Affects: Big Box, LaunchBox 13.25 Summary In Platform View, some Big Box themes may display no background image where one is expected. Details This issue affects themes that rely on a specific background element used in Platform View. That element supports multiple media priorities depending on user settings, including: Platform Theme Videos Random Game Videos Platform Background Fanart images Random Game Background Fanart images In LaunchBox 13.25, this element may fail to display background images, resulting in a black background. Important notes: Background videos still play correctly Background images do not render Modern themes can still be affected when using this element, but are less impacted if they use multiple layered backgrounds with fallbacks Older themes that rely solely on this single background element are impacted the most Next Steps A fix has been identified and is currently being tested for inclusion in an upcoming hotfix.
AstroBob About 1 month ago
Known Issue
Completed
Big Box Background Images Not Appearing in Platform View
Status: Known Issue Affects: Big Box, LaunchBox 13.25 Summary In Platform View, some Big Box themes may display no background image where one is expected. Details This issue affects themes that rely on a specific background element used in Platform View. That element supports multiple media priorities depending on user settings, including: Platform Theme Videos Random Game Videos Platform Background Fanart images Random Game Background Fanart images In LaunchBox 13.25, this element may fail to display background images, resulting in a black background. Important notes: Background videos still play correctly Background images do not render Modern themes can still be affected when using this element, but are less impacted if they use multiple layered backgrounds with fallbacks Older themes that rely solely on this single background element are impacted the most Next Steps A fix has been identified and is currently being tested for inclusion in an upcoming hotfix.
AstroBob About 1 month ago
Known Issue
Planned
Steam Trailers Unavailable Due to New Steam API Changes
Status: Known Issue Affects: LaunchBox 13.25 Workaround: None currently Summary Steam trailers are currently unavailable to download due to new changes on Steam’s side, separate from the Steam trailer issue addressed earlier in the 13.25 beta cycle. Details Earlier in 2025, Steam made changes to their trailer API which caused Steam trailers to fail in LaunchBox. That issue was addressed and fixed during the 13.25 beta cycle (around Beta 3). However, since then, Steam has made additional sweeping changes, fully removing access to direct trailer video files and replacing them with streaming only formats (such as DASH, HLS, and microtrailers). As a result: LaunchBox no longer detects any downloadable Steam trailers Steam Trailers may not appear as an available media type Bulk imports may still show the option, but no trailers will be downloaded This is not a regression caused by new LaunchBox code, but the result of further changes introduced by Steam after beta testing concluded. Next Steps Restoring Steam trailer support will require a more significant redesign of how LaunchBox retrieves and processes Steam trailers. This will be addressed in a future update rather than a hotfix.
AstroBob About 1 month ago
Known Issue
Planned
Steam Trailers Unavailable Due to New Steam API Changes
Status: Known Issue Affects: LaunchBox 13.25 Workaround: None currently Summary Steam trailers are currently unavailable to download due to new changes on Steam’s side, separate from the Steam trailer issue addressed earlier in the 13.25 beta cycle. Details Earlier in 2025, Steam made changes to their trailer API which caused Steam trailers to fail in LaunchBox. That issue was addressed and fixed during the 13.25 beta cycle (around Beta 3). However, since then, Steam has made additional sweeping changes, fully removing access to direct trailer video files and replacing them with streaming only formats (such as DASH, HLS, and microtrailers). As a result: LaunchBox no longer detects any downloadable Steam trailers Steam Trailers may not appear as an available media type Bulk imports may still show the option, but no trailers will be downloaded This is not a regression caused by new LaunchBox code, but the result of further changes introduced by Steam after beta testing concluded. Next Steps Restoring Steam trailer support will require a more significant redesign of how LaunchBox retrieves and processes Steam trailers. This will be addressed in a future update rather than a hotfix.
AstroBob About 1 month ago
Known Issue
Completed
Skip Mechanical Games Appears Twice on MAME Import ROMs Wizard
Extremely minor issue while importing MAME roms. The “Skip mechanical games” checkbox appears twice.
VodkaParalyzer 2 months ago
Known Issue
Completed
Skip Mechanical Games Appears Twice on MAME Import ROMs Wizard
Extremely minor issue while importing MAME roms. The “Skip mechanical games” checkbox appears twice.
VodkaParalyzer 2 months ago
Known Issue
Planned
Known Issue: Big Box Startup Videos Not Playing Reliably
Overview Some users are experiencing an issue where Big Box startup videos do not play consistently, or are skipped entirely, when launching Big Box. Reports began around LaunchBox 13.19–13.20 and continue through recent builds. Symptoms You may see one or more of the following: Startup video plays only on first launch, then gets skipped on subsequent launches Restarting Windows may allow the video to play once, then it stops again Startup video plays intermittently (for example, around 1 in 3 launches) Big Box skips the splash screen, but the startup video also fails to play Occurs on fresh installs as well as upgraded builds Reproduced across both low end and high end systems Happens with both FFMPEG and Windows Media Player Affected Versions Reported from approximately 13.19–13.20 onward Confirmed by users in 13.24 Reproduced internally in 13.25 beta Expected Behavior When a startup video is present in LaunchBox/Videos/Startup, Big Box should: Reliably play the startup video on every launch Allow users to skip the video via controller, keyboard, or mouse Transition smoothly into Big Box after playback or skip What This Is Not This issue is not typically caused by: Incorrect folder structure Correct path is LaunchBox/Videos/Startup A specific video file, format, or number of videos System performance alone Current Understanding Based on community reports and internal investigation: The issue is real but highly inconsistent, which made it difficult to diagnose The problem appears tied to startup video changes introduced when Big Box moved away from the legacy VLC based playback system Startup video playback now relies on FFMPEG or Windows Media Player, depending on user settings The behaviour suggests a timing or initialization issue in certain Windows or machine environments What We’re Doing We’ve now identified machines internally that reproduce the issue The startup video system has been rebuilt from the ground up in a test branch Early testing shows strong improvements, including: Startup videos playing reliably across repeated launches Proper skipping via controller, keyboard, or mouse Improved transitions into Big Box during or after playback What Happens Next Continued testing across a wider range of systems and configurations Once validated, the fix will be included in a future LaunchBox update Progress updates will be shared as testing continues How You Can Help If you’re affected and willing to share details, the following are especially helpful: Windows version CPU and GPU details, integrated vs dedicated How Big Box is launched Playback engine selected, FFMPEG or Windows Media Player Startup video file details and how many videos are present Thank you for your patience and for the detailed reports. Your feedback directly helped us identify and rebuild this system.
AstroBob 2 months ago
Known Issue
Planned
Known Issue: Big Box Startup Videos Not Playing Reliably
Overview Some users are experiencing an issue where Big Box startup videos do not play consistently, or are skipped entirely, when launching Big Box. Reports began around LaunchBox 13.19–13.20 and continue through recent builds. Symptoms You may see one or more of the following: Startup video plays only on first launch, then gets skipped on subsequent launches Restarting Windows may allow the video to play once, then it stops again Startup video plays intermittently (for example, around 1 in 3 launches) Big Box skips the splash screen, but the startup video also fails to play Occurs on fresh installs as well as upgraded builds Reproduced across both low end and high end systems Happens with both FFMPEG and Windows Media Player Affected Versions Reported from approximately 13.19–13.20 onward Confirmed by users in 13.24 Reproduced internally in 13.25 beta Expected Behavior When a startup video is present in LaunchBox/Videos/Startup, Big Box should: Reliably play the startup video on every launch Allow users to skip the video via controller, keyboard, or mouse Transition smoothly into Big Box after playback or skip What This Is Not This issue is not typically caused by: Incorrect folder structure Correct path is LaunchBox/Videos/Startup A specific video file, format, or number of videos System performance alone Current Understanding Based on community reports and internal investigation: The issue is real but highly inconsistent, which made it difficult to diagnose The problem appears tied to startup video changes introduced when Big Box moved away from the legacy VLC based playback system Startup video playback now relies on FFMPEG or Windows Media Player, depending on user settings The behaviour suggests a timing or initialization issue in certain Windows or machine environments What We’re Doing We’ve now identified machines internally that reproduce the issue The startup video system has been rebuilt from the ground up in a test branch Early testing shows strong improvements, including: Startup videos playing reliably across repeated launches Proper skipping via controller, keyboard, or mouse Improved transitions into Big Box during or after playback What Happens Next Continued testing across a wider range of systems and configurations Once validated, the fix will be included in a future LaunchBox update Progress updates will be shared as testing continues How You Can Help If you’re affected and willing to share details, the following are especially helpful: Windows version CPU and GPU details, integrated vs dedicated How Big Box is launched Playback engine selected, FFMPEG or Windows Media Player Startup video file details and how many videos are present Thank you for your patience and for the detailed reports. Your feedback directly helped us identify and rebuild this system.
AstroBob 2 months ago
Known Issue
Completed
LaunchBox Error When Attempting To Download Video Media From Steam
Summary Users may experience a crash with the error: “Object reference not set to an instance of an object.” App: LaunchBox Version: xx.xx Theme: Default Plus Type: System.NullReferenceException Site: System.String GetTrailerVideoUrl(Unbroken.LaunchBox.Windows.SteamGame) Source: Unbroken.LaunchBox.Windows This occurs when LaunchBox attempts to fetch trailer videos from Steam, triggered by specific actions like editing game metadata or importing Steam storefront media. Cause We identified a recent change with Steam in the way that their trailer videos are served via their backend. LaunchBox’s current video query system for Steam games is no longer compatible, resulting in a NullReferenceException when a trailer is requested. Symptoms Crash when selecting Media > Videos > Download Media while editing a PC game Crash during Download Metadata & Media Wizard if “Steam Trailer Video” is selected Crash during Tools > Scan for Storefront Games if trailers are prioritized Crash on startup if Automatic Storefront Imports is enabled and Steam videos are requested Temporary Workarounds To avoid triggering the crash: ✅ Disable Automatic Storefront Imports under Tools > Manage > Storefronts ✅ Avoid selecting Steam Trailer Video when using the Media Import Wizard ✅ Do not manually open Download Media > Videos for Steam or PC games ✅ If scanning for storefront games, temporarily change media priorities to exclude trailer videos Status ⚙️ Under Investigation — We’ve confirmed the root issue is due to a Steam-side change and are actively working on an update to restore compatibility. We’ll update this post as we have more information
AstroBob 3 months ago
Known Issue
Completed
LaunchBox Error When Attempting To Download Video Media From Steam
Summary Users may experience a crash with the error: “Object reference not set to an instance of an object.” App: LaunchBox Version: xx.xx Theme: Default Plus Type: System.NullReferenceException Site: System.String GetTrailerVideoUrl(Unbroken.LaunchBox.Windows.SteamGame) Source: Unbroken.LaunchBox.Windows This occurs when LaunchBox attempts to fetch trailer videos from Steam, triggered by specific actions like editing game metadata or importing Steam storefront media. Cause We identified a recent change with Steam in the way that their trailer videos are served via their backend. LaunchBox’s current video query system for Steam games is no longer compatible, resulting in a NullReferenceException when a trailer is requested. Symptoms Crash when selecting Media > Videos > Download Media while editing a PC game Crash during Download Metadata & Media Wizard if “Steam Trailer Video” is selected Crash during Tools > Scan for Storefront Games if trailers are prioritized Crash on startup if Automatic Storefront Imports is enabled and Steam videos are requested Temporary Workarounds To avoid triggering the crash: ✅ Disable Automatic Storefront Imports under Tools > Manage > Storefronts ✅ Avoid selecting Steam Trailer Video when using the Media Import Wizard ✅ Do not manually open Download Media > Videos for Steam or PC games ✅ If scanning for storefront games, temporarily change media priorities to exclude trailer videos Status ⚙️ Under Investigation — We’ve confirmed the root issue is due to a Steam-side change and are actively working on an update to restore compatibility. We’ll update this post as we have more information
AstroBob 3 months ago
Known Issue
Planned
Date formatting crash with Arabic regional settings on Windows 11
Summary LaunchBox throws a date formatting error when Windows is using Arabic regional settings with the Um Al Qura calendar. The Um Al Qura calendar only supports dates between 30 April 1900 and 16 November 2077 Gregorian. When LaunchBox formats a date outside that supported range, the app errors and certain views crash. Affected versions Reported on 13.22, user also notes behavior change on Windows 11 compared to Windows 10. Environment Windows 11 with Arabic language and Arabic regional format, Um Al Qura calendar active. Steps to reproduce Set Windows 11 display language or regional format to Arabic, which enables the Um Al Qura calendar Launch LaunchBox or Big Box Navigate to a game view that formats or displays dates, for example Game Details Observe the error dialog and crash Observed behavior Error appears frequently during normal operations. Example message Specified time is not supported in this calendar. It should be between 04/30/1900 00:00:00 and 11/16/2077 23:59:59, inclusive. Actual value was 451541088000000000. Stack shows System.Globalization.UmAlQuraCalendar.CheckTicksRange, called from DateTime.ToShortDateString, then GameDetailsViewModel. Expected behavior LaunchBox should format and display dates correctly regardless of Windows calendar choice. If a date falls outside the active calendar range, LaunchBox should clamp or fall back to Gregorian formatting rather than crashing. Notes User reports the issue disappears when switching Windows to English, which moves the system to a Gregorian calendar. This suggests LaunchBox is calling ToShortDateString under the current culture without guarding for calendars with smaller supported ranges. Possible workaround for users Temporarily set Windows Regional format to English United States or English United Kingdom to use the Gregorian calendar, then relaunch LaunchBox. This is not ideal for Arabic users and is shared only as a temporary mitigation. Relevant log excerpt System.ArgumentOutOfRangeException at System.Globalization.UmAlQuraCalendar.CheckTicksRange(Int64 ticks) at System.DateTimeFormat.Format(...) at System.DateTime.ToShortDateString() at Unbroken.LaunchBox.Windows.Desktop.ViewModels.GameDetailsViewModel.BuildResolver(...) ... Proposed direction • Audit all date formatting paths that rely on current culture • For calendars with limited ranges such as Um Al Qura, either clamp out of range values to the calendar minimum or maximum, or force a culture with Gregorian calendar for formatting only, while keeping the user’s language for text • Add defensive checks around date fields that may be null, default, or sentinel values outside 1900 to 2077 Gregorian
AstroBob 5 months ago
Known Issue
Planned
Date formatting crash with Arabic regional settings on Windows 11
Summary LaunchBox throws a date formatting error when Windows is using Arabic regional settings with the Um Al Qura calendar. The Um Al Qura calendar only supports dates between 30 April 1900 and 16 November 2077 Gregorian. When LaunchBox formats a date outside that supported range, the app errors and certain views crash. Affected versions Reported on 13.22, user also notes behavior change on Windows 11 compared to Windows 10. Environment Windows 11 with Arabic language and Arabic regional format, Um Al Qura calendar active. Steps to reproduce Set Windows 11 display language or regional format to Arabic, which enables the Um Al Qura calendar Launch LaunchBox or Big Box Navigate to a game view that formats or displays dates, for example Game Details Observe the error dialog and crash Observed behavior Error appears frequently during normal operations. Example message Specified time is not supported in this calendar. It should be between 04/30/1900 00:00:00 and 11/16/2077 23:59:59, inclusive. Actual value was 451541088000000000. Stack shows System.Globalization.UmAlQuraCalendar.CheckTicksRange, called from DateTime.ToShortDateString, then GameDetailsViewModel. Expected behavior LaunchBox should format and display dates correctly regardless of Windows calendar choice. If a date falls outside the active calendar range, LaunchBox should clamp or fall back to Gregorian formatting rather than crashing. Notes User reports the issue disappears when switching Windows to English, which moves the system to a Gregorian calendar. This suggests LaunchBox is calling ToShortDateString under the current culture without guarding for calendars with smaller supported ranges. Possible workaround for users Temporarily set Windows Regional format to English United States or English United Kingdom to use the Gregorian calendar, then relaunch LaunchBox. This is not ideal for Arabic users and is shared only as a temporary mitigation. Relevant log excerpt System.ArgumentOutOfRangeException at System.Globalization.UmAlQuraCalendar.CheckTicksRange(Int64 ticks) at System.DateTimeFormat.Format(...) at System.DateTime.ToShortDateString() at Unbroken.LaunchBox.Windows.Desktop.ViewModels.GameDetailsViewModel.BuildResolver(...) ... Proposed direction • Audit all date formatting paths that rely on current culture • For calendars with limited ranges such as Um Al Qura, either clamp out of range values to the calendar minimum or maximum, or force a culture with Gregorian calendar for formatting only, while keeping the user’s language for text • Add defensive checks around date fields that may be null, default, or sentinel values outside 1900 to 2077 Gregorian
AstroBob 5 months ago
Known Issue
Completed
Microsoft Store Login Does Not Complete in Manage Storefront
Summary: On LaunchBox 13.24, logging into the Microsoft Store via the Manage Storefronts window does not complete. The login flow starts, but the UI does not update to reflect a successful login. Steps to Reproduce: Open Tools > Manage Storefronts. Select Xbox / Microsoft Store and click Log In. Go through the Microsoft login process. After finishing, the button still reads Log In instead of showing a logged-in state. Clicking the button again briefly opens a login window that closes immediately, but the status does not change. Observed Behavior: The login flow runs, but the button remains at Log In. Re-clicking the button flashes a window that closes instantly. Storefront never shows as authenticated. Expected Behavior: After a successful login, the UI should update to reflect the account is logged in. Impact: Users cannot connect their Microsoft/Xbox Store accounts to LaunchBox, preventing storefront integration.
AstroBob 5 months ago
Known Issue
Completed
Microsoft Store Login Does Not Complete in Manage Storefront
Summary: On LaunchBox 13.24, logging into the Microsoft Store via the Manage Storefronts window does not complete. The login flow starts, but the UI does not update to reflect a successful login. Steps to Reproduce: Open Tools > Manage Storefronts. Select Xbox / Microsoft Store and click Log In. Go through the Microsoft login process. After finishing, the button still reads Log In instead of showing a logged-in state. Clicking the button again briefly opens a login window that closes immediately, but the status does not change. Observed Behavior: The login flow runs, but the button remains at Log In. Re-clicking the button flashes a window that closes instantly. Storefront never shows as authenticated. Expected Behavior: After a successful login, the UI should update to reflect the account is logged in. Impact: Users cannot connect their Microsoft/Xbox Store accounts to LaunchBox, preventing storefront integration.
AstroBob 5 months ago
Known Issue
Completed
Screensaver Skips a Game During Transitions
Summary: In LaunchBox 13.24, the screensaver briefly shows an additional game during transitions. It consistently skips one game before moving on to the next, causing a 1-second flash of an unrelated game before the intended one appears. Steps to Reproduce: Enable the Screensaver (tested with Ambiance and Gallery themes). Set Min / Max Time Between Games to 30 seconds (other values tested, no effect). Let the screensaver run. When transitioning between games, note the 1-second jump to an unintended game before the next one displays. Observed Behavior: Screensaver always flashes a different game for ~1 second during each transition. Issue occurs on multiple builds (main install and test install of 13.24). Reproducible across multiple themes. Expected Behavior: Screensaver should transition smoothly from one game to the next without flashing an unrelated game.
AstroBob 5 months ago
Known Issue
Completed
Screensaver Skips a Game During Transitions
Summary: In LaunchBox 13.24, the screensaver briefly shows an additional game during transitions. It consistently skips one game before moving on to the next, causing a 1-second flash of an unrelated game before the intended one appears. Steps to Reproduce: Enable the Screensaver (tested with Ambiance and Gallery themes). Set Min / Max Time Between Games to 30 seconds (other values tested, no effect). Let the screensaver run. When transitioning between games, note the 1-second jump to an unintended game before the next one displays. Observed Behavior: Screensaver always flashes a different game for ~1 second during each transition. Issue occurs on multiple builds (main install and test install of 13.24). Reproducible across multiple themes. Expected Behavior: Screensaver should transition smoothly from one game to the next without flashing an unrelated game.
AstroBob 5 months ago
Known Issue
Completed
Hidden Games Appear in Some Big Box Discovery Center Sections
Summary: Hidden games in LaunchBox are still being shown in certain sections of the Big Box Discovery Center, even though they are correctly hidden elsewhere. Details: Sections like “Because you recently played [Game]” may display games that have been marked as hidden in LaunchBox. Other Discovery Center sections appear to respect the hidden status as expected. Impact: This can lead to cluttered or misleading recommendations, particularly for users who intentionally hide unwanted games.
AstroBob 8 months ago
Known Issue
Completed
Hidden Games Appear in Some Big Box Discovery Center Sections
Summary: Hidden games in LaunchBox are still being shown in certain sections of the Big Box Discovery Center, even though they are correctly hidden elsewhere. Details: Sections like “Because you recently played [Game]” may display games that have been marked as hidden in LaunchBox. Other Discovery Center sections appear to respect the hidden status as expected. Impact: This can lead to cluttered or misleading recommendations, particularly for users who intentionally hide unwanted games.
AstroBob 8 months ago
Known Issue
Investigation
Crash When Editing Platform with Missing Game Directory
Summary: LaunchBox may crash when attempting to edit a platform if its associated games directory is not available (e.g., located on an unplugged external drive). Steps to Reproduce: Set a platform’s games directory to a path on an external or removable drive. Unplug or unmount the drive. Right-click the platform in the sidebar and select Edit. LaunchBox throws an error and crashes. Error Example: “A directory could not be created: [path to game]” “Could not find part of the path ’[path to game]’.” Impact: Users cannot edit platform metadata (e.g., name, year, notes) unless all referenced directories are mounted and accessible. This behavior blocks even non-directory-related edits and makes it difficult to correct or update platform paths. 🛠 Status: Known Issue – Under Investigation TWe’re aware of this issue and have identified that it stems from a lower-level part of the code that attempts to access game directories during platform edits. While the ideal behavior would be to gracefully handle missing paths, addressing this would involve significant changes with some risk. At this time, it’s under investigation for a possible future fix, but due to complexity and limited impact for most users, it hasn’t been prioritized yet.
AstroBob 8 months ago
Known Issue
Investigation
Crash When Editing Platform with Missing Game Directory
Summary: LaunchBox may crash when attempting to edit a platform if its associated games directory is not available (e.g., located on an unplugged external drive). Steps to Reproduce: Set a platform’s games directory to a path on an external or removable drive. Unplug or unmount the drive. Right-click the platform in the sidebar and select Edit. LaunchBox throws an error and crashes. Error Example: “A directory could not be created: [path to game]” “Could not find part of the path ’[path to game]’.” Impact: Users cannot edit platform metadata (e.g., name, year, notes) unless all referenced directories are mounted and accessible. This behavior blocks even non-directory-related edits and makes it difficult to correct or update platform paths. 🛠 Status: Known Issue – Under Investigation TWe’re aware of this issue and have identified that it stems from a lower-level part of the code that attempts to access game directories during platform edits. While the ideal behavior would be to gracefully handle missing paths, addressing this would involve significant changes with some risk. At this time, it’s under investigation for a possible future fix, but due to complexity and limited impact for most users, it hasn’t been prioritized yet.
AstroBob 8 months ago
Known Issue
Completed
“Games Completed” Binding Not Showing Accurate Count
🔍 Description: Following changes introduced in LaunchBox 13.22, the Games Completed binding no longer reflects accurate data. It’s meant to display the total number of completed games (e.g., Games Completed: 650), but it’s currently not linked to the new progress tracking system. 💡 Fix Required: Update the binding to reference the new Progress Status field introduced in 13.22 Ensure the correct total is displayed wherever this binding is used 📘 Notes: This issue stems from the transition to the new progress tracking system in 13.22. The binding is still used in several themes and needs to be updated to reflect the new logic.
AstroBob 8 months ago
Known Issue
Completed
“Games Completed” Binding Not Showing Accurate Count
🔍 Description: Following changes introduced in LaunchBox 13.22, the Games Completed binding no longer reflects accurate data. It’s meant to display the total number of completed games (e.g., Games Completed: 650), but it’s currently not linked to the new progress tracking system. 💡 Fix Required: Update the binding to reference the new Progress Status field introduced in 13.22 Ensure the correct total is displayed wherever this binding is used 📘 Notes: This issue stems from the transition to the new progress tracking system in 13.22. The binding is still used in several themes and needs to be updated to reflect the new logic.
AstroBob 8 months ago
Known Issue
Completed
“Completed” Icon Always Showing in Old Default Theme
📝 Description: In 13.22, some users have reported that all games appear marked as “Completed” in Big Box when using the Old Default theme or older custom themes. This is due to outdated controls that weren’t updated to support the new progress system. 💥 Impact: Affects users using the Old Default Big Box theme or themes built on older controls Visual issue only – your game data is not being changed The “Completed” icon may always appear, even for games that are not completed 🔍 Cause: Legacy theme logic includes an old C# binding that shows the “Completed” graphic by default, unless specifically told not to. This wasn’t updated during recent changes. 🛠️ Status: The issue has been identified and is on our internal list to be fixed in a future update ✅ 🚧 Workaround: We recommend switching to a modern or officially supported theme to avoid this behavior for now.
AstroBob 8 months ago
Known Issue
Completed
“Completed” Icon Always Showing in Old Default Theme
📝 Description: In 13.22, some users have reported that all games appear marked as “Completed” in Big Box when using the Old Default theme or older custom themes. This is due to outdated controls that weren’t updated to support the new progress system. 💥 Impact: Affects users using the Old Default Big Box theme or themes built on older controls Visual issue only – your game data is not being changed The “Completed” icon may always appear, even for games that are not completed 🔍 Cause: Legacy theme logic includes an old C# binding that shows the “Completed” graphic by default, unless specifically told not to. This wasn’t updated during recent changes. 🛠️ Status: The issue has been identified and is on our internal list to be fixed in a future update ✅ 🚧 Workaround: We recommend switching to a modern or officially supported theme to avoid this behavior for now.
AstroBob 8 months ago
Known Issue
Default collection missing from “Add to Collection” popup on Game's DB game profile pages
Description: When viewing a game’s profile page on the Games Database website, clicking the “Add to Collection” button does not include the default collection in the list of options. Only user-created collections, the option to create a new collection, and a link to manage collections are shown. In contrast, when using the ”+” shortcut from game search results, the default collection does appear as expected. Steps to Reproduce: Visit a game’s profile page on the Games DB website. Click the “Add to Collection” button. Observe the list of available collections. Search for a game using the search bar. Click the “+” icon beside a result and observe the list. Expected Result: The default collection should appear in both collection popups. Actual Result: The default collection is only shown in the popup when adding from search results, not from the game profile page. Additional Notes: The game profile page uses a different framework/technology than other parts of the site, which may explain the inconsistency.
AstroBob 8 months ago
Known Issue
Default collection missing from “Add to Collection” popup on Game's DB game profile pages
Description: When viewing a game’s profile page on the Games Database website, clicking the “Add to Collection” button does not include the default collection in the list of options. Only user-created collections, the option to create a new collection, and a link to manage collections are shown. In contrast, when using the ”+” shortcut from game search results, the default collection does appear as expected. Steps to Reproduce: Visit a game’s profile page on the Games DB website. Click the “Add to Collection” button. Observe the list of available collections. Search for a game using the search bar. Click the “+” icon beside a result and observe the list. Expected Result: The default collection should appear in both collection popups. Actual Result: The default collection is only shown in the popup when adding from search results, not from the game profile page. Additional Notes: The game profile page uses a different framework/technology than other parts of the site, which may explain the inconsistency.
AstroBob 8 months ago
Known Issue
No Action Required
The data is NULL at ordinal 1. This method can't be called on NULL values.
The data is NULL at ordinal 1. This method can't be called on NULL values. Check using IsDBNull before calling. Are you running into this error? Run this to get rid of it: Tools > Download > Force Update Games Database Metadata...
Brian Faeran 9 months ago
Known Issue
No Action Required
The data is NULL at ordinal 1. This method can't be called on NULL values.
The data is NULL at ordinal 1. This method can't be called on NULL values. Check using IsDBNull before calling. Are you running into this error? Run this to get rid of it: Tools > Download > Force Update Games Database Metadata...
Brian Faeran 9 months ago
Known Issue
No Action Required
UCEERR_RENDERTHREADFAILURE
Why is this happening? This error is usually caused by an issue with your video card (graphics) drivers or Windows itself. The app relies on your graphics card to help draw the interface quickly and smoothly — but if your drivers are out of date, corrupted, or something goes wrong during startup, it can cause the graphics system to crash behind the scenes, leading to this error. What can I do about this? Update your video card drivers Go to your video card manufacturer’s website (like NVIDIA, AMD, or Intel) and download the latest drivers. This fixes the issue in most cases. Run Windows Update Sometimes this kind of issue is fixed by Microsoft in a Windows update. Make sure you're fully up to date. Restart your PC It sounds basic, but if something weird happened during startup, a reboot can reset the graphics system. The Error UCEERR_RENDERTHREADFAILURE (0x88980406) App: LaunchBox Version: 13.20 Theme: Omni Type: System.Runtime.InteropServices.COMException Site: Void SyncFlush() Source: PresentationCore at System.Windows.Media.Composition.DUCE.Channel.SyncFlush() at System.Windows.Interop.HwndTarget.UpdateWindowSettings(Boolean enableRenderTarget, Nullable`1 channelSet) at System.Windows.Interop.HwndTarget.UpdateWindowPos(IntPtr lParam) at System.Windows.Interop.HwndTarget.HandleMessage(WindowMessage msg, IntPtr wparam, IntPtr lparam) at System.Windows.Interop.HwndSource.HwndTargetFilterMessage(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) Recent Log: 9:03:11 PM Exception
Brian Faeran 9 months ago
Known Issue
No Action Required
UCEERR_RENDERTHREADFAILURE
Why is this happening? This error is usually caused by an issue with your video card (graphics) drivers or Windows itself. The app relies on your graphics card to help draw the interface quickly and smoothly — but if your drivers are out of date, corrupted, or something goes wrong during startup, it can cause the graphics system to crash behind the scenes, leading to this error. What can I do about this? Update your video card drivers Go to your video card manufacturer’s website (like NVIDIA, AMD, or Intel) and download the latest drivers. This fixes the issue in most cases. Run Windows Update Sometimes this kind of issue is fixed by Microsoft in a Windows update. Make sure you're fully up to date. Restart your PC It sounds basic, but if something weird happened during startup, a reboot can reset the graphics system. The Error UCEERR_RENDERTHREADFAILURE (0x88980406) App: LaunchBox Version: 13.20 Theme: Omni Type: System.Runtime.InteropServices.COMException Site: Void SyncFlush() Source: PresentationCore at System.Windows.Media.Composition.DUCE.Channel.SyncFlush() at System.Windows.Interop.HwndTarget.UpdateWindowSettings(Boolean enableRenderTarget, Nullable`1 channelSet) at System.Windows.Interop.HwndTarget.UpdateWindowPos(IntPtr lParam) at System.Windows.Interop.HwndTarget.HandleMessage(WindowMessage msg, IntPtr wparam, IntPtr lparam) at System.Windows.Interop.HwndSource.HwndTargetFilterMessage(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) Recent Log: 9:03:11 PM Exception
Brian Faeran 9 months ago
Known Issue
Completed
EA Importer Not Working
Issue: As of 12/05/25 the EA platform importer is currently non-functional due to EA shutting down their old API. Cause: EA has discontinued support for the API that LaunchBox previously relied on, breaking the importer. Status: We’re actively working on a workaround using an alternative method, which will be included in the next beta and upcoming release. Since EA doesn’t offer a public API, the fix will be a bit of a workaround. Workaround: None currently available. Stay tuned for updates in the next beta.
AstroBob 10 months ago
Known Issue
Completed
EA Importer Not Working
Issue: As of 12/05/25 the EA platform importer is currently non-functional due to EA shutting down their old API. Cause: EA has discontinued support for the API that LaunchBox previously relied on, breaking the importer. Status: We’re actively working on a workaround using an alternative method, which will be included in the next beta and upcoming release. Since EA doesn’t offer a public API, the fix will be a bit of a workaround. Workaround: None currently available. Stay tuned for updates in the next beta.
AstroBob 10 months ago
Known Issue
Investigation
"Out of Memory" error after resuming from hibernation in LaunchBox or Big Box
📝 Description Some users running LaunchBox 13.21 on Windows 11 may encounter an “Out of Memory” error after waking their PC from hibernation or hybrid sleep. This occurs particularly when 3D features are active in LaunchBox or Big Box. 🔧 Technical Details This issue stems from a known problem in the.NET 3D engine. During hibernation, Windows moves RAM to disk. When waking, LaunchBox or Big Box attempts to access 3D elements that were previously in memory. Because these resources are no longer where expected, the .NET engine misinterprets it as a memory failure, resulting in a crash. This only appears to affect Windows 11; Windows 10 users are not impacted. 🛠️ Workarounds 💡 For full details and step-by-step instructions, please refer to our full guide: 👉 @Out of Memory Error When Waking from Sleep As of 13.22, we’ve implemented a partial workaround in the software. When possible, LaunchBox attempts to detect upcoming hibernation and unload 3D content preemptively. This works best in: Big Box views using Wheels Game Discovery Center However, the timing isn’t always reliable — especially in LaunchBox and hybrid sleep scenarios. In the meantime, you can try the following user-level workarounds: In LaunchBox: Go to Tools > Options > Visuals > Game Details Uncheck “Show 3D Model” In Big Box: Switch to text-based views instead of Wheel views to reduce the likelihood of a crash. Disable hibernation or hybrid sleep entirely via your system power settings. This completely avoids the issue and is the most effective option until a .NET fix becomes available. 🚧 Status We’re monitoring Microsoft for updates and will adopt a patched .NET version as soon as one is available. A full fix is not currently possible on our end, but we’ve taken steps to minimize the impact in the meantime. Thanks for your patience and continued support!
AstroBob 10 months ago
Known Issue
Investigation
"Out of Memory" error after resuming from hibernation in LaunchBox or Big Box
📝 Description Some users running LaunchBox 13.21 on Windows 11 may encounter an “Out of Memory” error after waking their PC from hibernation or hybrid sleep. This occurs particularly when 3D features are active in LaunchBox or Big Box. 🔧 Technical Details This issue stems from a known problem in the.NET 3D engine. During hibernation, Windows moves RAM to disk. When waking, LaunchBox or Big Box attempts to access 3D elements that were previously in memory. Because these resources are no longer where expected, the .NET engine misinterprets it as a memory failure, resulting in a crash. This only appears to affect Windows 11; Windows 10 users are not impacted. 🛠️ Workarounds 💡 For full details and step-by-step instructions, please refer to our full guide: 👉 @Out of Memory Error When Waking from Sleep As of 13.22, we’ve implemented a partial workaround in the software. When possible, LaunchBox attempts to detect upcoming hibernation and unload 3D content preemptively. This works best in: Big Box views using Wheels Game Discovery Center However, the timing isn’t always reliable — especially in LaunchBox and hybrid sleep scenarios. In the meantime, you can try the following user-level workarounds: In LaunchBox: Go to Tools > Options > Visuals > Game Details Uncheck “Show 3D Model” In Big Box: Switch to text-based views instead of Wheel views to reduce the likelihood of a crash. Disable hibernation or hybrid sleep entirely via your system power settings. This completely avoids the issue and is the most effective option until a .NET fix becomes available. 🚧 Status We’re monitoring Microsoft for updates and will adopt a patched .NET version as soon as one is available. A full fix is not currently possible on our end, but we’ve taken steps to minimize the impact in the meantime. Thanks for your patience and continued support!
AstroBob 10 months ago
Known Issue