Forum Discussion
I was able to install the drivers. You first have to disable driver signature enforcement. This is the sequence:
1 - Go to windows 10 settings and search for "advanced startup options" 2 - Under Advanced startup, hit "Restart now" 3 - After a moment, you'll get a "choose an option" screen - choose "Troubleshoot", then "Advanced options", then "Startup Settings" 4 - You'll get a screen telling you what you will be able to change and a single "Restart" button - press it. 5 - If your boot drive is BitLocker encrypted, you'll need to enter the recovery key (press return, enter the key in the text box then hit return again - it took me three goes to realize I had to hit return before I could enter they key !) 6 - You'll be given a menu of options, number 7 disables driver signature enforcement 7 - When the PC restarts, use Device manager to update the drivers - this time you'll get a warning about the signature, but they install fine. 8 - When you've finished, restart normally to re-enable signature enforcementYep, that worked for me. Thanks! Glad to hear Intel is lazy like my little company in not getting their drivers registered with Microsoft!
- fdsa985 years ago
New Contributor
I'm having no luck installing drivers for a DE10-Lite demo board on windows 10.
I've tried two computers and both end with the exact same message:
"Windows found drivers for your device but encountered an error while attempting to install them", "A problem was encountered while attempting to add the driver to the store".
I tried one option for eliminating driver signing (command line) and tried the advanced restart settings suggestion above but that ended with a bricked computer and a call to IT to get a bitlocker key. I'm not trying it again.
Are there any updates to this problem?
- Fancellu5 years ago
New Contributor
2021, this is still the case. Astonishing that they ship drivers that will simply not work for 99% of win10 users
The drivers in Quartus 20.1 are unsigned
I attach screenshot of what my Windows 10 says
Doesn't even complain about hash, just says no.
Had to turn off driver signing enforcement, then worked fine via JTag- fdsa985 years ago
New Contributor
Yep that's exactly the message I get.
Specifically how did you disable driver signing?