If you’ve encountered the “Could not find file” error while using LaunchBox, you’re not alone. The error usually appears when LaunchBox attempts to access an image file that has become corrupted or is missing entirely.

Here’s an example of what the full error could look like

Could not find file 'LaunchBox\Images\Sony Playstation\Box - Full\Disney_s 102 Dalmatians_ Puppies to the Rescue-02.png'. 

App: LaunchBox 
Version: 13.19 
Theme: Default 
Type: System.IO.FileNotFoundException 
Site: Microsoft.Win32.SafeHandles.SafeFileHandle CreateFile(System.String, System.IO.FileMode, System.IO.FileAccess, System.IO.FileShare, System.IO.FileOptions) Source: System.Private.CoreLib at Microsoft.Win32.SafeHandles.SafeFileHandle.CreateFile(String fullPath, FileMode mode, FileAccess access, FileShare share, FileOptions options) at Microsoft.Win32.SafeHandles.SafeFileHandle.Open(String fullPath, FileMode mode, FileAccess access, FileShare share, FileOptions options, Int64 preallocationSize, Nullable1 unixCreateMode) at System.IO.File.ReadAllBytes(String path) at Unbroken.LaunchBox.Windows.Data.Game.<>c.EnablePrincipalComposer(Object) at Unbroken.LaunchBox.Windows.Data.Game.<>c.RegisterInvalidMerchant(String path) at Unbroken.LaunchBox.Windows.Data.Game.GetImageChecksums(String imageType) at ServerProxyInvocation.RemoveDrivenField(Object, String imageType, ServerProxyInvocation) at Unbroken.LaunchBox.Windows.Processes.BulkImageDownloader.ManageInvalidRegistry(Object info) at Unbroken.BulkDownloader1.CustomizeStatementPrinter(WebClient item) at Unbroken.BulkDownloader1.ConnectStatementPrinter(Object spec, AsyncCompletedEventArgs col) at System.Threading.QueueUserWorkItemCallback1.Execute() at System.Threading.ThreadPoolWorkQueue.Dispatch() at System.Threading.PortableThreadPool.WorkerThread.WorkerThreadStart() Recent Log: 10:23:30 AM Exception

What Causes This Error?

From past reports and discussions, the primary cause of this issue appears to be corrupt image files. While the file may technically exist, it might be damaged, missing metadata, or have broken headers, which makes it unreadable by .NET. Some image files might still display fine in other applications, but LaunchBox struggles to process them, leading to this error.

Additionally, many users experiencing this issue seem to be using third-party image packs rather than sourcing artwork from LaunchBox or EmuMovies. If multiple users encounter the same issue, it’s likely that a bad image has been distributed in a popular community image pack.

How to Fix It

The solution is usually simple: delete the problematic image file. Here’s how to identify and resolve the issue:

1. Check the Error Message – The error will specify the exact file path and image name that is causing the issue. Usually, this is noted at the top of the error.

2. Locate the Image – Navigate to the file’s location on your system.

3. Delete or Replace the File – If the file is corrupted, remove it and try redownloading it from a reliable source (LaunchBox or EmuMovies).

4. Restart LaunchBox – Once the corrupted file is removed, LaunchBox should function without the error.

Preventing This Issue in the Future

• Use Trusted Sources – Stick to LaunchBox’s built-in image downloader or EmuMovies instead of relying on unofficial image packs.

• Verify Image Integrity – If you’re sourcing images manually, check that they open correctly in multiple image viewers.

• Report Bad Images – If you suspect a bad image slipped through into the official LaunchBox database, reporting it can help prevent others from encountering the same issue.

Conclusion

While this isn’t a “known bug” within LaunchBox itself, it is a common error caused by damaged image files. If you run into this issue, simply removing the corrupted file should resolve it. If you’re unsure where the bad image came from, it might be worth asking others if they’ve encountered the same issue.

Have you seen this error before? Let us know where you sourced the problematic image, and we may be able to track it down!