Version 90.x (Early 2016) – The first version to issue a warning if you were using a clone or counterfeit VCM II. Ford began embedding digital signatures that would brick clone hardware. This version also added support for the 2017 Super Duty’s 10-speed automatic (10R140).
Version 95.x (Mid-2017) – Dropped support for Windows XP entirely. Windows 7 (64-bit) and Windows 10 became mandatory. This version introduced TCU (Telematics Control Unit) programming – essential for vehicles with FordPass and emergency assist.
Version 100.x (Early 2018) – A celebratory milestone. Version 100 added support for Cybersecurity Keys (SecOC). For the first time, programming certain modules (like the RCM or PCM) required a 12-hour online wait to obtain a security token. This was Ford’s response to rising vehicle hacking concerns.
Version 105.x (Late 2018) – The last version to support Mazda vehicles (Ford-owned era). After 105.x, Mazda diagnostics moved entirely to Mazda’s own IDS variant.
Version 107.x (Mid-2019) – The final major feature update. This version added diagnostic capabilities for electric vehicles (Mustang Mach-E development mules and Ford Focus Electric) and improved hybrid battery balancing procedures. ford ids version history
Version 108.x (Early 2020) – The final release of Ford IDS. Version 108.01 (and subsequent minor builds like 108.05) served only as bug fixes and security patches for existing vehicles. No new features were added.
Around 2005, Ford launched the Integrated Diagnostic System (IDS). The philosophy shifted from dedicated hardware to software running on a standard personal computer.
This era defined the classic image of the dealership mechanic: a Panasonic Toughbook strapped to a rolling cart, wired into the vehicle.
Note: During this era, Ford introduced J2534 passthru capabilities, allowing independent shops to use the IDS software (often via a VCM II) for module programming, breaking the dealership monopoly on certain repairs. Version 90
Currently, a Ford technician does not just use "IDS." They navigate a "Triangle" of software depending on the vehicle in the bay:
As vehicles became more complex, the hardware needed to keep up. Ford released the VCM II, replacing the metal brick with a sleek, black plastic device.
For professional use on 2004–2019 Fords with a genuine VCM II/VCM III, the last stable version is v107.06 (or v110.x if you need minor bug fixes). For anything newer, you must use FDRS.
Would you like a breakdown of FDRS version history or a comparison between IDS and FDRS? Note: During this era, Ford introduced J2534 passthru
This was intended to replace IDS for module programming and diagnostics on newer vehicles. It was a lighter, faster software designed to work strictly with J2534 devices (eliminating the need for the expensive VCM hardware). While fast, it initially lacked some of the advanced data logging features of the classic IDS.
When IDS first appeared around 2004, it replaced the older World Diagnostic System (WDS) and the even more primitive New Generation Star (NGS) tester. Early IDS (v1.0 to v20.0) was a creature of the early 2000s: clunky, icon-driven, and running on ruggedized Dell laptops with Windows XP. Its genius was modularity—for the first time, a single software package could talk to the PCM (engine), ABS (brakes), and the new, nervous GEM (Generic Electronic Module).
Version 14.0 (circa 2008) was a watershed moment. With the launch of the 2008 Ford Flex and Lincoln MKS came the introduction of Networked Vehicle Architecture. Suddenly, modules could talk to each other. IDS 14.0 introduced the "Network Test," a terrifyingly powerful tool that could map the entire car’s CAN bus. For technicians, this was the shift from fixing broken wires to diagnosing missing messages.
Before IDS became the standard, Ford technicians relied on the WDS (Worldwide Diagnostic System). Introduced in the late 1990s and early 2000s, the WDS was a standalone unit often recognizable by its ruggedized "blue box" design and a monochrome or early color touch screen.
While revolutionary for its time—allowing technicians to access modules beyond the engine and transmission—the WDS had limitations. Updates were slow, requiring the purchase of compact discs or flash cards, and the hardware was expensive and bulky.