USB-BlasterII mounts as "USB-Blaster variant"

 Hello!  My company uses the USB-BlasterII pods with Quartus.  Many times, when the Blaster is plugged in, it is detected by Quartus as "USB-Blaster variant" instead of "USB-BlasterII".  When this happens, the JTAG clock frequency is not settable, and the pod will not operate correctly.  The problem occurs equally with Quartus Prime 16.1 and Quartus Standard 24.1.  I have not tried other versions of Quartus.

This appears to be the same root issue that AdamLevine experienced in a previous Altera forum post: USB Blaster II | Altera Community.

To answer the questions he was asked,

1. Yes, we experience this issue on all the PCs we have tried the USB-BlasterII on.  My company is running Windows 11.
2. We tried numerous boards, but similar to Adam, the problem occurs whether a board is connected to the Blaster or not.  The issue appears to be with the driver for the Blaster and how it is detected when it is connected to the PC.
3. This problem has been occurring more lately than it used to, but we have had significant failure rates with this for the past two years almost.
4. I know our JTAG pin connections are correct because the USB-BlasterII works perfectly IF AND ONLY IF it is detected with the correct device name but cannot work at all if it shows up with the wrong name in Quartus.

Our conclusion is that the drivers for the USB-BlasterII have a problem.  I suspect that the driver caches the Blaster devices that have been connected and encounters an error if the cache is not cleared by ejecting all the Blaster devices.  Just a guess.  

Has anyone found the issues with the drivers?  Is anyone from Intel available to look into this behavior?  If not, would Intel supply my corporation with the driver source code so our engineers can fix it? 

Thanks!