Bitscope USB connection to Windows

Google suggests the following steps:

• Connect the BS310, press Win + X, and open Device Manager. Locate the unrecognized device under Other devices or Universal Serial Bus controllers (often listed as USB Serial Converter, BitScope, or Unknown Device). Right-click it, select Properties > Details, and choose Hardware Ids from the dropdown.
  Verification: Note the VID_XXXX and PID_XXXX values (standard FTDI is VID_0403; custom BitScope PIDs vary by revision). NOTE. If you do not see anything then the USB device is not working.
• Install the Current Signed FTDI VCP Driver. Download the latest Windows 11 x64 VCP (Virtual COM Port) driver executable directly from FTDI Chip Drivers (version 2.12.36.4 or newer, which is WHQL-signed for Windows 11). Run the installer with administrator privileges so the signed ftdibus.inf and ftdiport.inf packages are added to the Windows Driver Store. Verification: The FTDI CDM Driver Package Installer completes with a green checkmark showing "Ready to use."
• Manually Bind the FTDI Driver to Custom PIDs. If Windows 11 refuses to bind the driver automatically due to a custom BitScope PID, right-click the device in Device Manager and select Update driver > Browse my computer for drivers > Let me pick from a list of available drivers on my computer. Uncheck Show compatible hardware, select FTDI under Manufacturer, and choose USB Serial Converter (ignore any compatibility warning prompt). Repeat this process if a second USB Serial Port entry appears afterward. Verification: The device moves cleanly into Ports (COM & LPT) as USB Serial Port (COMx) with no yellow exclamation mark.
• Adjust Latency Timer and COM Port Number. In Device Manager, expand Ports (COM & LPT), right-click USB Serial Port (COMx), and open Properties > Port Settings > Advanced. Change the COM Port Number to a low value (COM1 through COM4) if legacy BitScope DSO software fails to enumerate high COM numbers, and lower the Latency Timer (msec) from 16 to 1 or 2 to prevent waveform capture timeouts. Verification: Clicking OK saves the port assignment without an "in use" conflict, and BitScope DSO connects when USB and the matching COMx port are selected under SETUP.

If Windows still blocks the setup.

• USB 3.x xHCI Host Controller Timing: Older FTDI USB 1.1/2.0 Full-Speed chips occasionally fail enumeration on modern USB 3.2 Gen 2 root hubs. Plugging the BS310 through an unpowered USB 2.0 hub forces the host controller to negotiate via a Transaction Translator, resolving descriptor read errors.

• Memory Integrity (HVCI) Block: If Device Manager reports Code 39 or Code 52 (driver signature/integrity enforcement), open Windows Security > Device security > Core isolation details and check if Memory integrity is blocking an older ftdibus.sys remnant. Uninstalling all old FTDI entries via pnputil /enum-drivers in an elevated terminal before running the latest FTDI installer resolves driver store conflicts.

The only alternative I could think of is to try a proxy. E.g. Connect via Raspberry Pi.

Good luck.

Google suggests the following steps:

• Connect the BS310, press Win + X, and open Device Manager. Locate the unrecognized device under Other devices or Universal Serial Bus controllers (often listed as USB Serial Converter, BitScope, or Unknown Device). Right-click it, select Properties > Details, and choose Hardware Ids from the dropdown.
  Verification: Note the VID_XXXX and PID_XXXX values (standard FTDI is VID_0403; custom BitScope PIDs vary by revision). NOTE. If you do not see anything then the USB device is not working.
• Install the Current Signed FTDI VCP Driver. Download the latest Windows 11 x64 VCP (Virtual COM Port) driver executable directly from FTDI Chip Drivers (version 2.12.36.4 or newer, which is WHQL-signed for Windows 11). Run the installer with administrator privileges so the signed ftdibus.inf and ftdiport.inf packages are added to the Windows Driver Store. Verification: The FTDI CDM Driver Package Installer completes with a green checkmark showing "Ready to use."
• Manually Bind the FTDI Driver to Custom PIDs. If Windows 11 refuses to bind the driver automatically due to a custom BitScope PID, right-click the device in Device Manager and select Update driver > Browse my computer for drivers > Let me pick from a list of available drivers on my computer. Uncheck Show compatible hardware, select FTDI under Manufacturer, and choose USB Serial Converter (ignore any compatibility warning prompt). Repeat this process if a second USB Serial Port entry appears afterward. Verification: The device moves cleanly into Ports (COM & LPT) as USB Serial Port (COMx) with no yellow exclamation mark.
• Adjust Latency Timer and COM Port Number. In Device Manager, expand Ports (COM & LPT), right-click USB Serial Port (COMx), and open Properties > Port Settings > Advanced. Change the COM Port Number to a low value (COM1 through COM4) if legacy BitScope DSO software fails to enumerate high COM numbers, and lower the Latency Timer (msec) from 16 to 1 or 2 to prevent waveform capture timeouts. Verification: Clicking OK saves the port assignment without an "in use" conflict, and BitScope DSO connects when USB and the matching COMx port are selected under SETUP.

If Windows still blocks the setup.

• USB 3.x xHCI Host Controller Timing: Older FTDI USB 1.1/2.0 Full-Speed chips occasionally fail enumeration on modern USB 3.2 Gen 2 root hubs. Plugging the BS310 through an unpowered USB 2.0 hub forces the host controller to negotiate via a Transaction Translator, resolving descriptor read errors.

• Memory Integrity (HVCI) Block: If Device Manager reports Code 39 or Code 52 (driver signature/integrity enforcement), open Windows Security > Device security > Core isolation details and check if Memory integrity is blocking an older ftdibus.sys remnant. Uninstalling all old FTDI entries via pnputil /enum-drivers in an elevated terminal before running the latest FTDI installer resolves driver store conflicts.

The only alternative I could think of is to try a proxy. E.g. Connect via Raspberry Pi.

Good luck.