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.
Matthias Huber 00
Thanks for the suggestion! I'd like to try this, but I'm not sure where I can find the driver file. I tried the the "uvhid.inf" in the UR3 installation folder, but this gives me an error message in the hardware wizard saying that the driver could not be found.
I don't use widows10...... but I believe the driver causing problems is in the "uvhid" folder of the UR download... X64 if you are running a 64-bit os...... and X86 if 32-bit (unlikely).
But maybe you only have easy access to that if you have downloaded a standalone (portable) version of the server. You will find it here..... https://www.unifiedremote.com/download/other
Download the V3 portable Windows server..... go to the uvhid/x64 folder, where you will find the .inf file and drivers........
Matthias Huber 00
That's the exact driver I tried to install, but unfortunately, it gives me this error message:
I cannot help then....sorry.... you will have to hope the developers do something about it.
Every day I am more and more pleased that I bought a quantity of Win7 licenses.
Ian Williams 00
I took a meander through the portable version, as well as the drivers installed by the MSI installer. It appears that the
hidkmdf.sysdriver is unsigned, and one of the ones used by the app.
This file is still unsigned, even in the recent 3.6.0 release. Signing this file should fix the issue.
This is still an issue. The Unified Virtual HID driver digital signatures still cannot be verified by windows, so the remote can't be used on the unlock screen or user access control screens.
Bumping this because I have been looking for a solution for months.
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.