If the installer throws a generic "Error 1722" or "Install Shield" error:
| Aspect | Rating | |--------|--------| | Claim truthfulness | ✅ True for default modern PC setup | | Workaround availability | ✅ Possible via VM or old hardware | | Suitability for new users | ❌ Not recommended — too fragile | | Better alternative | Use newer ESI (2020+) or online versions (e.g., Bosch Web ESI) |
If you’d like, I can also provide a step-by-step fix based on the most successful MHH Auto guide for ESI 2013 v3. Just let me know.
The installation of Bosch ESI[tronic] 2013 versions (1, 2, and 3) from sources like MHH Auto often fails due to strict system requirements, licensing conflicts, or improper installation sequences. This 2013 version is one of the last "offline" releases before Bosch transitioned heavily toward ESI[tronic] 2.0 . Common Installation Barriers
Operating System Compatibility: ESI[tronic] 2013 was designed for Windows XP and Windows 7 (32-bit). Attempting to install it on Windows 10 or 11 frequently results in kernel errors or setup termination.
Sequential DVD Dependency: The software is often split into three DVDs (Version 1, 2, and 3). Users frequently report that Version 2 or 3 won't install if the base files from Version 1 aren't correctly registered by the setup wizard .
Licensing & "I-Key" Errors: Most non-official versions require a specific "patch" or "keygen" to bypass the I-Key requirement. If the activation ID is not generated correctly after the initial software setup, subsequent modules will fail to recognize the installation. Troubleshooting Steps If the installer throws a generic "Error 1722"
Clean Installation Environment: Ensure all previous ESI[tronic] remnants are removed. Residual files in the C:\Program Files\Bosch or C:\ESI directories can block new setup attempts.
Run as Administrator: Execute the RBsetup.exe file with administrative privileges and in Windows 7 Compatibility Mode if using a newer OS.
Correct DVD Order: Always install Version 1 first. Do not attempt to "update" to Version 2 or 3 until the first version is fully installed and, if necessary, patched.
Hardware Configuration: If you are using a KTS diagnostic interface , ensure the drivers are configured only after the main software is on the disk to avoid USB conflict errors.
For the most reliable experience, modern workshops typically use the Diagnostics Download Manager (DDM), which automates these complex installation steps for current versions.
Which specific error code or message are you seeing during the setup process for Version 2 or 3? Bosch Esi(tronic) installation If you’d like, I can also provide a
Title: FIXED: Bosch ESI[tronic] 2013 (Version 1, 2, & 3) Will NOT Install – The MHH Auto “New” Solution
Posted by: DrivingDiagnostics (Today at 03:45 PM)
Subject: Solving the installation failure for 2013 v1, v2, and v3 on modern OS (Windows 10/11)
Body:
Hey everyone,
I know we are all used to hunting down the latest 2024/2025 releases, but sometimes you need the old faithful 2013 versions (1, 2, or 3) for legacy vehicle diagnostics, specific diesel injection timing data, or older TSI engines that later software versions stopped supporting properly. Title: FIXED: Bosch ESI[tronic] 2013 (Version 1, 2,
I kept running into a brick wall trying to install ESI[tronic] 2013/1, 2013/2, and 2013/3 on a modern PC (Windows 10 Pro x64). The installer would either:
After digging through the old MHH Auto archives and combining three different “fixes,” I finally got all three versions to install cleanly. Here is the MHH-approved method that works as of this week.
If you’re trying to install Bosch ESI[tronic] 2013 (versions 1, 2 or 3) and the installer fails on an MHH Auto New system, this guide shows practical troubleshooting steps and fixes to get the software installed and working. These steps address the most common causes: compatibility issues, missing prerequisites, permission problems, and corrupted installers.
For 2013/1:
For 2013/2:
For 2013/3 (trickiest):
Even with the MHH Auto New method, some users encounter issues. Here is the community’s debugging checklist:
| Problem | MHH Auto Solution |
| :--- | :--- |
| “The patch says ‘Target file CRC mismatch’” | You are using the wrong version (trying to patch 2013.1 on 2013.3 files). Re-download the correct patch from MHH. |
| Install hangs at 67% copying wds_data.mdb | Your hard drive has bad sectors, or the ISO is corrupted. Re-extract from original RARs. Use chkdsk /f. |
| “MSI error 1628: failed to complete installation” | Windows Installer service is stuck. Run msiexec /unregister, then msiexec /regserver. Reboot. |
| ESI launches but shows blank screen | The SQLite database repair failed. Run ESI_DB_Repair.exe again, but this time select “Deep Rebuild Mode.” |
@echo off
set __COMPAT_LAYER=WIN7RTM
set SETUPAPI_OVERRIDE=1
set SQL2005_IGNORE=TRUE
start /wait EsiSetup.exe /norestart