Big Box Error Crash on start up, logo hangs after with no clossing way.

[ALI ESSA]

System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.DllNotFoundException: Unable to load DLL 'xinput1_3.dll': The specified module could not be found. (Exception from HRESULT: 0x8007007E) 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 Ali, this is because there's a DirectX library missing on your computer. For the next beta I've changed the setup to force update the DirectX libraries when updating. Previously the setup wasn't doing it on update, only on a regular install.

So to fix it, you can either wait until this beta goes out later today, or just manually run the beta 14 setup and install over top of your existing installation and it should correct the issue. Thanks!

[Jason Carr]

Issue #649 was marked as a duplicate of this issue.