Error launching BigBox

Issue #907 invalid
Matt Wynn created an issue

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)

Comments (10)

  1. Matt Wynn reporter

    Thanks for the quick response. Running Win 10 64-bit. Tried to reinstall DirectX but it said I have the current version.

  2. Jason Carr repo owner

    Okay, this has happened to a few people and we're pretty baffled about it to be honest. Doesn't happen to the vast majority but somehow or other DirectX XInput seems to be busted on some people's machines. Do you have any game controllers connected by chance?

  3. Jason Carr repo owner

    I did some more research with this; it appears to be caused by users somehow getting 32-bit versions of DirectX DLLs on 64-bit machines. Honestly I still haven't figured out why or how that happens, but I've been reading through a few threads here:

    https://steamcommunity.com/app/207140/discussions/2/619569341041228870/ http://steamcommunity.com/app/241600/discussions/1/846958223171354071 http://xboxforums.create.msdn.com/forums/t/45021.aspx https://steamcommunity.com/app/244850/discussions/6/618457398966571406/

    Anyways, it does seem that the issue is that the xinput_1_3.dll file on your machine is 32-bit when it should be 64-bit, or something like that. I haven't found a solution yet that doesn't involve overwriting system files (that sucks); it seems that the DirectX installer somehow doesn't take care of the problem. I'll keep looking.

  4. Jason Carr repo owner

    Okay, sigh. Hrm. Can you do me a favor? Can you zip up your C:\Windows\System32\xinput1_3.dll file from your machine and send it over to me via email? That file seems to be the problem and I'm curious what might be causing it. I think if we replace that file with the right copy it will work, but I'm admittedly hesitant to tell people to go replacing files in the Windows System32 folder.

  5. Log in to comment