Aeravon

I found the other thread about this just now.... I really, really hate that 13.10 made no OS check or warning about it no longer supporting Win7 or 8 and blasted a bunch of people. This is a pretty big mistake in communication.

Long time user and forever license holder. I run a Windows 7 machine for my arcade and have for a few years. 13.9 was working fine, and the 13.10 update for launchbox came out. Updated like usual and now I'm perpetually getting crashes attempting to launch with the following: =============================== (Inner Exception) A procedure imported by 'D:\LaunchBox\ThirdParty\Chromium\CefSharp.Core.Runtime.dll' could not be loaded. App: Version: 13.10 Theme: NOT SET Type: System.IO.FileLoadException Site: Void LoadFromPath(IntPtr, System.String, System.String, System.Runtime.CompilerServices.ObjectHandleOnStack) Source: System.Private.CoreLib at System.Runtime.Loader.AssemblyLoadContext.LoadFromPath(IntPtr ptrNativeAssemblyLoadContext, String ilPath, String niPath, ObjectHandleOnStack retAssembly) at System.Runtime.Loader.AssemblyLoadContext.LoadFromAssemblyPath(String assemblyPath) at System.Reflection.Assembly.LoadFile(String path) at Unbroken.LaunchBox.Windows.Desktop.Program.<>c.LoginSessionObject(Object ) at Unbroken.LaunchBox.Windows.Desktop.Program.<>c.ManageInvalidReader(Object sender, ResolveEventArgs e) at System.Runtime.Loader.AssemblyLoadContext.InvokeResolveEvent(ResolveEventHandler eventHandler, RuntimeAssembly assembly, String name) at System.Runtime.Loader.AssemblyLoadContext.OnAssemblyResolve(RuntimeAssembly assembly, String assemblyFullName) (Outer Exception) A procedure imported by 'CefSharp.Core.Runtime, Version=117.2.40.0, Culture=neutral, PublicKeyToken=40c4b6fc221f4138' could not be loaded. App: Version: 13.10 Theme: NOT SET Type: System.IO.FileLoadException Site: Void .ctor() Source: CefSharp.Core at CefSharp.CefSettingsBase..ctor() at Unbroken.LaunchBox.Windows.Desktop.App..ctor() at Unbroken.LaunchBox.Windows.Desktop.Program.Main(String[] args) Recent Log: 4:37:55 PM Exception ============================ I had a restore point to 13.5 which I did, and launchbox ran fine again and other than losing any changes I made since then, was okay. But then I tried to update to 13.10 again and returned to same error on launch and can no longer use the product. The machine isn't Windows 11 capable, and I don't have a spare license of 10 to use so please don't tell me to update my OS. Either the product works on the OS or it doesn't now; so what internal component of Launchbox is trying to leverage aspects of chromium that don't exist in Windows 7 and disqualify it? Is this a bug? Is this a graduation of the product to no longer support Windows 7 and 8? But that we didn't get warned? Installing Chrome as a separate product doesn't help. TL:DR Windows 7, 13.9 and all previous versions ran great, 13.10 broke it.