Skip to content
English - United States
Contact us
  • There are no suggestions because the search field is empty.

Diagnostic software compatibility: which OEM tools can run on the same computer

Compatibility guide for installing Honda, Ford, Mazda, GM, Nissan, Jaguar/Land Rover, and Chrysler diagnostic software on the same PC. Lists which programs conflict and how to run them all using a 5-partition computer from AETools.

Trying to install multiple OEM diagnostic programs on one computer and running into conflicts? Many automotive diagnostic software packages cannot coexist on the same Windows installation - they share drivers, runtimes, or licensing components that interfere with each other. Here's a breakdown of which diagnostic apps don't run together and what to do if you need all of them.

Why some diagnostic software cannot be installed on the same computer

Several OEM diagnostic programs are built by the same developers (or use overlapping J2534 drivers, .NET runtimes, and database services), which causes conflicts when installed side by side. Symptoms include software that won't launch after a second program is installed, VCI/pass-thru devices no longer being recognized, license activation failures, and database errors after a reboot. The safest fix is to keep conflicting programs on separate Windows installations.

Honda diagnostic software compatibility

Honda i-HDS / HDS cannot be installed on the same computer as:

- Ford IDS
- Ford FJDS
- Ford FDRS
- Nissan Consult 4 (Consult III Plus)
- Mazda IDS
- Mazda MMP (Mazda Modular Programming)
- Mazda MDFSA (Mazda Diagnostic and Flashing Software Application)
- GM SPS / SPS2 (works most of the time, but not recommended alongside Honda)

Ford diagnostic software compatibility

Ford IDS and Ford FJDS cannot be installed on the same computer as each other. This catches shops out because both are Ford products covered by the same subscription. Which one you install depends on the interface you use:

  • Ford IDS — for the Ford VCM2 and VCM3.

  • Ford FJDS — for J2534 pass-thru devices such as the AEZ Flasher 3.

If you have IDS installed and need FJDS, remove IDS first. Installing one over the other produces a corrupted installation that has to be cleaned up before either will run. Symptoms include software that will not launch, a VCI that is no longer recognised, and errors immediately after a Ford update.

FDRS coexists with either one and is unlocked by the same Ford subscription.

Ford IDS, FJDS, and FDRS also cannot be installed on the same computer as:

  • Honda i-HDS

  • Mazda IDS

  • Mazda MMP

  • Mazda MDFSA

  • Jaguar / Land Rover SDD (JLR SDD)

Mazda diagnostic software compatibility

Mazda IDS, MMP, and MDFSA cannot be installed on the same computer as:

- Ford IDS
- Ford FJDS
- Jaguar / Land Rover SDD
- Nissan Consult 4

How to run all of these diagnostic programs on one machine

If you need Honda, Ford, Mazda, Nissan, GM, and Jaguar/Land Rover diagnostic software all in one place, AETools sells dedicated 5-partition diagnostic computers. Each partition is its own isolated Windows installation, so conflicting OEM programs never see each other. Switching between OEMs is just a reboot - it works similar to having 5 different computers in 1.

This is the cleanest solution for shops that service multiple makes and don't want to maintain separate physical laptops for each OEM.

Important notes about diagnostic software compatibility

GM SPS / SPS2 generally installs alongside other software without issue, but is not recommended on a Honda machine. If you only run Honda occasionally, isolating GM to its own partition is still the safer call.

J2534 pass-thru drivers (DrewTech, AEZFlasher, Cardaq, etc.) can usually coexist on the same partition, but the OEM applications that use them often cannot. The conflict is at the application level, not the J2534 driver level.

This list reflects the most common conflicts AETools sees in the field. New software versions occasionally change compatibility - if you're planning a multi-OEM build, contact us first.

Ford VCM1 is not supported after IDS 133.01. A VCM1 that worked on an older IDS version will stop being recognised once IDS is updated to 133.01 or later, and there is no way to restore support on the current version. Shops still running a VCM1 need to move to a J2534 pass-thru with FJDS, or to a VCM2 or VCM3 with IDS. If a VCM1 stopped working immediately after an IDS update, this is why — it is not a driver or installation fault. 

If you need help choosing which OEM diagnostic programs can run together, configuring a multi-partition computer, or troubleshooting a software conflict, contact AETools at https://aetools.us or call us directly.