What to do when the MicroPod update freezes or hangs during configuration
Step-by-step guide to recovering and reconfiguring a frozen MicroPod (MDP/MDP+/WSP) during a WiTech update, including disconnecting the device, reopening the VCI Setup Utility, and completing the reconfiguration process.
If your MicroPod (MDP, MDP+, or Wireless Smart Pod / WSP) is in the middle of a WiTech update and freezes or stops responding, the device will need to be reconfigured using the VCI Setup Utility. This is a known recovery process for Stellantis (Chrysler) diagnostic tools. The MicroPod cannot resume the update from where it stopped, so the recovery process requires shutting down the PC, disconnecting the pod, and walking through the VCI Setup Utility reconfiguration from the beginning.
Running the firmware update correctly (so it doesn't hang)
Micropod firmware is updated through the VCI Setup Utility (Documents → VCI Setup Utility), not through WiTECH 2.0 itself. To avoid a hung update:
- Connect the Micropod by wired USB — do not use wireless during a firmware update. - Let the VCI Setup Utility detect the Micropod, then start the update.
- During a running update, do NOT click "Continue," close the VCI Setup Utility, or unplug the Micropod. (Clicking "Continue" is only used in the recovery reconfiguration below, if the update has already frozen — not during a running update.)
- Disable PC sleep mode so the laptop doesn't sleep mid-update.
- A normal update takes 5–15 minutes and can pause 2–3 minutes with no visible progress while it writes flash memory — wait before assuming it has failed.
How to recover a frozen MicroPod (MDP/MDP+/WSP) during a WiTech update
Follow these steps in order to recover a MicroPod that has frozen or hung during a WiTech update:
1. Turn off your PC.
2. Disconnect the MicroPod from both the PC and the vehicle. The pod must be disconnected to power down.
3. Turn the PC back on.
4. Plug the MicroPod back into the PC using the right angle USB cable only.
5. Open Device Manager on your PC to confirm the MicroPod is recognized.
6. Open the VCI Setup Utility and select "Continue."
WARNING: Only select "Continue" if you intend to reconfigure the MicroPod. Reconfiguring will erase all factory settings and rebuild the pod's configuration from scratch.
7. Select "Continue" again — this allows the VCI Utility Manager to connect to the MicroPod.
8. Once the connection is established, select "Continue" once more to start the reconfiguration process. This step takes approximately 5 minutes.
9. Once reconfiguration is complete, you can use the underlined link in the VCI Setup Utility to open and log in to WiTech 2.
10. Log in to WiTech 2 and run the update again. The update will take 5 to 10 minutes to finish.
11. After the update completes, the MicroPod is ready to be connected to the vehicle.
If reconfiguring the pod doesn't fix it - the WiTech 2 client may be corrupted
If you've completed the VCI Setup Utility reconfiguration above and the update still freezes, hangs, or returns a certificate error, the problem is usually the WiTech 2 client on the laptop, not the pod. Work through these in order.
First, cycle the YTAG session to force activation against your current subscription:
1. Unplug the MicroPod (MDP/MDP+) or AEZ Flasher 3.
2. In WiTech 2, fully log out of YTAG - do not just close the window.
3. Log back in with the subscription holder's credentials.
4. Reconnect the tool via USB or wireless, then retry the update.
If a certificate error or "stuck on updating" message still appears, do a clean reinstall of the client:
1. Download Revo Uninstaller (the free version is fine).
2. Run Advanced scan.
3. Right-click the WiTech 2 entry only - this avoids affecting other Stellantis or Mopar software on the same machine.
4. Let Revo finish the uninstall (about 5 minutes), then restart the laptop.
5. Download the latest WiTech/Flasher installer fresh from the AE Tools site.
6. Right-click the installer and Run as administrator.
7. Reopen the application, log into YTAG, reconnect the pod or Flasher, and let updates complete without interruption.
A clean WiTech 2 reinstall typically takes 20–30 minutes depending on internet speed.
If the update still fails after reconfiguring
Before retrying, rule out Windows, security software, and the connection:
- Do not unplug the Micropod the instant an update fails — that's when corruption happens. Close the VCI Setup Utility cleanly first.
- Switch to a different USB port and plug directly into the laptop, not a USB hub. Reopen the VCI Setup Utility on a wired connection, let it re-detect the Micropod, then retry.
- Check for pending Windows Updates, including .NET Framework updates. Install anything pending, reboot the PC, then unplug the tool and rerun the VCI Setup Utility.
- If it still fails, type "Windows Security" in the search bar and turn off the firewall and real-time antivirus protection for the duration of the update (re-enable both afterward).
- Confirm the PC's date and time are correct — a wrong clock can break the secure connection during the update.
- If the Micropod is not detected at all after a failed update, the unit may need to be replaced via RMA — call AE Tools.
"No update available" but WiTECH says the tool is out of date
If the VCI Setup Utility shows no update available but WiTECH 2.0 flags the Micropod as out of date:
1. Unplug the Micropod.
2. Fully log out of YTAG in WiTECH 2.0.
3. Log back in, then reconnect the Micropod and reopen the VCI Setup Utility.
If WiTECH still flags the tool as out of date after this, it's the WiTECH client that's out of date, not the Micropod — run the latest WiTECH/Flasher installer to refresh it.
2026 Durango / Ram won't pair keys after an update (RFH module)
If a 2026 Durango or Ram fails to pair keys after a Micropod firmware update, this is not a Micropod problem. These vehicles use a locked RFH (Radio Frequency Hub) module that can show "protected" status without a VIN, which blocks key pairing and RFH configuration. Updating Micropod firmware or reinstalling WiTECH will not unlock it — a locked/protected RFH must be replaced, followed by a PCM reflash and the secret-key procedure.
Why the MicroPod freezes during a WiTech update
A MicroPod freezing or hanging during a WiTech update is typically caused by interrupted communication between the MicroPod and the PC, a USB connection issue, or a software conflict during the update process. The device cannot resume the update partway through, which is why the VCI Setup Utility reconfiguration is required to recover the pod.
Important notes when reconfiguring a MicroPod
- Always use the right angle USB cable when reconnecting the MicroPod to the PC. Using a different cable or USB hub can cause the reconfiguration to fail.
- The reconfiguration process erases the MicroPod's existing factory settings, so do not interrupt it once started.
- The MicroPod must remain connected to the PC throughout the reconfiguration and update process. Do not unplug it until the update completes.
- If the MicroPod still does not recover after running the VCI Setup Utility, contact AETools support for further assistance.
Common follow-up issues
"VCI Setup Utility won't open." Run it as administrator. If it still won't open, reinstall the VCI Setup Utility from the AE Tools site, and make sure WiTECH 2.0 is closed when you launch it.
"The Wi-Fi setup is gone after the update." Wi-Fi profiles can clear during a firmware update — reconfigure wireless through the VCI Setup Utility (see the article on connecting the MicroPod to Wi-Fi using wiTECH 2.0).
"Keys won't program on a 2025 Wagoneer after a forced MDP update." A forced MDP update is irreversible; a 2024 reflash (calibration 8131AC) is a known workaround. If that doesn't help, contact AE Tools for the latest field guidance.