You need to change 3 things to make the Google USB driver work on any Android phone in any Windows:
- Add device id to
android_winusb.inf file - Digital sign of a modified driver
- Add the device vendor id to the
adb_usb.ini (no longer required)
and here are the details:
1. Add the device identifier to the android_winusb.inf file
format to add:
Before proceeding, VID is the identifier of the USB provider.
How to get vid and pid: they are in the drivers that you combine; but if you do not have a driver for the device, you can get it by opening the device manager; then right-click the device - select properties - in the new dialog, go to the "Information" tab> in the "Properties" menu, select "Equipment Identifiers". for example, you see something like:

USB\VID_2207&PID_0000&REV_0222&MI_01 USB\VID_2207&PID_0000&MI_01
take this value for composite adb device and delete MI for one adb device, you will get
;MSI WindPad Enjoy 7 plus %SingleAdbInterface% = USB_Install, USB\VID_2207&PID_0000 %CompositeAdbInterface% = USB_Install, USB\VID_2207&PID_0000&REV_0222&MI_01 ;
copy this 2 lines of TWICE, once to the [Google.NTx86] section, and another to the [Google.NTamd64] section.
REPEAT for each device you want to support
Now additional editing for the [Lines] section: edit
[Strings] ProviderName = "Google, Inc." SingleAdbInterface = "Android ADB Interface" CompositeAdbInterface = "Android Composite ADB Interface" SingleBootLoaderInterface = "Android Bootloader Interface" WinUSB_SvcDesc = "Android USB Driver" DISK_NAME = "Android WinUsb installation disk" ClassName = "Android Device"
To:
[Strings] ProviderName = "Google, Inc." SingleAdbInterface = "MSI ADB Interface" CompositeAdbInterface = "MSI Composite ADB Interface" SingleBootLoaderInterface = "MSI Bootloader Interface" WinUSB_SvcDesc = "MSI USB Driver" DISK_NAME = "MSI WinUsb installation disk" ClassName = "MSI Tablet"
2. Digital sign of the modified driver:
Although the original google usb driver was signed by google, changing android_winusb.inf will not allow you to install it on Windows 8, displaying an error message 
The hash file is not present in the specified catalog file. The file is likely corrupt or the victim of tampering.
This is only in Windows 8. Windows 7 or earlier does not display this error message. You need to restore the directory file (possibly using the Windows SDK) and sign
Workaround: workaround for internal binding - verification of signature as a string: either temporarily or permanently:
temporarily
Go to the upper or lower corner of the screen on the left to open the charms panel and press the settings button.
select "Change PC Settings"
select "General"
Scroll down and click "Restart Now" in the "Advanced Launch" section.
Click "Troubleshoot. Click" Advanced Options. "Click" Windows Startup Options. "Click" Restart. "
or
run cmd and type:
shutdown -o -r -t 0
then after restarting, select "Disable driver forced signing" from the list. install the driver before rebooting.
Constantly:
press Window + Q
find cmd
right click cmd
select start as administrator from action bar
enter cmd:
bcdedit -set loadoptions DISABLE_INTEGRITY_CHECKS bcdedit -set TESTSIGNING ON
3. Add the device provider identifier to the adb_usb.ini white list (no longer required):
adb used to hardcode the whitelist of supported vendor identifiers. If your device was not listed, then adb completely ignored it. In order for adb recognize such devices, users had to manually add their vendor identifiers to %USERPROFILE%\.android\adb_usb.ini - one identifier per line.
on the command line:
echo 0x2207 >> "%USERPROFILE%\.android\adb_usb.ini"
Fortunately, Google removed VendorID filtering in later adb versions. Therefore, this step is no longer required.
Finally, you can test the installation:
adb kill-server adb start-server adb devices
and enable debugging in the developer settings on the Android device
This should restart the ADB server and device list. If the driver is working properly, the device must be specified.