Windows 10 Version 1607 Input Driver Signature
I've just discovered a driver issue related to latest Unified Remote Server (downloadable yesterday, 08th Aug.). The Issue happens when UR-Server is installed using the input driver for windows. The driver gets installed successfully, but windows revokes to use it due to "Driver Signature Failure". That way, "Basic Input" and other driver related functions are not usable.
This seems to happen only on the new Windows 10 Version 1607, it does not make any difference in updating to 1607 or installing a fresh copy of 1607.
It seems Microsoft now accept only drivers signed by themselves.
If you absolutely cannot live without this feature you could try one of these solutions........
Registry hack for this driver only......
John Youdan 00
I've just found this little app today and it installed perfectly and runs well on my Win 10 x64 Surface Pro 3 with a completely busted, non functioning screen and a badly bent chassis.
I found this particular thread because I wish to try to run the server as a service having failed to select the option during install. Maybe irrelevant to what you are discussing here and if so I apologise to the OP.
Anyway here is a screenshot of my system, a bit squashed up unfortunately as I am accessing the Surface using RDC on a low res laptop.
So how do we enable to run as a Windows service after install?
Jake Storms 00
Will the driver ever get signed? I would think atleast users of the pro version should have access to a signed driver if this is a cost issue to get things signed by MS?? Really annoying.
Ian Williams 00
This is in the top 5 most-viewed threads on this board - anyone going to respond about it?
so I contacted them on twitter and they suggested this was fixed, although it isn't. The issue seems to be they are not signed with a (more expensive) EV certificate which Windows 10 now requires for kernel mode drivers, as per https://blogs.msdn.microsoft.com/windows_hardware_certification/2016/07/26/driver-signing-changes-in-windows-10-version-1607/
They also don't seem to be signed by Microsoft (e.g. via the portal) which also seems to be a requirement.
I believe the only way to get around this until Unified Remote update their certificate and resign the drivers via Microsoft is to disable signature enforcement which isn't ideal.
Shame as being unable to unlock my PC remotely really limits using the remote, e.g. from waking my PC up.
This post is deleted!last edited by
I just paid ... For an useless app...
My windows 10 pro absolutely cannot have disabled any kind of protection . but ... Really? No solution by developers?
I tried legacy input mode, but anyway the logs registers my remote inputs but the server app do not do anything....
I do not have any error. I tried also to reinstall to enable HID... I have no error but simply I have nothing at all.
Thanks for commercializing something that is not working.
and the driver signature problem continues to this day with windows 10 1809.
it's a shame, but at least the legacy V2 version works, it does not have several features equal to V3, but at least it works the basic input and vlc keybord.