Forum Discussion
https://www.technipages.com/enable-disable-device-driver-signing
Option 2.
When you install driver after that, it will warn you and ask if you are sure.
I even went and bought another USB Blaster, thinking that mine was faulty!
Thanks Intel!!!
Did you try option 1?
I tried both. The first didn't seem to work though I'll try again. The second bricked my computer. If you have an encrypted drive you need the encryption key to use option 2. IT fixed it but I'm not doing it again.
- TScho165 years ago
New Contributor
I had the same problem. Finally, i solved it by installing a driver of a previous Quartus version. I used the driver of the following site:
http://www.terasic.com.tw/wiki/File:Usb_blaster_q16.1.zip
The site is linked here:
http://www.terasic.com.tw/wiki/Altera_USB_Blaster_Driver_Installation_Instructions
- Fancellu5 years ago
New Contributor
Option 1 did nothing for me
I don't have an encrypted drive for Option 2 was fine, for me
Of course the real answer is for Intel to release proper signed s/w
If I'd paid for Quartus and couldn't get it working because of broken drivers I'd be furious
Maybe see if you can get a human from Intel to help
https://www.intel.com/content/www/us/en/programmable/support/support-resources.html - Depka5 years ago
New Contributor
When i completed the Quartus lite 20.1 installation, i got an error in the driver wizard . Can some one help me resolve this? - Fancellu5 years ago
New Contributor
Look back up the thread.
Latest intel usb blaster drivers are not signed.
- Depka5 years ago
New Contributor
I tried using the above drivers but got the same error .
- MRigh45 years ago
New Contributor
After last windows update I have the same problem. Previously the programmer worked fine... now Quartus doesn’t recognize it anymore... My drive requires a key for bitlocker, therefore I’d prefer not to try option 2 (I haven’t tried option 1 since all says that it does not work). Does anyone have another solution? - MRigh45 years ago
New Contributor
Solved, the driver at the link in the post of TScho16 worked fine. Thank you!