WIN10 USB problems in 1.09 build. Code 10 failure.

[WOPR-Computer]

Is anyone looking into WIN10 USB incompatibility? This is a deal breaker for using opentx i6x. I am a hardware guy and do not know much about programing. I suspect the problem is with timing but have no way of checking. Failures show up in the WIN10 driver. Mabey a new driver is needed? I do not know. Please someone take on this problem. I like opentx but can not be much help in fixing this.

[WOPR-Computer]

I found a work around. I created a new model and placed it in the exterior TX with the interior tx off. I use a 4 channel uart USB cable to PS2 connector. The uart connects to the computer as a USB device and reads the i6x ppm output. be cause it is only a 4 channel devise it does not see channels 5,6. AETR work. Curves can be set. The cable I am using is very old, I think it came with an E-Sky Helicopter transmitter.

[WOPR-Computer]

Device USB\VID_1209&PID_4F54\00000000001B was not migrated due to partial or ambiguous match.

Last Device Instance Id: USB\VID_046D&PID_C52B\6&231ed10a&0&2
Class Guid: {36fc9e60-c465-11cf-8056-444553540000}
Location Path: PCIROOT(0)#PCI(0801)#PCI(0003)#USBROOT(0)#USB(2)
Migration Rank: 0xF000FFFFFFFF0033
Present: false
Status: 0xC0000719

[WOPR-Computer]

The INF Version section should have the CLASSGUID and DriverVer directives set as follows:

The CLASSGUID directive must specify the Microsoft class GUID for HID devices. This GUID has the value {745a17a0-74d3-11d0-b6fe-00a0c90f57da}.

The DriverVer directive must have a value that has a newer date and greater version number than the value specified by the DriverVer directive in Input.inf.

The VendorXYZDevice* sections specify the hardware identifier (ID) for the vendor's HID device. The hardware ID consists of a vendor identifier (VID) and product identifier (PID). Each hardware ID for a device must have VID/PID values that are unique to the vendor and device. This ensures that the same hardware ID does not correspond to multiple names and settings
The VendorXYZDevice_Install.NT and VendorXYZDevice_Install.NT.HW sections are INF DDInstall sections. In this example, these sections contain INF Include and Needs directives.
The Include directives reference the system-supplied Input.inf file, which contains INF sections needed to enable the USB selective suspend feature for the vendor's HID device.

The Needs directives indicate which sections from Input.inf should be processed during device installation. In this case, the HID_SelSus_Inst section is selected instead of the default HID_Inst section, which does not support selective suspend.

The VendorXYZDevice_Install.NT.Services section is an INF DDInstall.HW section. In this example, the section also contains the same values for the INF Include and Needs directives.