USB Blaster conflicts with other FTDI devices result in PC crash

**Hello David,**

Thank you for the detailed report — this is a **very well-known and frustrating issue** that has affected many engineers using the original **USB-Blaster** (Altera/Intel first-generation programmer) alongside other FTDI-based devices.

Let me give you a clear summary of the situation, the root cause, and the realistic options in 2026.

### Root Cause – Summary

The original USB-Blaster uses an **FT2232D** chip (same as many of your other FTDI devices).

Altera/Intel released a **custom driver** (version 2.12.28.0) many years ago that **intentionally conflicts** with the official FTDI drivers to prevent Windows from loading the generic FTDI driver on the USB-Blaster (which would break JTAG functionality).

When Windows Update pushes the **latest official FTDI driver (2.12.36.20 or newer)**:

- It detects all FTDI devices (including your FT2232D, FT4232HL, FT232R products).

- It tries to update **all** of them — including the USB-Blaster.

- The old Altera driver (2.12.28.0) is still installed → **driver conflict** → **BSOD (Blue Screen of Death)**.

This has been reported since ~2018–2019 and is still happening in 2026 because:

- Intel **never updated** the USB-Blaster driver after ~2015.

- FTDI keeps releasing new drivers (security/bug fixes), triggering Windows Update.

### Your Workaround is Correct & Common

Uninstalling the Altera/Intel driver (2.12.28.0) **before** letting Windows Update apply the new FTDI driver is the standard workaround used by thousands of engineers.

After the update finishes:

→ Re-install the old Altera driver (from Quartus installer or standalone package).

→ USB-Blaster works again.

**The bad news**:

Every time FTDI releases a new driver version (and Windows pushes it), the same crash cycle **will repeat**. This is not going away unless you block Windows Update for FTDI drivers permanently (possible but not recommended for security).

### Best Long-Term Solutions in 2026

1. **Switch to USB-Blaster II (recommended)**

- Intel **USB-Blaster II** (part # USB-Blaster II) uses a **different USB chip** (not FTDI) → **no driver conflict** with modern FTDI devices.

- Fully supported in current Quartus Prime (Lite/Pro/Standard).

- Much faster programming speed.

- Price: ~$300–400 (official), or ~$50–100 for good clones (widely available in China/HK).

- Drawback: Official one is expensive; clones work fine for most users but may have reliability issues.

2. **Use a Third-Party Programmer (Best Value)**

- **Terasic USB-Blaster** (clone but high quality) or **JTAG Blaster** from other vendors.

- **Segger J-Link** (with JTAG adapter) — very reliable, no FTDI conflict, supports many FPGAs/CPLDs.

- **Olimex ARM-USB-OCD-H** or **Tigard** (FTDI-based but with newer drivers that play nicer).

3. **Permanent Workaround (Block FTDI Driver Updates)**

- Use **Windows Device Installation Control** or **Group Policy** to block driver updates for specific Hardware IDs.

- Hardware IDs of your USB-Blaster (FT2232D):

- VID_09FB & PID_6001 or PID_6002 (Altera signature)

- Tools like **wushowhide.diagcab** (Microsoft) or third-party tools like **Driver Store Explorer (RAPR)** can hide the FTDI driver update.

- This stops the crash but means you stay on the old FTDI driver forever (security risk).

4. **Other Minor Annoyance Fix (Multiple FTDI Devices)**

- The old USB-Blaster driver is **very aggressive** and sometimes grabs other FTDI devices.

- Solution: After installing Altera driver, go to Device Manager → right-click other FTDI devices → **Update driver** → **Browse my computer** → select the **official FTDI driver folder** → force it back.

- Or use **zadig** tool (libusb driver) for non-critical FTDI devices.

### Final Recommendation (2026 Reality)

- **Short-term**: Keep using your current workaround (uninstall Altera driver → update → reinstall). It will keep working.

- **Long-term**: **Replace the original USB-Blaster** with USB-Blaster II (official or good clone).

This completely eliminates the conflict and gives you a modern, supported programmer.

The original USB-Blaster is 15–20 years old — it's time to retire it.

If you want, I can help you find a reliable USB-Blaster II clone supplier in Hong Kong/China or give you exact steps for blocking driver updates.

Alternatively, you can visit www.aceicc.com and seek their advice; I got a good answer from them last time.