dzldoctor wrote: Fri Nov 21, 2025 9:32 pm
MY old laptop crashed and burned so that part isnt an option. lol
Ill try to load those files. But device or vci manager isnt showing up. Not sure if it didnt download fully or the new version isnt very compatible.
It will not pick up my OBD adaptor either. Its a ELMconfig adaptor with the switch. I read that may not work with the newer versions so I grabbed my VCM2.
First off: is this Surface an Intel/AMD processor or an Arm Processor!
Arm Processors can have trouble with Intel/AMD based Software! Forscan(see this topic if so:
viewtopic.php?f=5&t=27650) has discovered that there is a Compatibility mode in the Arm system that must be used to run FORScan on Arm processors and this may be true also of the Ford/Bosch VCI manager!
When the VCM2 is connected by USB the first time with the VCI manager installed there should be an install manager that opens and installs the VCI software and should show a box advising not to disturb the USB cable or turn off the computer until the install completes!
If the VCI Manager installed correctly there should be a Bosch File folder in the in the Start menu which contains the VCI manager and a J2534 Configuration APP!
You should be able to run the the VCI Manager and see if the VCI manger sees the VCM2(And it's serial number highlighted in blue) and can connect to it(Connect Button) and Page it with the check box(VCM should beep, beep, beep)!
If you got the VCI manger software from the Bosch diagnostics site(boschdiagnostics.com/software-updates/ford-vcm-ii) I suspect you got Version v2.3.85.7 which is about 8-9 years old and Ford has much later versions(See the Update tab in the VCI Manager with the VCM Connected) and that may be too old for a later produced VCM 2 and may not connect to a VCM2 produced up to the latest when the VCM2 was discontinued in favour of the VCM3!
Do not know for sure! I run the 2.3.85.7 as it works with A Patched Version of IDS 86 and the one Ford installs does not but does work with FORScan and My VCM2 Clone!
If you have working VCI Manager but the VCM is X'ed out in the VCI Manager go and do the following!
When you plug the VCM2 USB cable into the Surface, you should here the Windows USB connection Sound and the VCM2 should cycle through the lights( Car, Computer and Power on) and then give a long Beep to signify that the VCM has connected to the Computer!
Nothing will connect if the above is not happening!
If the above does not happen, open the Windows Device Manager to "Network Adapters" and open the tree and connect the VCM2 to a USB port. The device manager tree should cycle and there should appear a network device labeled "ETAS VCI USB RNDIS Device" or at least " ETAS RNDIS Device"!
If this device is not there then Windows for some reason is not loading the Base device driver! This RNDIS network adapter loads the VCM2 into Windows so that the VCI manager sees it! (This is a device integeral and contained in the windows system files or at least it is in INTEL/AMD based systems, not sure about ARM, and should not need a separate install and should load when the VCM2 USB cable is plugged in)!
If this surface has a USB2 port try that and see if the RNDIS device loads if the above does not show the device(Have not had experience with the VCM2 on USB3 although USB3 is supposed to be backwards compatible back to USB1 but some of the ELM/FTDI adapters have been having trouble connecting on USB3 Ports)!
Make sure that FORScan's connection type(Gear Icon unchecked Auto) is set to J2534 and the J2534 Adapter Box shows "Ford-VCM-ii
Not having any experience with the VCM2 on an ARM Processor I do not have much else to offer if this is your situation accept to try setting up the VCI Manager and FORScan to run in "Compatibility Mode!