<div dir="ltr">It certainly seems that if Secure Boot is off then most problems will be alleviated:<div><br></div><div><a href="http://www.thewindowsclub.com/driver-signing-changes-windows-10">http://www.thewindowsclub.com/driver-signing-changes-windows-10</a></div><div><br></div><div>73,</div><div><br></div><div>Scott<br><div class="gmail_extra"><br><div class="gmail_quote">On Sat, Aug 20, 2016 at 11:20 AM, George Byrkit <span dir="ltr"><<a href="mailto:ghbyrkit@chartermi.net" target="_blank">ghbyrkit@chartermi.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Scott,<br>
This may or may not work on Windows 10. Certainly I am ONLY talking about Windows 10 Build 1607 and later. It is not reasonable to expect a Ham to take a boot-time choice each time they (re)boot their computers. I'm speaking about generally booting a computer. I suggest that you review the article and other related information and make your own conclusion.<br>
<br>
What happens for debugging a driver under development is not relevant to what happens when you use a driver as a normal computer user. I'm telling you that MANY drivers from the past will stop working on Windows 10 at Day 60 (or is it 90) after the release of Windows 10 Anniversary (build 1607), which occurred on August 2, 2016. One of those affected is the Ozy/Magister 'libusb0' USB driver.<br>
<br>
And it is a separate issue if you have Secure Boot enabled in the BIOS of a modern computer. YMMV. Read, be informed, and draw your own conclusions that are relevant to how you use drivers.<br>
<br>
I had not seen a warning about this published on this list. This will affect many pieces of HAM hardware, not just USB devices. It could affect printers, things like MicroHam 'digikeyer' products and the like, and other pieces of hardware.<br>
<br>
73,<br>
George K9TRV<br>
<br>
-----Original Message-----<br>
From: Scott Traurig [mailto:<a href="mailto:scott.traurig@gmail.com">scott.traurig@gmail.<wbr>com</a>]<br>
Sent: Saturday, August 20, 2016 11:07 AM<br>
To: George Byrkit <<a href="mailto:ghbyrkit@chartermi.net">ghbyrkit@chartermi.net</a>><br>
Cc: OpenHPSDR <<a href="mailto:hpsdr@openhpsdr.org">hpsdr@openhpsdr.org</a>><br>
Subject: Re: [hpsdr] Ozy/Magister will likely stop working on Win10 in about 60 days<br>
<br>
George,<br>
<br>
Will this no longer work?<br>
<br>
<a href="http://www.howtogeek.com/167723/how-to-disable-driver-signature-verification-on-64-bit-windows-8.1-so-that-you-can-install-unsigned-drivers/" rel="noreferrer" target="_blank">http://www.howtogeek.com/<wbr>167723/how-to-disable-driver-<wbr>signature-verification-on-64-<wbr>bit-windows-8.1-so-that-you-<wbr>can-install-unsigned-drivers/</a><br>
<br>
<br>
73,<br>
<br>
Scott/w-u-2-o<br>
<br>
<br>
On Sat, Aug 20, 2016 at 10:51 AM, George Byrkit <<a href="mailto:ghbyrkit@chartermi.net">ghbyrkit@chartermi.net</a> <mailto:<a href="mailto:ghbyrkit@chartermi.net">ghbyrkit@chartermi.net</a><wbr>> > wrote:<br>
<br>
<br>
***** High Performance Software Defined Radio Discussion List *****<br>
<br>
Dear all,<br>
<br>
So Microsoft has a policy for double-signed drivers on Windows 10 that didn't exist<br>
before, and it will take place between 60 and 90 days after the release of Windows 10<br>
Anniversary (build 1607).<br>
<br>
The purpose of this is to ensure that the drivers are fully signed and fully trusted, at a<br>
level that is greater than before, in order to be able to load on any computer with Secure<br>
Boot active in the BIOS.<br>
<br>
I won't enter into a debate as to whether this is a good thing or a bad thing. I will<br>
only point out that the Ozy/Magister USB drivers for PowerSDR, KISS Konsole, etc., are NOT<br>
double-signed, and I don't really see a need to do that, and take the time, and spend the<br>
money to do so.<br>
<br>
While the current Ozy/Magister USB driver is single-signed, it is signed with a<br>
certificate that is too old to be able to put the package thru Microsoft to get their<br>
counter-signature. If you want more information, I suggest that you visit<br>
<a href="http://www.osr.com/developers-blog" rel="noreferrer" target="_blank">http://www.osr.com/developers-<wbr>blog</a> <<a href="http://www.osr.com/developers-blog" rel="noreferrer" target="_blank">http://www.osr.com/<wbr>developers-blog</a>> and check the article 'Driver Signing - more details<br>
emerge".<br>
<br>
To do all of this requires a 'code signing certificate' from one of the vendors of such<br>
certificates, apparently with 'EV' (extended validation?) Such seem to cost $200-$400 per<br>
year. Since everything new uses Metis technology (Ethernet), I don't think that it is<br>
worth the cost or the hassle to keep supporting Ozy/Magister on Windows 10. If someone<br>
who wants it to keep working donates the money, there might be a chance to reconsider.<br>
<br>
73,<br>
George K9TRV<br>
<br>
______________________________<wbr>_________________<br>
HPSDR Discussion List<br>
To post msg: <a href="mailto:hpsdr@openhpsdr.org">hpsdr@openhpsdr.org</a> <mailto:<a href="mailto:hpsdr@openhpsdr.org">hpsdr@openhpsdr.org</a>><br>
Subscription help: <a href="http://lists.openhpsdr.org/listinfo.cgi/hpsdr-openhpsdr.org" rel="noreferrer" target="_blank">http://lists.openhpsdr.org/<wbr>listinfo.cgi/hpsdr-openhpsdr.<wbr>org</a> <<a href="http://lists.openhpsdr.org/listinfo.cgi/hpsdr-openhpsdr.org" rel="noreferrer" target="_blank">http://lists.openhpsdr.org/<wbr>listinfo.cgi/hpsdr-openhpsdr.<wbr>org</a>><br>
HPSDR web page: <a href="http://openhpsdr.org" rel="noreferrer" target="_blank">http://openhpsdr.org</a><br>
Archives: <a href="http://lists.openhpsdr.org/pipermail/hpsdr-openhpsdr.org/" rel="noreferrer" target="_blank">http://lists.openhpsdr.org/<wbr>pipermail/hpsdr-openhpsdr.org/</a> <<a href="http://lists.openhpsdr.org/pipermail/hpsdr-openhpsdr.org/" rel="noreferrer" target="_blank">http://lists.openhpsdr.org/<wbr>pipermail/hpsdr-openhpsdr.org/</a><wbr>><br>
<br>
<br>
<br>
<br>
</blockquote></div><br></div></div></div>