Page 1 of 1

Driver for X10S

Posted: Sun Dec 10, 2017 1:34 pm
by Hjeresen
Hi
After my Windows 10 has been updated, I can no longer connect with my Horus X10S!
I do not have an overview of which driver should be installed and maybe that's where the problem is!
Drivers that are now installed:
With Horus turned on:
Frsky X10 mass storage
Produced by: Libwdi
Winusb.sys
WdfColinstaller01011.dll
WinUSBCoInstaller2.dll

With Horus off
STM Device in DFU Mode
Driver STTub30.sys

Best regards
Bo

Re: Driver for X10S

Posted: Mon Dec 11, 2017 4:25 am
by bob195558
I have a lot of stuff not connecting after upgrading Win10, I like win7 better.

Re: Driver for X10S

Posted: Mon Dec 11, 2017 7:08 am
by Kilrah
Seems you used Zadig with radio powered on, not powered off. So you nuked a perfectly good storage driver, and didn't install the one needed for flashing.
Uninstall from device manager, removing driver.

Re: Driver for X10S

Posted: Mon Dec 11, 2017 9:46 am
by MikeB
I had a Windows 10 (Home) update occur, and at least 4 devices then stopped working. I had to change the drivers back to working ones.
I then found: https://www.howtogeek.com/302595/how-to ... e-drivers/, which I followed, so we will see if they now stay working.

Mike.

Re: Driver for X10S

Posted: Mon Dec 11, 2017 11:01 am
by Kilrah
This seems to be only for the normal "minor update" cycle.
From my experience the major updates every 6 months will reselect the Windows default driver for any device for which it has one whatever you do.

The custom driver is still there so you don't actually need to reinstall it, just reselect it in device manager.

The STM32 dfu bootloader is the only one for which it's an annoyance here.

Re: Driver for X10S

Posted: Mon Dec 11, 2017 11:14 am
by jhsa
I think that when windows 7 has no more support I will keep Linux only. I think windows 10 would be just a waste of space on my computer's hard drive :(
Just my 2 cents
João

Re: Driver for X10S

Posted: Mon Dec 11, 2017 11:52 am
by Hjeresen
Thank you for your many responses, I solved the task by deleting and reinstalling the driver.
Mike thanks for linking to article on how to avoid the problem in the future!
Regards Bo