FORScan Adapter Not Found / Can’t Connect: COM Port Fix
You plugged the adapter in, opened FORScan, hit connect, and got “Adapter not found”, “Cannot connect to adapter”, or a spinner that never finishes. It is one of the most common FORScan problems, and it is almost always fixable in a few minutes. This guide walks through the fixes in the order that actually works: ignition and cable first, FORScan Auto settings second, COM port third, and drivers only if Windows did not handle them on its own.
I’m Henry, and I write the guides here. Everything below assumes you got FORScan from the official site, forscan.org. Forscan.com does not host or offer FORScan downloads, and you should not install it from anywhere else.
What “adapter not found” usually means
FORScan talks to your Ford through two links: laptop to adapter (USB, Bluetooth, or Wi-Fi), and adapter to vehicle (the OBD-II port and the CAN buses behind it). “Adapter not found” or “Cannot connect to adapter” means the first link failed. FORScan could not open the port, or it opened a port and nothing answered like an adapter.
That is different from messages like “Cannot connect to vehicle” or “Adapter not compatible”. If FORScan sees the adapter but cannot reach modules, the problem is the second link: ignition, bus, or the adapter itself. If you see a compatibility warning, read FORScan Warning: Adapter Not Compatible? Don’t Panic instead.
The usual causes, roughly in order of how often I see them:
- The adapter is not getting power or the cable is loose (many adapters power from the OBD port, not USB).
- FORScan is pointed at the wrong COM port or the wrong connection type.
- Another program (or a second FORScan window) already has the port open.
- A cheap clone adapter that does not respond properly to FORScan.
- A driver that did not install, which is less common on current Windows than most forums suggest.
Quick checklist before you change anything
Run through this first. It solves most cases without touching a single setting.
- Ignition on. Key in RUN (or push-button start pressed twice without the brake), engine off is fine. Most adapters only power up from the OBD-II port.
- Adapter fully seated. Push it firmly into the OBD-II port under the dash. Check its LED. No light usually means no power.
- Cable and USB port. Plug directly into the laptop, not a hub. Try a different USB port. Wiggle-test the cable.
- HS/MS-CAN switch (switched ELM327 only). If you use a switched ELM327 like the OHP ELM327, set the switch to HS-CAN for the first connection. Many modules are on HS-CAN, and the wrong position can make the scan fail.
- Close other software. Shut down other OBD apps, serial monitors, or a second FORScan instance that may hold the port.
- Use FORScan Auto settings first. See the next section.
Start with FORScan Auto settings
Before you pick a COM port by hand, let FORScan find the adapter itself. In FORScan, open Settings → Connection and set the connection type and port to Auto. Save, close the settings, and press the connect button (the plug icon) again with the ignition on.
Auto mode scans the available ports and probes them for an adapter. With a well-built adapter on a clean Windows install, Auto just works, and you never need to know which COM number Windows assigned. If Auto finds the adapter, stop here. Do not change anything else.
If Auto still reports adapter not found after one or two tries (with ignition on and the checklist done), move to manual COM selection.
COM port: find it in Device Manager and set it manually
USB adapters show up in Windows as a virtual serial port, usually called “USB Serial Port (COMx)” or something similar. Bluetooth adapters on Windows can also create COM ports. Here is how to find the right one:
- Plug in the adapter (ignition on is fine, but not required for this step).
- Right-click the Start button and open Device Manager.
- Expand Ports (COM & LPT).
- Look for the entry that appears when you plug the adapter in and disappears when you unplug it. Note its COM number, for example COM4.
- In FORScan, go to Settings → Connection, set the connection type to COM/FTDI (for USB), and pick that exact COM port. Save and connect again.
A few things worth knowing:
- The COM number can change. Plugging into a different USB port can give the adapter a new COM number. If it worked yesterday and not today, check Device Manager again, or go back to Auto.
- Several COM ports listed? Bluetooth often adds two “Standard Serial over Bluetooth link” ports. Built-in modems and docks add others. The unplug test above is the quickest way to find the adapter’s port.
- Yellow warning icon? That points to a driver problem. See the next section.
- Nothing appears at all when you plug in? Try another cable and USB port before blaming drivers. A dead cable looks exactly like a missing driver.
Drivers: let Windows handle it first
Most forum advice jumps straight to “install the FTDI driver”. In practice, that is rarely the first fix on Windows 10 or 11.
Adapter makers rarely build their own USB chip. Inside, most USB OBD adapters use a standard USB-to-serial bridge from one of a few vendors: FTDI, Silicon Labs CP210x, or WCH CH340. Windows Update already knows these chips and usually installs the driver automatically the first time you plug the adapter in. Give it a minute with the laptop online, then check Device Manager.
Only if the device still shows a yellow warning icon, or appears under “Other devices” with no COM port, should you install a driver yourself:
- In Device Manager, right-click the device and choose Update driver → Search automatically. This often fixes it.
- If that fails, check the adapter maker’s support page for the chip they use, or open the device properties to see the hardware ID. Then get the driver directly from the chip vendor (FTDI, Silicon Labs, or WCH), not a random download site.
- Unplug, replug, and confirm a COM port now appears under Ports (COM & LPT). Then go back to FORScan Auto.
Do not install several driver packages “just in case”. Conflicting drivers cause more connection problems than they solve.
Adapter quality matters more than settings
If you have done all of the above and the adapter still is not found, or it connects one minute and drops the next, the adapter is often the real problem. Many cheap ELM327 clones on the market respond badly to FORScan, have unreliable firmware, or cannot reach MS-CAN at all.
To be honest about the options:
- OBDLink EX (USB) and OBDLink MX+ (Bluetooth) are the full-function picks. They switch between HS-CAN and MS-CAN automatically, so FORScan can reach all supported modules without you flipping anything. If you want the fewest connection headaches, this is where to look.
- OHP ELM327 is the budget pick. It is USB only and has a manual HS/MS-CAN switch, so you flip it when FORScan asks. It works with FORScan on Windows, but it is not as hands-off as the OBDLink adapters.
For a full comparison, see Best FORScan Adapters for 2026. If you are not sure whether you need USB or Bluetooth for your laptop or phone, start with Which FORScan adapter do I need?
A note on licenses and the trial
A license does not cause “adapter not found”. That error happens before FORScan even reaches the vehicle. But once you are connected, keep this in mind: full FORScan functionality needs both a paid Extended license and a fully compatible adapter. The trial might not be 100% functional, so if a specific function does not behave as expected on the trial, that may be a license limit rather than a connection fault. See the FORScan license guide for what the Standard and Extended licenses cover. Get licenses only from forscan.org.
Still stuck? Related guides
- Start here: the safe first-session order for new FORScan users.
- How to install FORScan on Windows: a clean install from the official site.
- Which FORScan adapter do I need?: match the adapter to your device.
- Best FORScan Adapters for 2026: EX, MX+, and OHP compared.
- Adapter not compatible warning: what that message really means.
FAQ
Why does FORScan say adapter not found?
Usually the adapter has no power (ignition off or loose plug), FORScan is looking at the wrong port, or another program has the port open. Turn the ignition on, reseat the adapter, close other OBD apps, and set FORScan’s connection to Auto before changing anything else.
Should I set the COM port manually in FORScan?
Only if Auto fails. Set Settings → Connection to Auto first. If it still cannot find the adapter, open Device Manager, note the COM number under Ports (COM & LPT), set the connection type to COM/FTDI, and pick that port.
Do I need to install a driver for my FORScan USB adapter?
Usually not. Most USB adapters use a standard FTDI, CP210x, or CH340 chip, and Windows normally installs the driver automatically. Only install a driver from the chip vendor if Device Manager shows a warning icon or no COM port.
Which adapter gives the fewest connection problems?
The OBDLink EX (USB) and OBDLink MX+ (Bluetooth) are the full-function picks with automatic HS/MS-CAN switching. The OHP ELM327 is a budget USB-only option with a manual HS/MS-CAN switch.
As an Amazon Associate, Forscan.com earns from qualifying purchases. Adapter links above are affiliate links. Full disclosure.
