I downloaded the WDK and SDK and followed the instructions in  https://msdn.microsoft.com/en-us/library/windows/hardware/ff546236.aspx and am now able to use the B210 in Windows 10.  It's been a learning experience. Here are the specific command lines that need be typed into an administrator command prompt: cd C:\Program Files (x86)\Windows Kits\10\bin\x86 makecert -r -pe -ss PrivateCertStore -n CN=Contoso.com(Test) ContosoTest.cer inf2cat /driver:\Users\me\Downloads\erllc_uhd_winusb_driver\erllc_uhd_winusb_d river\ /os:10_X64 Signtool sign /v /s PrivateCertStore /n Contoso.com(Test) /t http://tim estamp.verisign.com/scripts/timstamp.dll C:\Users\me\Downloads\erllc_uhd_winusb_driver\erllc_uhd_winusb_driver\ usrp_b200.cat Signtool verify /pa /v /c C:\Users\me\Downloads\erllc_uhd_winusb_driver\erllc_uhd_winusb_driver\ usrp_b200.cat C:\Users\me\Downloads\erllc_uhd_winusb_driver\erllc_uhd_winusb_driver\ erllc_uhd_b200_reinit.inf certmgr.exe /add ContosoTest.cer /s /r localMachine root 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. > >