Big Box

[Max Howard]

I have a pretty new pc build with win 10 64bit and the latest version of launchbox. Launchbox opens fine but I can't open big box at all. Below is the error I receive every time I try to open big box. Any insight would be appreciated.

[e-mail]

System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.BadImageFormatException: An attempt was made to load a program with an incorrect format. (Exception from HRESULT: 0x8007000B) at SharpDX.XInput.XInput.XInputGetState_(Int32 arg0, Void* arg1) at SharpDX.XInput.XInput.XInputGetState(Int32 dwUserIndex, State& stateRef) at () at LaunchBox.GameControllerHandler.GetCurrentDevices() at BigBox.Data.OptionsListItem..ctor(String name, Action1 saveAction, Action1 loadAction, Func1 getValues) at () at BigBox.Data.OptionsPages.get_Controller() at BigBox.ViewModels.OptionsViewModel..ctor(MainViewModel mainViewModel) at BigBox.ViewModels.MainViewModel..ctor() --- End of inner exception stack trace --- at System.RuntimeTypeHandle.CreateInstance(RuntimeType type, Boolean publicOnly, Boolean noCheck, Boolean& canBeCached, RuntimeMethodHandleInternal& ctor, Boolean& bNeedSecurityCheck) at System.RuntimeType.CreateInstanceSlow(Boolean publicOnly, Boolean skipCheckThis, Boolean fillCache, StackCrawlMark& stackMark) at System.Activator.CreateInstance(Type type, Boolean nonPublic) at System.Activator.CreateInstance(Type type) at Caliburn.Micro.BootstrapperBase.DisplayRootViewFor(Type viewModelType, IDictionary2 settings) at (Bootstrapper , Object , StartupEventArgs ) at BigBox.Bootstrapper.OnStartup(Object sender, StartupEventArgs e) at System.Windows.Application.OnStartup(StartupEventArgs e) at System.Windows.Application.<.ctor>b__1_0(Object unused) 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)

[Jason Carr]

Hi Max, please try updating your DirectX install. Download this and give it a run: https://www.microsoft.com/en-us/download/details.aspx?id=35&nowin10

[Max Howard]

Thanks for you help Jason.I have updated directx and restarted but it hasn't seemed to have an impact. I get what looks to be the same error message. I will continue to troubleshoot but if you have any suggestions please let me know.

System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.BadImageFormatException: An attempt was made to load a program with an incorrect format. (Exception from HRESULT: 0x8007000B) at SharpDX.XInput.XInput.XInputGetState_(Int32 arg0, Void* arg1) at SharpDX.XInput.XInput.XInputGetState(Int32 dwUserIndex, State& stateRef) at () at LaunchBox.GameControllerHandler.GetCurrentDevices() at BigBox.Data.OptionsListItem..ctor(String name, Action1 saveAction, Action1 loadAction, Func1 getValues) at () at BigBox.Data.OptionsPages.get_Controller() at BigBox.ViewModels.OptionsViewModel..ctor(MainViewModel mainViewModel) at BigBox.ViewModels.MainViewModel..ctor() --- End of inner exception stack trace --- at System.RuntimeTypeHandle.CreateInstance(RuntimeType type, Boolean publicOnly, Boolean noCheck, Boolean& canBeCached, RuntimeMethodHandleInternal& ctor, Boolean& bNeedSecurityCheck) at System.RuntimeType.CreateInstanceSlow(Boolean publicOnly, Boolean skipCheckThis, Boolean fillCache, StackCrawlMark& stackMark) at System.Activator.CreateInstance(Type type, Boolean nonPublic) at System.Activator.CreateInstance(Type type) at Caliburn.Micro.BootstrapperBase.DisplayRootViewFor(Type viewModelType, IDictionary2 settings) at (Bootstrapper , Object , StartupEventArgs ) at BigBox.Bootstrapper.OnStartup(Object sender, StartupEventArgs e) at System.Windows.Application.OnStartup(StartupEventArgs e) at System.Windows.Application.<.ctor>b__1_0(Object unused) 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)

[Jason Carr]

Odd. I've seen this issue once before with one other person. It's obviously somehow related to DirectX on your machine, and specifically with XInput, which handles your game controllers. By chance, do you have any Windows Updates available on your machine or are you all up to date?

[Max Howard]

I'm all up to date BUT I do remember downloading an extra XInput dll file that I was missing and that was keeping Skyrim from starting. Is there a way to wipe and reinstall directx?

[Jason Carr]

Ah, interesting. That definitely sounds like the culprit. Where did you put the file and how did you install it? Unfortunately I'm not aware of a way to wipe and reinstall DirectX, but it's probably worth a quick web search.

[Max Howard]

I knew this was my fault. I just copied and pasted it in windows and system32. There were several dll files I did that with. I probably messed up some other things also. I will try to undo my mistakes. Thank you for your help. Hope you have a nice weekend

[Jason Carr]

No problem, Max; if you do figure out exactly what file is causing the problem, I'd love to know the details so that if it comes up again I know how to fix it. Thanks for working through this. :)

[Max Howard]

Hey Jason, I have fixed my problem. I ended up completely reinstalling windows. I couldn't identify which dll files were the problems but I did figure out that I had corrupted my directx install by replacing some of the original dll files. I tired to delete the dll files I had changed and ran several directx installs(hoping they would install the missing pieces) but nothing seemed to help. I was much more careful this time around and found the official directx packages I needed for each game, instead of downloading specific dll files. So the lesson I learned is to not replace dll files, once you have corrupted directx it seems like its impossible to restore.

[Jason Carr]

Gotcha, thank you for the update, Max. It's pretty frustrating that MS doesn't provide a good solution for people in that situation. Glad you got it resolved though. :)