The Lighting Controller

I'm going round in circles trying to install drivers on Windows 10 for my USB Cable dongle.

The furthest I have got is "CABLE Interface 64bits (2018_04_25)" in my "Universal Serial Bus Controllers" in Device Manager, but it has a warning triangle and reviewing the properties it says .....

"Windows cannot verify the digital signature for the drivers required for this device. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be unknown software from a malicious source. (Code 52)"

What could be the problem ? And how to fix it.....

TIA

Please follow this for manual usb driver installation: https://thelightingcontroller.com/viewt ... f=7&t=5083.

FYI, with an internet connection, Microsoft is supposed to install automatically the drivers for our interfaces.

No, this is not working as described...

"Searching Online for Drivers" has been running for over 3 hours, this is obviously not right....

Please give link to driver install so I can do it manually.

Just completed a 5 hour Windoze Update, and the drivers have installed successfully.

I already had those files you linked to.

Nice to hear all is fine now.

Well it was all fine 2 days ago, but started up Showexpress a while ago and it can't fine the USB Cable dongle again - even though it was working 2 days ago. The PC hasn't been switched off since it was working.

Device Manager is showing "CABLE interface 64bits (2018_04_25)" in the "Universal Serial Bus controllers" category

There have been no Windows updates since then, and Windows is saying I have the best driver for the hardware installed.

I don't know how to "fix" this issue.... Can anyone help, point me in the right direction to go please....

So if we right understand:
- the dmx interface was found some days ago and now it is now found anymore
- and there was no change in the PC, even not a power off/on

Please try on another PC, in order to know which device (PC or dmx interface) has a problem.

support wrote:So if we right understand:
- the dmx interface was found some days ago and now it is now found anymore
- and there was no change in the PC, even not a power off/on

Please try on another PC, in order to know which device (PC or dmx interface) has a problem.

To be brutally honest, I think that would cloud the issue, and introduce new variables. Imagine if I had only this one PC, what would be a solution to this problem ?

I have removed the device (and drivers) several times, re-installed drivers several times, but still this issue persists. ShowXpress still cannot see the Xpress 100 Cable interface.

After removing the device and drivers in Device Manager, then plug my Xpress 100 device in. Windows immediately detects it, and installs drivers as shown ....

In "Other Devices" : "USB Serial Port", warning triangle : Properties say "The drivers for this device are not installed. (Code 28)", location "on CABLE interface 64bits (2017_07).

In "Universal Serial Bus Controllers" : "CABLE interface 64bits (2017_07)" : Properties say "This device is working properly."

At this point, I can start ShowXpress, and it DOES find the interface, and I can work with it. But this is not the latest driver software, and I still have that "USB Serial Port" entry in device manager.

So, I update the driver manually, from the Drivers.zip files you linked to, and then restart the PC (it tells you to).

After doing that, the "Other Devices" : "USB Serial Port" is not there in Device Manager, and the "CABLE interface 64bits (2017_07)" has been replaced with "CABLE interface 64bits (2018_04_25)", but this has a warning triangle, and the device properties say "Windows cannot verify the digital signature for the drivers required for this device. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source. (Code 52)", and of course ShowXpress cannot see the interface.

For now, I will use the "CABLE interface 64bits (2017_07)" driver, because it works, but there must be an issue with the "CABLE interface 64bits (2018_04_25)" driver.