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

wiTECH 2 J2534 "Device Not Connected: Internal Error" on the AEZ Flasher 3 or EZ Flasher

The "Device not connected: Internal error" message on a J2534 interface is usually caused by the laptop rather than the tool — a wrong system clock, missing Microsoft Visual C++ runtime files, or an installation damaged by a Windows update. This guide covers the causes in the order they most often occur, and what to check before reinstalling.

Device not connected: Internal error" on a wiTECH 2 J2534 interface — the AEZ Flasher 3 or EZ Flasher — almost always points at the laptop rather than the tool. The most frequent causes are a system clock that has drifted, missing Microsoft Visual C++ runtime files, or a wiTECH installation damaged by a Windows update. The interface itself is rarely at fault, so replacing it or trying a second vehicle will not clear the error. This Installation & Setup guide works through the causes in the order they most often occur. Test the connection after each step before moving on to the next.

Checks to run in order

The five checks below cover the causes behind most occurrences of this error. The first two take a couple of minutes each and resolve the majority of cases, so work through them top to bottom rather than starting with a reinstall.

Check 1 — Sync the system clock

An incorrect system time is one of the most common causes of authentication and connection failures on a J2534 interface, and it costs nothing to rule out.

  1. Open Windows date and time settings.
  2. Toggle "Set time automatically" off, then back on.
  3. Confirm the time zone is correct as well as the time.
  4. Relaunch wiTECH 2 with the interface connected and test the connection.

Check 2 — Install the missing Microsoft Visual C++ runtime

A Windows update can remove or break the Microsoft Visual C++ runtime files that wiTECH 2 depends on. This produces "Device not connected: Internal error," and on some machines an executable error naming a missing VC runtime DLL. It is most common on Windows 10 laptops shortly after a Windows update.

  1. Install the current Microsoft Visual C++ Redistributable packages, both x86 and x64.
  2. Restart the laptop.
  3. Relaunch wiTECH 2 with the interface connected and test the connection.

If you are not sure which packages the machine is missing, submit a support ticket — this is a quick fix over a remote session.

Check 3 — Run a repair on the wiTECH installation

If the error started immediately after a Windows update, the wiTECH installation itself may be damaged. A repair is faster than a full reinstall and preserves your configuration.

  1. Locate the wiTECH 2 installer in your Downloads folder, or download the current version.
  2. Run the installer and choose the repair option rather than a fresh install.
  3. Let the repair finish, restart the laptop, and test the connection.

If a repair is not offered, or does not clear the error, uninstall and reinstall wiTECH 2. On first launch after reinstalling, the software updates the firmware on the interface automatically — do not unplug the tool during that process.

Check 4 — Confirm the Windows version

Current wiTECH 2 J2534 work expects Windows 11 Pro. J2534 behaviour on Windows 10 is inconsistent, and a machine that worked previously can stop after a Windows 10 update. If the laptop is on Windows 10 and the error persists after the checks above, upgrading to Windows 11 Pro is likely the durable fix. See the Windows 11 requirements article, and contact AE Tools to check upgrade eligibility for that laptop.

Check 5 — Confirm the subscription and tool serial

The error can also appear when the interface is not authenticated. Confirm your wiTECH 2 and TechAuthority subscriptions are both active and registered against the correct tool serial number. After any subscription change, wait about five minutes, unplug the tool, sign fully out of wiTECH 2, sign back in, and reconnect.

When it is not this error at all

On 2023-and-newer Stellantis vehicles — including Grand Cherokee, Wagoneer, and Grand Caravan — a J2534 pass-thru such as the AEZ Flasher 3 cannot be used for key and module programming, and a genuine MicroPod is required. A connection failure on those vehicles is a coverage limitation rather than a fault, and none of the checks above will change it. See the article on J2534 issues with WiTECH 2.0 on 2023+ Stellantis vehicles.

Wi-Fi-specific failures on the interface are covered separately — if the tool connects over USB but not wirelessly, see the EZ Flasher / AEZFlasher Wi-Fi troubleshooting guide instead.

If it still will not connect

Submit a support ticket including:

  • The tool serial number.

  • The Windows version and edition.

  • Whether the problem started after a Windows update or a wiTECH update.

  • The vehicle year, make, and model you were working on.

  • The exact error text.

  • What you found in each of the checks above.