Resolving A USB Driver Connection Failure (Caused By Use of The Old GC2 Driver)

Resolving A USB Driver Connection Failure (Caused By Use of The Old GC2 Driver)

Foresight Sports USB Device Issues

Two separate issues have been found relating to the Foresight Sports USB Drivers which affect Windows users. This document is provided in order to assist with diagnosing these issues and provide instructions to resolve them so that normal functionality can be restored to the affected systems.

Issue #1: USB Driver Access Denied

On certain installations of Windows an issue has been introduced which prevents communication with the USB Device Driver and thus prevents all associated software from functioning. This is caused by some, as of yet unknown, Windows Kernel component over-writing the default Security attributes of our Device handle.

Symptoms

Software and Driver will install correctly but communication with the device will fail with an error “Access Denied”

Diagnosis

  1. Open Device Manager
  2. Find the “NGLM MSC Interface Device” entry
  3. Double click to open the “Properties” dialog and click on the “”Details” tab
  4. From the “Property” dropdown select “Physical Device Object Name
  5. Note the value (ex \Device\USBPDO-10)
  6. Download the “exe” tool from https://technet.microsoft.com/en-us/sysinternals/bb896657.aspx
  7. Extract and execute exe with Administrator privileges and navigate to “Device” tree
  8. Double click the entry which corresponds to the previously noted “Physical Device Object Name
  9. If you see an error “Access is Denied” than proceed to work around steps

Workaround

  1. Uninstall Device Instance Software
  • Unplug NGLM USB Device
  • Open Device Manager and select “View -> Show Hidden Devices
  • This Uninstall Device Instance (Right Click -> Uninstall) Note on Windows 10 you must check "Delete the driver software for this device"
  1. Uninstall Device Setup Class Software
  • Run "Regedit" with Administrator privileges
  • Navigate to: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{78A1C341-4539-11d3-B88D-00C04FAD5171}
  • Take ownership of this key (Right Click -> Permissions -> Security -> Advanced -> Owner : Change)

 

  • Explicitly add full permissions (Right Click -> Permissions -> Security -> Add : Full Permissions)
  • Repeat previous 2 steps for all subkeys
  • Delete the registry key
  1. ReInstall Drivers
  2. Verify Proper Functionality

 

 

Issue #2: USB Driver Failed to Load

On certain installations of Windows an issue has been introduced which prevents the USB drivers from correctly loading. This is caused by using the default value for the Setup Class Guid (78A1C341-4539-11d3-B88D-00C04FAD5171) present in the WinUsb sample from Microsoft instead of generating a unique value. The result is interoperability issue with other software which uses this default value which manifests as an incomplete and corrupted Drive Package being staged to the Windows Driver Repository.

Symptoms

During Software Installation, the Driver Software will fail to load with an error “The Path Could not be Found”.

Diagnosis

Open Regedit and navigate to the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{78A1C341-4539-11d3-B88D-00C04FAD5171} key. If it is present without our driver correctly loading, then proceed to the work around steps.

Workaround

  1. Uninstall the software which is using this key.
  • Currently only McAfee Antivirus software has been found to use this value. But potentially other products may be making the same mistake.
  • This can be verified by examining the Class node under this Registry key. Find the corresponding entry under the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Services hive and it will indicate which software is using this value.

 

  1. Uninstall the Device Setup Class
  • Follow workaround instructions Step 2 of Issue 1: USB Driver Access

 

  1. Uninstall Corrupted ForeSightSports Driver Package
  • Start a “cmd” prompt session with Administrator privileges
  • Execute “pnputil –e” to list all installed 3rd Party Driver Packages
  • Find the entry corresponding to “Driver Package Provider” equals ForesightSports and note “Published Name” value in the format “inf
  • Execute “pnputil –f –d <Published Name> with the name noted earlier to force deletion of this package
  1. Install ForeSightSports Software
  2. Verify Proper Functionality
    • Related Articles

    • GC2 USB Troubleshooting

      Your GC2 Device will not connect to the computer or within the software as expected. To Begin Troubleshooting the USB for a GC2 device follow the steps below: Note: These troubleshooting steps assume the device is functioning correctly and will ...
    • Failed GC2 Driver Installation

      Problem: Your GC2 device is not communicating to your software or computer correctly. Explanation: Your device may be damaged. However, if this is not the case than you may have a failed USB driver installation for the GC2 device. This will be ...
    • FSX 2020 Crashing During Use

      We are sorry to hear you are having trouble with the FSX 2020 Software. The following system specifications are required to operate the FSX 2020 Software: System Requirements: Operating System: 64 Bit Windows 10 or greater not supported: iOS, Linux ...
    • What Connection Type Is Best For Me?

      Every GC3, Bushnell Launch Pro, GCQuad, and GCHawk allows for three primary connection types to software: 1. USB-C 2. Ethernet (Cat 5/6/7/10) Cable 3. WiFi (Wireless) Connection The best connect type is determined by your use case: USB- C is simple ...
    • Validation Failure or Internet Error Message Related to Comcast / Xfinity

      Customers having issues with Comcast/Xfinity not allowing their Activation Emails through or for FSX to validate/activate please adjust the settings below: 1. Log into xfinity.com/myxfi 2. Click "More" at the top 3. Disable XFi advanced security ...