Why did you not try to use the Microsoft driver?
If you attach zip with the driver you got from onyx I may take a look at it and try on my gaming box.
I took the adb as platform tools from the web
https://developer.android.com/studio...orm-tools.html
EDIT:
To speed-up the try-response chat, I am attaching driver extracted from my system. It is Microsoft driver so don't do any mambo-jumbo with unsigned boot, whatsoever...
winusb.zip
First step I recommend, check your C:\Windows\DriverStore\FileRepository... if you have the Microsoft driver as in the zip. I would be surprised if you don't have it.
Next, uninstall onyx driver, google driver, whatsoever. Go to Windows Device Manager click properties on your device and choose "Uninstall driver". Now depending if you already have the windows driver or not: if you have just reboot, if you don't then don't reboot immediately but copy all the files I gave you in the zip to the same folders starting in C:\Windows. Reboot afterwards and you should be using Microsoft driver fully functioning with your Max.
From your screenshot I can see that currently you are using driver named winusb.sys (don't know if it is Microsoft one or just 3rd party with the same name) but with
android_winusb.inf instead of just
winusb.inf. That's a big difference even if you are using the same sys driver. The inf files configure general purpose drivers so it may be the case that your inf file screw up the MS driver.