usrp-users@lists.ettus.com
Discussion and technical support related to USRP, UHD, RFNoC
View all threadsRe: [USRP-users] Signed driver needed for Windows 10
This must have worked at one time, but it seems to have been disabled
with recent Windows 10 updates. I am using a brand-new computer with
the latest updates applied. There are also some other tricks involving
"bcdedit" incantations that worked on W10 preview don't do anything on
the most recent release either. The right answer is for Ettus to
release a signed driver, which they say they are working on. I hope
that the process on their end isn't too involved since the issue will
expand as people accept the Windows 10 update that is being widely
pushed.
Another solution might be for the driver to be released in source form,
if there is a way for a user to self-sign code that he compiles
himself. I'd take either one at this point.
Hi
You can install unsigned drivers in Windows 10. Just follow the
instruction from this link: http://www.howtogeek.com/167723/how-to-dis
able-driver-signature-verification-on-64-bit-windows-8.1-so-that-you-
can-install-unsigned-drivers/
Basically, you need to reboot your system with deactivated signed
driver check.
Regards,
Jonas
Hi D.Des,
all the drivers involved are open source; also, you wouldn't need the
source code to sign it, as far as I know; however, doing that will
require your Windows to trust the certificate that signed the driver,
and that won't work any better for you than it should for e.g. an
arbitrary program running on your PC that tries to install a driver they
actually shouldn't be allowed to install.
So, you need some certificate that Microsoft trusts, use that to sign
your driver's signing, etc.
As Martin said, working on that for the WinUSB driver, being able to use
NI's ressources. It's just not production-ready yet.
I'm a bit surprised it stopped working, because, well, there's people
who actually need to develop drivers... but nevertheless, yes, having
a signed driver is pretty much what you'd want. (No, actually, what
you'd want is for Windows to have a "normal" USB stack like any other
serious desktop OS out there, where you don't need to install a driver
for generic USB devices that just offer bulk transfer packets to
userland, but that's a rant for another day ;) ).
Best regards,
Marcus
On 09.02.2016 03:52, d.des via USRP-users wrote:
This must have worked at one time, but it seems to have been disabled
with recent Windows 10 updates. I am using a brand-new computer with
the latest updates applied. There are also some other tricks involving
"bcdedit" incantations that worked on W10 preview don't do anything on
the most recent release either. The right answer is for Ettus to
release a signed driver, which they say they are working on. I hope
that the process on their end isn't too involved since the issue will
expand as people accept the Windows 10 update that is being widely
pushed.
Another solution might be for the driver to be released in source form,
if there is a way for a user to self-sign code that he compiles
himself. I'd take either one at this point.
Hi
You can install unsigned drivers in Windows 10. Just follow the
instruction from this link: http://www.howtogeek.com/167723/how-to-dis
able-driver-signature-verification-on-64-bit-windows-8.1-so-that-you-
can-install-unsigned-drivers/
Basically, you need to reboot your system with deactivated signed
driver check.
Regards,
Jonas
USRP-users mailing list
USRP-users@lists.ettus.com
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
I had thought that it was only possible to sign drivers that you
compiled yourself but that might not be the case. The process is
described here:
http://blogs.msdn.com/b/windows_hardware_certification/archive/2015/04/
01/driver-signing-changes-in-windows-10.aspx
https://msdn.microsoft.com/en-us/library/windows/hardware/ff552275%28v=
vs.85%29.aspx
and involves installing a 6.5 GB Windows Driver Kit (or Assessment
Development Kit -- the name changes somewhere in the download link
chain...). I'll attempt it for grins when I get somewhere with better
internet access and try to set it up and see if I can test-sign your
driver. The "Bcdedit.exe -set TESTSIGNING ON" command only allows the
computer to accept your own signature (and constantly reminds you with
a banner on your screen): you still need the development kit to sign
the driver package.
I'm stuck with Windows on this application. I don't know how general
your driver is, but maybe once it's accepted by Windows it will
effectively provide that "normal" USB stack functionality.
Thanks,
Dave
Hi D.Des,
all the drivers involved are open source; also, you wouldn't need the
source code to sign it, as far as I know; however, doing that will
require your Windows to trust the certificate that signed the driver,
and that won't work any better for you than it should for e.g. an
arbitrary program running on your PC that tries to install a driver
they
actually shouldn't be allowed to install.
So, you need some certificate that Microsoft trusts, use that to sign
your driver's signing, etc.
As Martin said, working on that for the WinUSB driver, being able to
use
NI's ressources. It's just not production-ready yet.
I'm a bit surprised it stopped working, because, well, there's people
who actually need to develop drivers... but nevertheless, yes, having
a signed driver is pretty much what you'd want. (No, actually, what
you'd want is for Windows to have a "normal" USB stack like any other
serious desktop OS out there, where you don't need to install a driver
for generic USB devices that just offer bulk transfer packets to
userland, but that's a rant for another day ;) ).
Best regards,
Marcus
On Tue, 2016-02-09 at 02:52 +0000, d.des wrote:
This must have worked at one time, but it seems to have been disabled
with recent Windows 10 updates. I am using a brand-new computer with
the latest updates applied. There are also some other tricks
involving
"bcdedit" incantations that worked on W10 preview don't do anything
on
the most recent release either. The right answer is for Ettus to
release a signed driver, which they say they are working on. I hope
that the process on their end isn't too involved since the issue will
expand as people accept the Windows 10 update that is being widely
pushed.
Another solution might be for the driver to be released in source
form,
if there is a way for a user to self-sign code that he compiles
himself. I'd take either one at this point.
Hi
You can install unsigned drivers in Windows 10. Just follow the
instruction from this link: http://www.howtogeek.com/167723/how-to-
dis
able-driver-signature-verification-on-64-bit-windows-8.1-so-that-
you-
can-install-unsigned-drivers/
Basically, you need to reboot your system with deactivated signed
driver check.
Regards,
I'm stuck with Windows on this application. I don't know how general
your driver is, but maybe once it's accepted by Windows it will
effectively provide that "normal" USB stack functionality.
Yeah, that's exactly what WinUSB does: give you access to the raw bulk
transfers; again, the problem is that Windows "expects" a driver for
every single new USB device ID; hence you can't say "hi, I'm a userland
program, I'd like to talk to this and that device using the general
driver"; you need to "register" a driver for that PID/VID combo...
Best regards,
Marcus
On 02/09/2016 03:39 PM, d.des via USRP-users wrote:
I had thought that it was only possible to sign drivers that you
compiled yourself but that might not be the case. The process is
described here:
http://blogs.msdn.com/b/windows_hardware_certification/archive/2015/04/
01/driver-signing-changes-in-windows-10.aspx
https://msdn.microsoft.com/en-us/library/windows/hardware/ff552275%28v=
vs.85%29.aspx
and involves installing a 6.5 GB Windows Driver Kit (or Assessment
Development Kit -- the name changes somewhere in the download link
chain...). I'll attempt it for grins when I get somewhere with better
internet access and try to set it up and see if I can test-sign your
driver. The "Bcdedit.exe -set TESTSIGNING ON" command only allows the
computer to accept your own signature (and constantly reminds you with
a banner on your screen): you still need the development kit to sign
the driver package.
I'm stuck with Windows on this application. I don't know how general
your driver is, but maybe once it's accepted by Windows it will
effectively provide that "normal" USB stack functionality.
Thanks,
Dave
Hi D.Des,
all the drivers involved are open source; also, you wouldn't need the
source code to sign it, as far as I know; however, doing that will
require your Windows to trust the certificate that signed the driver,
and that won't work any better for you than it should for e.g. an
arbitrary program running on your PC that tries to install a driver
they
actually shouldn't be allowed to install.
So, you need some certificate that Microsoft trusts, use that to sign
your driver's signing, etc.
As Martin said, working on that for the WinUSB driver, being able to
use
NI's ressources. It's just not production-ready yet.
I'm a bit surprised it stopped working, because, well, there's people
who actually need to develop drivers... but nevertheless, yes, having
a signed driver is pretty much what you'd want. (No, actually, what
you'd want is for Windows to have a "normal" USB stack like any other
serious desktop OS out there, where you don't need to install a driver
for generic USB devices that just offer bulk transfer packets to
userland, but that's a rant for another day ;) ).
Best regards,
Marcus
On Tue, 2016-02-09 at 02:52 +0000, d.des wrote:
This must have worked at one time, but it seems to have been disabled
with recent Windows 10 updates. I am using a brand-new computer with
the latest updates applied. There are also some other tricks
involving
"bcdedit" incantations that worked on W10 preview don't do anything
on
the most recent release either. The right answer is for Ettus to
release a signed driver, which they say they are working on. I hope
that the process on their end isn't too involved since the issue will
expand as people accept the Windows 10 update that is being widely
pushed.
Another solution might be for the driver to be released in source
form,
if there is a way for a user to self-sign code that he compiles
himself. I'd take either one at this point.
Hi
You can install unsigned drivers in Windows 10. Just follow the
instruction from this link: http://www.howtogeek.com/167723/how-to-
dis
able-driver-signature-verification-on-64-bit-windows-8.1-so-that-
you-
can-install-unsigned-drivers/
Basically, you need to reboot your system with deactivated signed
driver check.
Regards,
USRP-users mailing list
USRP-users@lists.ettus.com
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
Hello Dave,
I am working on this driver signing issue and as you may imagine, the
process is more of a procedural one than a technical one. As soon as the
process is complete we'll be releasing them. It's well understood that this
is needed on recent versions of Windows.
In the meanwhile the process described in the post linked above, and below,
has worked for many people. If it has recently stopped working for Windows
10 then that is very unfortunate.
Regards,
Derek
On Tue, Feb 9, 2016 at 6:48 AM, Marcus Müller usrp-users@lists.ettus.com
wrote:
I'm stuck with Windows on this application. I don't know how general
your driver is, but maybe once it's accepted by Windows it will
effectively provide that "normal" USB stack functionality.
Yeah, that's exactly what WinUSB does: give you access to the raw bulk
transfers; again, the problem is that Windows "expects" a driver for
every single new USB device ID; hence you can't say "hi, I'm a userland
program, I'd like to talk to this and that device using the general
driver"; you need to "register" a driver for that PID/VID combo...
Best regards,
Marcus
On 02/09/2016 03:39 PM, d.des via USRP-users wrote:
I had thought that it was only possible to sign drivers that you
compiled yourself but that might not be the case. The process is
described here:
http://blogs.msdn.com/b/windows_hardware_certification/archive/2015/04/
01/driver-signing-changes-in-windows-10.aspx
https://msdn.microsoft.com/en-us/library/windows/hardware/ff552275%28v=
vs.85%29.aspx
and involves installing a 6.5 GB Windows Driver Kit (or Assessment
Development Kit -- the name changes somewhere in the download link
chain...). I'll attempt it for grins when I get somewhere with better
internet access and try to set it up and see if I can test-sign your
driver. The "Bcdedit.exe -set TESTSIGNING ON" command only allows the
computer to accept your own signature (and constantly reminds you with
a banner on your screen): you still need the development kit to sign
the driver package.
I'm stuck with Windows on this application. I don't know how general
your driver is, but maybe once it's accepted by Windows it will
effectively provide that "normal" USB stack functionality.
Thanks,
Dave
Hi D.Des,
all the drivers involved are open source; also, you wouldn't need the
source code to sign it, as far as I know; however, doing that will
require your Windows to trust the certificate that signed the driver,
and that won't work any better for you than it should for e.g. an
arbitrary program running on your PC that tries to install a driver
they
actually shouldn't be allowed to install.
So, you need some certificate that Microsoft trusts, use that to sign
your driver's signing, etc.
As Martin said, working on that for the WinUSB driver, being able to
use
NI's ressources. It's just not production-ready yet.
I'm a bit surprised it stopped working, because, well, there's people
who actually need to develop drivers... but nevertheless, yes, having
a signed driver is pretty much what you'd want. (No, actually, what
you'd want is for Windows to have a "normal" USB stack like any other
serious desktop OS out there, where you don't need to install a driver
for generic USB devices that just offer bulk transfer packets to
userland, but that's a rant for another day ;) ).
Best regards,
Marcus
On Tue, 2016-02-09 at 02:52 +0000, d.des wrote:
This must have worked at one time, but it seems to have been disabled
with recent Windows 10 updates. I am using a brand-new computer with
the latest updates applied. There are also some other tricks
involving
"bcdedit" incantations that worked on W10 preview don't do anything
on
the most recent release either. The right answer is for Ettus to
release a signed driver, which they say they are working on. I hope
that the process on their end isn't too involved since the issue will
expand as people accept the Windows 10 update that is being widely
pushed.
Another solution might be for the driver to be released in source
form,
if there is a way for a user to self-sign code that he compiles
himself. I'd take either one at this point.
Hi
You can install unsigned drivers in Windows 10. Just follow the
instruction from this link: http://www.howtogeek.com/167723/how-to-
dis
able-driver-signature-verification-on-64-bit-windows-8.1-so-that-
you-
can-install-unsigned-drivers/
Basically, you need to reboot your system with deactivated signed
driver check.
Regards,
USRP-users mailing list
USRP-users@lists.ettus.com
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
USRP-users mailing list
USRP-users@lists.ettus.com
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
On 02/09/2016 10:26 AM, Derek Kozel via USRP-users wrote:
Hello Dave,
I am working on this driver signing issue and as you may imagine, the
process is more of a procedural one than a technical one. As soon as
the process is complete we'll be releasing them. It's well understood
that this is needed on recent versions of Windows.
In the meanwhile the process described in the post linked above, and
below, has worked for many people. If it has recently stopped working
for Windows 10 then that is very unfortunate.
Regards,
Derek
Another issue is a philosophical/chain-of-custody type thing. WinUSB
isn't written by Ettus, but is packaged as a convenience for Windows
users. In the best of all possible worlds, that driver would be
signed by the folks who provide and package WinUSB. Although I guess
that if it's being compiled-from-source, Ettus has no choice but to
sign the result.
On Tue, Feb 9, 2016 at 6:48 AM, Marcus Müller
<usrp-users@lists.ettus.com mailto:usrp-users@lists.ettus.com> wrote:
I'm stuck with Windows on this application.I don't know how general
your driver is, but maybe once it's accepted by Windows it will
effectively provide that "normal" USB stack functionality.
Yeah, that's exactly what WinUSB does: give you access to the raw bulk
transfers; again, the problem is that Windows "expects" a driver for
every single new USB device ID; hence you can't say "hi, I'm a
userland
program, I'd like to talk to this and that device using the general
driver"; you need to "register" a driver for that PID/VID combo...
Best regards,
Marcus
On 02/09/2016 03:39 PM, d.des via USRP-users wrote:
I had thought that it was only possible to sign drivers that you
compiled yourself but that might not be the case. The process is
described here:
http://blogs.msdn.com/b/windows_hardware_certification/archive/2015/04/
01/driver-signing-changes-in-windows-10.aspx
https://msdn.microsoft.com/en-us/library/windows/hardware/ff552275%28v=
vs.85%29.aspx
and involves installing a 6.5 GB Windows Driver Kit (or Assessment
Development Kit -- the name changes somewhere in the download link
chain...). I'll attempt it for grins when I get somewhere with
better
internet access and try to set it up and see if I can test-sign your
driver. The "Bcdedit.exe -set TESTSIGNING ON" command only
allows the
computer to accept your own signature (and constantly reminds
you with
a banner on your screen): you still need the development kit to sign
the driver package.
I'm stuck with Windows on this application. I don't know how
general
your driver is, but maybe once it's accepted by Windows it will
effectively provide that "normal" USB stack functionality.
Thanks,
Dave
Hi D.Des,
all the drivers involved are open source; also, you wouldn't
need the
source code to sign it, as far as I know; however, doing that will
require your Windows to trust the certificate that signed the
driver,
and that won't work any better for you than it should for e.g. an
arbitrary program running on your PC that tries to install a driver
they
actually shouldn't be allowed to install.
So, you need some certificate that Microsoft trusts, use that to
sign
your driver's signing, etc.
As Martin said, working on that for the WinUSB driver, being able to
use
NI's ressources. It's just not production-ready yet.
I'm a bit surprised it stopped working, because, well, there's
people
who actually need to develop drivers... but nevertheless, yes,
having
a signed driver is pretty much what you'd want. (No, actually, what
you'd want is for Windows to have a "normal" USB stack like any
other
serious desktop OS out there, where you don't need to install a
driver
for generic USB devices that just offer bulk transfer packets to
userland, but that's a rant for another day ;) ).
Best regards,
Marcus
On Tue, 2016-02-09 at 02:52 +0000, d.des wrote:
This must have worked at one time, but it seems to have been
disabled
with recent Windows 10 updates. I am using a brand-new
computer with
the latest updates applied. There are also some other tricks
involving
"bcdedit" incantations that worked on W10 preview don't do anything
on
the most recent release either. The right answer is for Ettus to
release a signed driver, which they say they are working on. I
hope
that the process on their end isn't too involved since the
issue will
expand as people accept the Windows 10 update that is being widely
pushed.
Another solution might be for the driver to be released in source
form,
if there is a way for a user to self-sign code that he compiles
himself. I'd take either one at this point.
Hi
You can install unsigned drivers in Windows 10. Just follow the
instruction from this link:
http://www.howtogeek.com/167723/how-to-
dis
able-driver-signature-verification-on-64-bit-windows-8.1-so-that-
you-
can-install-unsigned-drivers/
Basically, you need to reboot your system with deactivated signed
driver check.
Regards,
_______________________________________________
USRP-users mailing list
USRP-users@lists.ettus.com <mailto:USRP-users@lists.ettus.com>
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
USRP-users mailing list
USRP-users@lists.ettus.com
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
On 02/09/2016 10:34 AM, Marcus D. Leech via USRP-users wrote:
Another issue is a philosophical/chain-of-custody type thing. WinUSB
isn't written by Ettus, but is packaged as a convenience for Windows
users. In the best of all possible worlds, that driver would be
signed by the folks who provide and package WinUSB. Although I guess
that if it's being compiled-from-source, Ettus has no choice but to
sign the result.
Well, it turns out, I'm misinformed. It's just the .inf file that is
at issue, and not the WinUSB package itself. Which negates all my
comments above.
On Tue, Feb 9, 2016 at 6:48 AM, Marcus Müller
<usrp-users@lists.ettus.com mailto:usrp-users@lists.ettus.com> wrote:
I'm stuck with Windows on this application. I don't know how general
your driver is, but maybe once it's accepted by Windows it will
effectively provide that "normal" USB stack functionality.
Yeah, that's exactly what WinUSB does: give you access to the raw
bulk
transfers; again, the problem is that Windows "expects" a driver for
every single new USB device ID; hence you can't say "hi, I'm a
userland
program, I'd like to talk to this and that device using the general
driver"; you need to "register" a driver for that PID/VID combo...
Best regards,
Marcus
On 02/09/2016 03:39 PM, d.des via USRP-users wrote:
I had thought that it was only possible to sign drivers that you
compiled yourself but that might not be the case. The process is
described here:
http://blogs.msdn.com/b/windows_hardware_certification/archive/2015/04/
01/driver-signing-changes-in-windows-10.aspx
https://msdn.microsoft.com/en-us/library/windows/hardware/ff552275%28v=
vs.85%29.aspx
and involves installing a 6.5 GB Windows Driver Kit (or Assessment
Development Kit -- the name changes somewhere in the download link
chain...). I'll attempt it for grins when I get somewhere with
better
internet access and try to set it up and see if I can test-sign
your
driver. The "Bcdedit.exe -set TESTSIGNING ON" command only
allows the
computer to accept your own signature (and constantly reminds
you with
a banner on your screen): you still need the development kit to
sign
the driver package.
I'm stuck with Windows on this application. I don't know how
general
your driver is, but maybe once it's accepted by Windows it will
effectively provide that "normal" USB stack functionality.
Thanks,
Dave
Hi D.Des,
all the drivers involved are open source; also, you wouldn't
need the
source code to sign it, as far as I know; however, doing that will
require your Windows to trust the certificate that signed the
driver,
and that won't work any better for you than it should for e.g. an
arbitrary program running on your PC that tries to install a driver
they
actually shouldn't be allowed to install.
So, you need some certificate that Microsoft trusts, use that
to sign
your driver's signing, etc.
As Martin said, working on that for the WinUSB driver, being
able to
use
NI's ressources. It's just not production-ready yet.
I'm a bit surprised it stopped working, because, well, there's
people
who actually need to develop drivers... but nevertheless,
yes, having
a signed driver is pretty much what you'd want. (No, actually, what
you'd want is for Windows to have a "normal" USB stack like any
other
serious desktop OS out there, where you don't need to install a
driver
for generic USB devices that just offer bulk transfer packets to
userland, but that's a rant for another day ;) ).
Best regards,
Marcus
On Tue, 2016-02-09 at 02:52 +0000, d.des wrote:
This must have worked at one time, but it seems to have been
disabled
with recent Windows 10 updates. I am using a brand-new
computer with
the latest updates applied. There are also some other tricks
involving
"bcdedit" incantations that worked on W10 preview don't do
anything
on
the most recent release either. The right answer is for Ettus to
release a signed driver, which they say they are working on.
I hope
that the process on their end isn't too involved since the
issue will
expand as people accept the Windows 10 update that is being widely
pushed.
Another solution might be for the driver to be released in source
form,
if there is a way for a user to self-sign code that he compiles
himself. I'd take either one at this point.
Hi
You can install unsigned drivers in Windows 10. Just follow the
instruction from this link:
http://www.howtogeek.com/167723/how-to-
dis
able-driver-signature-verification-on-64-bit-windows-8.1-so-that-
you-
can-install-unsigned-drivers/
Basically, you need to reboot your system with deactivated signed
driver check.
Regards,
_______________________________________________
USRP-users mailing list
USRP-users@lists.ettus.com <mailto:USRP-users@lists.ettus.com>
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
USRP-users mailing list
USRP-users@lists.ettus.com
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
USRP-users mailing list
USRP-users@lists.ettus.com
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
Hi Marcus,
WinUSB is supplied by Windows. Ettus will only be signing the portion
specific to the USB USRPs.
On Tue, Feb 9, 2016 at 7:34 AM, Marcus D. Leech via USRP-users <
usrp-users@lists.ettus.com> wrote:
On 02/09/2016 10:26 AM, Derek Kozel via USRP-users wrote:
Hello Dave,
I am working on this driver signing issue and as you may imagine, the
process is more of a procedural one than a technical one. As soon as the
process is complete we'll be releasing them. It's well understood that this
is needed on recent versions of Windows.
In the meanwhile the process described in the post linked above, and
below, has worked for many people. If it has recently stopped working for
Windows 10 then that is very unfortunate.
Regards,
Derek
Another issue is a philosophical/chain-of-custody type thing. WinUSB
isn't written by Ettus, but is packaged as a convenience for Windows
users. In the best of all possible worlds, that driver would be signed
by the folks who provide and package WinUSB. Although I guess
that if it's being compiled-from-source, Ettus has no choice but to sign
the result.
On Tue, Feb 9, 2016 at 6:48 AM, Marcus Müller usrp-users@lists.ettus.com
wrote:
I'm stuck with Windows on this application. I don't know how general
your driver is, but maybe once it's accepted by Windows it will
effectively provide that "normal" USB stack functionality.
Yeah, that's exactly what WinUSB does: give you access to the raw bulk
transfers; again, the problem is that Windows "expects" a driver for
every single new USB device ID; hence you can't say "hi, I'm a userland
program, I'd like to talk to this and that device using the general
driver"; you need to "register" a driver for that PID/VID combo...
Best regards,
Marcus
On 02/09/2016 03:39 PM, d.des via USRP-users wrote:
I had thought that it was only possible to sign drivers that you
compiled yourself but that might not be the case. The process is
described here:
http://blogs.msdn.com/b/windows_hardware_certification/archive/2015/04/
01/driver-signing-changes-in-windows-10.aspx
https://msdn.microsoft.com/en-us/library/windows/hardware/ff552275%28v=
vs.85%29.aspx
and involves installing a 6.5 GB Windows Driver Kit (or Assessment
Development Kit -- the name changes somewhere in the download link
chain...). I'll attempt it for grins when I get somewhere with better
internet access and try to set it up and see if I can test-sign your
driver. The "Bcdedit.exe -set TESTSIGNING ON" command only allows the
computer to accept your own signature (and constantly reminds you with
a banner on your screen): you still need the development kit to sign
the driver package.
I'm stuck with Windows on this application. I don't know how general
your driver is, but maybe once it's accepted by Windows it will
effectively provide that "normal" USB stack functionality.
Thanks,
Dave
Hi D.Des,
all the drivers involved are open source; also, you wouldn't need the
source code to sign it, as far as I know; however, doing that will
require your Windows to trust the certificate that signed the driver,
and that won't work any better for you than it should for e.g. an
arbitrary program running on your PC that tries to install a driver
they
actually shouldn't be allowed to install.
So, you need some certificate that Microsoft trusts, use that to sign
your driver's signing, etc.
As Martin said, working on that for the WinUSB driver, being able to
use
NI's ressources. It's just not production-ready yet.
I'm a bit surprised it stopped working, because, well, there's people
who actually need to develop drivers... but nevertheless, yes, having
a signed driver is pretty much what you'd want. (No, actually, what
you'd want is for Windows to have a "normal" USB stack like any other
serious desktop OS out there, where you don't need to install a driver
for generic USB devices that just offer bulk transfer packets to
userland, but that's a rant for another day ;) ).
Best regards,
Marcus
On Tue, 2016-02-09 at 02:52 +0000, d.des wrote:
This must have worked at one time, but it seems to have been disabled
with recent Windows 10 updates. I am using a brand-new computer with
the latest updates applied. There are also some other tricks
involving
"bcdedit" incantations that worked on W10 preview don't do anything
on
the most recent release either. The right answer is for Ettus to
release a signed driver, which they say they are working on. I hope
that the process on their end isn't too involved since the issue will
expand as people accept the Windows 10 update that is being widely
pushed.
Another solution might be for the driver to be released in source
form,
if there is a way for a user to self-sign code that he compiles
himself. I'd take either one at this point.
Hi
You can install unsigned drivers in Windows 10. Just follow the
instruction from this link: http://www.howtogeek.com/167723/how-to-
dis
able-driver-signature-verification-on-64-bit-windows-8.1-so-that-
you-
can-install-unsigned-drivers/
Basically, you need to reboot your system with deactivated signed
driver check.
Regards,
USRP-users mailing list
USRP-users@lists.ettus.com
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
USRP-users mailing list
USRP-users@lists.ettus.com
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
USRP-users mailing listUSRP-users@lists.ettus.comhttp://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
USRP-users mailing list
USRP-users@lists.ettus.com
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com