PDA

View Full Version : Uninstalling and reinstalling FlashScan/AutoCal USB drivers



Blacky
June 11th, 2013, 02:52 PM
Before attempting to trouble shoot any USB driver issues it is important to make sure the drivers are installed correctly and that all the files that are part of the driver set are from the same driver version. Other USB devices may also be installed on your system that also use the FTDI USB drivers that FlashScan and AutoCal use. Installing those other devices can cause problems with incompatible driver files. If you are experiencing USB connectivity issues EFILive recommends uninstalling the USB drivers and reinstalling them.

These instructions are specifically for Windows 7 but they can also be used with minor differences for Windows XP, Vista and 8.

To uninstall the EFILive USB drivers:

Unplug all EFILive USB devices.
Log in to your computer with administrator privileges.
Start Windows Explorer and navigate to the folder:
C:\Program Files\EFILive\Drivers\Utilities\Remove FDTI USB Drivers (on 32 bit machines)
or
C:\Program Files (x86)\EFILive\Drivers\Utilities\Remove FDTI USB Drivers (on 64 bit machines)
Run the CDMuninstallerGUI.exe program by double clicking it.
Enter the following values: Vendor ID: 0403 and Product ID: E4A0, then click [Add].
Do the same for Product IDs: E4A1, E4A2 and E4A3, clicking add after each one.
You should end up with a display like this:
15329
Click [Remove Devices], the removal process should be complete after about 10-20 seconds.
You may see messages that some devices were not found - that's ok because not all devices may have had drivers loaded.
You may also see a message that says "This program may not have installed correctly", if you do, just click [Cancel].
Click [Cancel] to close the uninstaller program.


Remove old/unwanted dll files:
Search the EFILive Program Files folder for copies of the file: ftd2xx.dll. If you find any copies of that file in the folders:
C:\Program Files\EFILive\V7.5 (on 32 bit machines)
or
C:\Program Files (x86)\EFILive\V7.5 (on 64 bit machines)
or
C:\Program Files\EFILive\V8 (on 32 bit machines)
or
C:\Program Files (x86)\EFILive\V8 (on 64 bit machines)
then delete those ftd2xx.dll files.

IMPORTANT: Do not remove any dll files from the actual driver installation folders:
C:\Program Files\EFILive\Drivers
or
C:\Program Files (x86)\EFILive\Drivers


To re-install the EFILive USB drivers:

Reboot your PC.
Connect FlashScan or AutoCal.
If a balloon appears in the system tray saying installing or searching for drivers, click on it and then click on the option "Skip obtaining driver software from Windows Update".
You should see a message similar to this:
15330
Click [Close] to close the error dialog box.
Start Windows Device Manager: Hold down the Windows key and press and release the Pause key, then select Device Manager.
Locate the device you connected (FlashScan or AutoCal) in the list of devices, most likely it will be shown with a little yellow tag indicating that the drivers are not loaded.
15331
Right click on the device and select "Update Driver Software..."
Select "Browse my computer for driver software"
15334
Navigate to the folder containing the latest drivers which will usually be
C:\Program Files\EFILive\Drivers\EFILive\Win-XP-Vista-7-8(on 32 bit machines)
or
C:\Program Files (x86)\EFILive\Drivers\EFILive\Win-XP-Vista-7-8 (on 64 bit machines)
15333
Click [Next] and the drivers will be installed.
15332

2007 5.9
June 11th, 2013, 04:24 PM
Done this process 4-times and still no better. Hangs when opening V7.5, closing 7.5 and closing Scan Tool.

Blacky
June 11th, 2013, 04:40 PM
I presume that on your system, the V8 software does not suffer from the same hanging that the V7 software is experiencing.

There may be something in the V7 USB API that is incompatible with some PC configurations and/or USB ports.
Unfortunately, it all works perfectly on our test systems here so we can't track down the problem.

Meanwhile, I am building a version of V7 that uses the same USB API calls as the V8 software. Once that is ready, I'd appreciate it if you could test the new version side by side with the old version to see if the new version works while the old version hangs.
I hope to have that ready tomorrow.

Regards
Paul

2007 5.9
June 11th, 2013, 04:43 PM
I'm ready to try anything!!!

And yes V8 runs perfectly.

Thanks for your hard work Paul.

koryenger
June 12th, 2013, 03:53 AM
Fighting the same issue all day yesterday...read all the threads and tried everything. Prior to doing a system restore to the old reliable USB driver would hang about 1/3 of the way throught loading calibration definitions. After system restore... I installed the newest, latest and greatest driver....now it hangs up 3/4 of the way during "loading calibration definition" I dont know if this info helps... but I will gladly try the new version to see if it works.

voda1
August 8th, 2013, 02:30 AM
Having same issue after installing v7.5.235 software(upgrading from .170).

When plugging V1 into computer first time the balloon pops saying device install successful. However the device manager shows no Flashscan device.

Using TuneTool - Going to HELP-->Flashscan V1 PcmLicensing screen: shows "EFI cannot communicate with FlashScan or Autocal" message.

When running the CDMUninstaller.exe app it fails with: "Invalid Arguments"

Tried this on 2 different computers(XP pro & win7) with same results.

Also there are no yellow tags in device manager.
Do you know the Device Instance ID?

voda1
August 8th, 2013, 03:45 AM
However the device manager shows no Flashscan device.

Ok found the 'EFILive Flashscan FSP' device under the the USB Controllers section of the device manager.

Trying: Right click --> Properties--> Advanced then check Load VCP (adds a virtual com port interface device under the Ports tab in device manager)

Blacky
August 8th, 2013, 08:51 AM
When running the CDMUninstaller.exe app it fails with: "Invalid Arguments"

Use CMDUninstallerGUI.exe instead.


Do you know the Device Instance ID?

No, that will be different depending on which USB port you connect it to.

Regards
Paul

Blacky
August 8th, 2013, 08:57 AM
Ok found the 'EFILive Flashscan FSP' device under the the USB Controllers section of the device manager.

Trying: Right click --> Properties--> Advanced then check Load VCP (adds a virtual com port interface device under the Ports tab in device manager)

Adding the Virtual COM Port option won't help. FlashScan does not use that.

I would recommend updating to the latest version here (http://forum.efilive.com/showthread.php?23025-Update-Aug-06-2013), except there is a known issue with the latest version that causes the exact problem you are seeing with build 235.
We are working on it right now, as soon as it is fixed in the latest version, I recommend updating.

I have found that doing this should allow V1 to work with the V7 software again:
Uninstall V7
Uninstall the USB drivers (using CMDUninstallerGUI described in the first post)
Reboot the machine
Re-installing V7.5.7.135
Connect FlashScan and wait for Windows to fail to load the drivers
Open up the device manager page, locate the FlashScan V1 entry, and re-install/update the drivers
Browse to the Win-2K drivers and install those (yes, even on Win7 and Win8)

Regards
Paul

voda1
August 8th, 2013, 01:46 PM
Re-installing V7.5.7.135

I no longer have that version. Is it available somewhere yet?

Blacky
August 8th, 2013, 02:35 PM
I no longer have that version. Is it available somewhere yet?

Sorry, my mistake, I meant build 235 (not 135) available here:
https://www.efilive.com/latest/cat/download-efilive

Regards
Paul

voda1
August 10th, 2013, 12:50 PM
Adding the Virtual COM Port option won't help. FlashScan does not use that.

I would recommend updating to the latest version here (http://forum.efilive.com/showthread.php?23025-Update-Aug-06-2013), except there is a known issue with the latest version that causes the exact problem you are seeing with build 235.
We are working on it right now, as soon as it is fixed in the latest version, I recommend updating.

I have found that doing this should allow V1 to work with the V7 software again:
Uninstall V7
Uninstall the USB drivers (using CMDUninstallerGUI described in the first post)
Reboot the machine
Re-installing V7.5.7.135
Connect FlashScan and wait for Windows to fail to load the drivers
Open up the device manager page, locate the FlashScan V1 entry, and re-install/update the drivers
Browse to the Win-2K drivers and install those (yes, even on Win7 and Win8)

Regards
Paul

Followed steps listed above but the FlashScan was immediately recognized when plugged in. Went to the device manager and installed the Win-2K drivers. Everything is working OK now.

Thanks

skirsman
December 18th, 2023, 12:17 PM
following these steps windows 11 won't recognize the driver in any folder.

Blacky
December 18th, 2023, 01:06 PM
following these steps windows 11 won't recognize the driver in any folder.

Have you tried using the EFILive USB Manager program?

Windows Start Button -> search for USB, right click on EFILive USB Manager and select Run As Administrator.

24564

Regards
Paul

skirsman
December 18th, 2023, 01:55 PM
Have you tried using the EFILive USB Manager program?

Windows Start Button -> search for USB, right click on EFILive USB Manager and select Run As Administrator.

24564

Regards
Paul

doing some research just find out that windows 11 is the only one that support M1 chip from Apple. maybe that why the windows won't install any driver. Looked into https://ftdichip.com/drivers/d2xx-drivers/
still won't like it. Maybe there an specific driver for the M1 chip...my old Mac is OK...I also order a different usb cable WO adaptor.

skirsman
December 22nd, 2023, 09:01 AM
doing some research just find out that windows 11 is the only one that support M1 chip from Apple. maybe that why the windows won't install any driver. Looked into https://ftdichip.com/drivers/d2xx-drivers/
still won't like it. Maybe there an specific driver for the M1 chip...my old Mac is OK...I also order a different usb cable WO adaptor.

new try with usb-c cable WO adaptor...no luck...look like I need that specific driver for W11 for M1 chip

ANY HELP:sly: