ViGEm Bus Driver v1.16.115 Setup Hotfix released



  • Howdy 🤠

    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.112 setup 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.115 which 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:

    2f9cd78e-a951-4447-8dac-8be522454be3-image.png

    2a496f63-713f-4cb1-a381-d01732e82769-image.png

    137aebc9-b1f9-458f-818f-9f7a7e6b05bc-image.png

    0f94bf3f-3cf2-4000-9669-cf4f9bdc0e6a-image.png

    c1e57df9-87d1-469d-8a93-44213206b1e0-image.png

    a3b4c9a0-26f9-4d84-8581-2cae27205a4b-image.png

    f8017626-3540-4f78-86b2-a2152fc9a64e-image.png

    And there we have it 🙂 Happy downloading and keep up helping us discovering and squashing those pesky bugs 🐛 🔫

    Cheers


Log in to reply