Ford IDS FDRS - Official OBD2 Diagnostic & Programming 132.04

Emotor said:

Thanks!

Click to expand...

Let me address the multiple questions here:

Regarding the "IDS_Patch" / "not found device or liсеnsе" error

The раtсh files included in the 132.04 package (раtсh 1.1.3.1 and раtсh 1.1.3.6) are device-specific — they look for a connected VCM II or compatible VCI interface. If you're getting "install vcx driver first" or "not found device or liсеnsе," it means:

• The раtсh is designed for a specific hardware type (VCM II / VCM3 / VXDiag)
• Your VCI driver is not installed, or the device is not connected/detected when you run the раtсh
• You need to install the VCI driver first, connect your interface, and then run the раtсh

Make sure VCISoftware1.0.1.18.exe is installed and your device shows up in Device Manager before running the раtсh.

Regarding Windows 10 32-bit

This is likely your main problem. Ford IDS 132.x and the associated patches are 64-bit only. The system requirements specify Windows 10 64-bit. On a 32-bit system:

• The IDS installer itself may complete (some components are 32-bit legacy), but the раtсh/activation tools are compiled as 64-bit executables — they simply won't run on a 32-bit OS
• This explains why IDS installs and opens (asking for liсеnsе) but the раtсh does nothing and IDS won't launch after patching
• There is no 32-bit version of the current patches available in this package

Your options:

• Upgrade to Windows 10 64-bit (if your netbook hardware supports it — most CPUs from 2010+ are 64-bit capable even if the OS installed is 32-bit)
• Use an older IDS version (pre-130) that had 32-bit support with older patches — but coverage will be limited
• Use a different machine for diagnostics

Regarding "IDS-Activation" vs the two раtсh files

To clarify the naming confusion:

• IDS-Activation.exe = referenced in the README of the 132.03 update package (earlier version of the resource)
• раtсh 1.1.3.1 / раtсh 1.1.3.6 = the activation tools included in the latest 132.04 collection

They serve the same purpose (bypassing liсеnsе/login), just different versions. Use 1.1.3.6 (the newer one) with IDS 132.x. But again — 64-bit Windows is required.

Hi,

Thanks for your reply. In fact I managed to install and run 131 version on 31bit. I can run it no problem but aaking for liсеnsе. And patches can run/open and no driver issues on 32bit. But then nothing happens after that. So, a раtсh for 32bit could easily be done. It is a раtсh issue. So, if someone could create a 32bit раtсh. I know all systems are 32bit now on but would be no time for someone to create a 32bit version if 64bit versions. I use old 31bit netbook for diagnostics even though I have a new 64bit comouter because easier to move. And old netbook does not support 64bit.

So, only 130 and earlier support 32bit? If I try run version 129 on 32bit it does not allow me to run because it says it is too old.

So, if someone could create 32bit versions of the patches? They run on 32bit but then IDS does not open at all. Could be just that files to be patched are only located elsewhere on 32bit.

Aris said:

So, if someone could create 32bit versions of the patches? They run on 32bit but then IDS does not o...

Click to expand...

Unfortunately, creating a 32-bit раtсh is not something that can be done as a simple request here — it requires reverse engineering the specific liсеnsе check mechanisms in the 32-bit IDS binaries, which is a completely different task from the existing 64-bit patches.

Here's the situation:

Why the раtсh "runs" but doesn't work on 32-bit:

The раtсh executable itself may be 32-bit compatible (so it launches), but it's targeting specific 64-bit DLLs/binaries in the IDS installation. On a 32-bit install, IDS uses different binary files in different locations. So the раtсh runs, finds nothing to modify (or modifies the wrong files), and IDS either won't launch or still asks for a liсеnsе.

Regarding IDS 129 saying "too old":

That's a calibration/subscription expiry message, not an OS compatibility issue. Older IDS versions check the date and refuse to run if they consider themselves expired. This is a separate protection that also needs patching.

Your realistic options:

• Check if your netbook CPU supports 64-bit — many Atom N-series (N270, N280) are 32-bit only, but N450/N455/N2600 and later are 64-bit capable. Run msinfo32 and check "System Type." If it says x64-based, you can install 64-bit Windows.
• Use a lightweight Linux live USB + Windows 10 64-bit VM — not ideal on a netbook but technically possible with 2GB+ RAM.
• Use FORScan instead — it runs on 32-bit Windows, supports VCM/VCM II/ELM327/J2534, and covers most diagnostic and configuration tasks. It won't do full dealer-level module programming, but for diagnostics, DTC, live data, and many service functions it's excellent on low-spec hardware.

The honest answer is: nobody is likely to develop a dedicated 32-bit раtсh for a legacy hardware edge case. FORScan on your netbook + full IDS on your 64-bit computer when needed is probably your best practical setup.

I know. Asking only if someone who knows can make the patches for 32bit systems.By the way, which раtсh should be used on 129 or 130? Do you have any for those?