ViGEm Bus Driver v1.16.115 Setup Hotfix released
nefarius last edited by nefarius
Three weeks have passed since the glorious release announcement and we already have to fix things, oops
We've received a report on Discord, that the
v1.16.112setup might abort with an error when run on Windows 7 because of an exception:
Calling custom action ViGEm.Setup.CustomAction!ViGEm.Setup.CustomAction.CustomActions.RemoveAllViGEmBusInstances Begin RemoveAllViGEmBusInstances Exception thrown by custom action: System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.NullReferenceException: Object reference not set to an instance of an object. at ViGEm.Setup.CustomAction.Core.ViGEmBusDevice.GetDeviceDetails(String instanceId, String path) at ViGEm.Setup.CustomAction.CustomActions.RemoveAllViGEmBusInstances(Session session) --- End of inner exception stack trace --- at System.RuntimeMethodHandle.InvokeMethod(Object target, Object arguments, Signature sig, Boolean constructor) at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object parameters, Object arguments) at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object parameters, CultureInfo culture) at Microsoft.Deployment.WindowsInstaller.CustomActionProxy.InvokeCustomAction(Int32 sessionHandle, String entryPoint, IntPtr remotingDelegatePtr) CustomAction RemoveAllViGEmBusInstances_x64 returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox) Action ended 21:08:03: InstallExecute. Return value 3.
Unfortunately this can cause both the installation and the removal and therefore potential upgrades to be stuck for all eternity
So if you happen to be on the receiving end of the issue that the installer can't successfully complete neither installation nor removal, please check out this post and follow the instructions of the provided Microsoft tool to manually clean your system from the broken residue.
To avoid this annoyance in the future we've crafted a hotfix release
v1.16.115which will be pushed through the automatic updater. It doesn't contain a new driver but combats mentioned issue in the setup so updating is advised
A quick preview on how the update process will most probably look like on your end:
And there we have it Happy downloading and keep up helping us discovering and squashing those pesky bugs