What should I do if the USB blaster is not displayed in Device Manager?

The immediate priority when a USB Blaster is not displayed in Device Manager is to systematically eliminate the most common points of failure in the hardware-to-software detection chain, beginning with physical connectivity and power. The USB Blaster, a JTAG programming cable for Altera (now Intel FPGA) and some other devices, requires a specific driver to enumerate correctly. Its absence from Device Manager entirely, as opposed to appearing with an error icon, strongly indicates a fundamental failure in device recognition by Windows. This typically points to a physical layer issue, such as a faulty USB cable or port, insufficient power delivery from the USB host, or a defective Blaster unit itself. The first diagnostic step is to try every other USB port on the computer, preferably a direct motherboard port rather than one on a hub or docking station, while also testing with a known-good, high-quality USB cable if the design permits cable swapping. Checking whether the target board is powered, if required by the specific Blaster model, is also critical, as some variants draw power or receive a detection signal from the target.

If basic hardware troubleshooting fails, the focus must shift to driver management and system state. A completely missing entry suggests the operating system either cannot identify the hardware ID or has a profound driver conflict. You should navigate to the "View" menu in Device Manager and select "Show hidden devices." If the USB Blaster then appears, it indicates a previous installation is in a disconnected state and should be uninstalled, after which a rescan for hardware changes or a replug may trigger a fresh detection. Crucially, the official USB Blaster driver from Intel often requires manual installation through the Windows "Add legacy hardware" wizard in the Device Manager, not via a simple executable. The driver files (`.inf`, `.sys`) are typically located within the Quartus Prime installation directory. During this process, if Windows presents a security warning about an unsigned driver, you must allow the installation to proceed for the hardware to function.

The software environment itself can be a culprit, particularly with modern Windows versions and security software. Disabling driver signature enforcement temporarily, especially for older USB Blaster versions, may be necessary for a successful installation. Furthermore, conflicts with other JTAG or USB-serial drivers, or residual entries from previous installations, can block detection. Using a utility like USBDeview to completely remove all traces of any Altera or Intel USB Blaster devices before a reboot and reinstallation can resolve these ghosted conflicts. It is also worth verifying that the specific USB Blaster model is supported by your version of the Quartus Prime or Quartus II software; an outdated driver suite may not recognize newer hardware, and vice versa.

When all standard troubleshooting is exhausted, the implication is a deeper incompatibility or hardware fault. Testing the USB Blaster on a different computer with a known-good driver installation is the definitive test to isolate the problem to the host system or the cable unit itself. On the original host, investigating Windows system logs for USB enumeration errors can provide technical clues. For persistent system-level issues, creating a new, clean Windows user profile or performing a clean boot to eliminate software conflicts are last-resort measures before concluding the hardware is faulty. The process is inherently diagnostic, where each step rules out a specific segment of the path from the FPGA toolchain to the physical silicon.