Bosch Esi Tronic 2013 1 2 And 3 Versions Will Not Install Mhh Auto New

Given the installation hurdles, why not use a newer version?

However, if you must have newer data (2014+), consider merging database files from 2015/1 into a 2013/3 shell – a hack documented on MHH Auto (search "ESI DB swap 2013 to 2015"). It requires manual SQLite editing.

The original ESI 2013/1 installer contains a custom action that attempts to stop the Windows Installer service mid-installation to write registry keys. On Windows 7 SP1, 8.1, or 10, this triggers a deadlock. The MSI engine waits for itself, then times out after 15 minutes, rolling back.

Solution: Extract the MSI from the DVD using Universal Extractor. Then run: msiexec /i Bosch_ESI_2013_1.msi /qb- /norestart This bypasses the custom action.

Yes, the statement is accurate for many users attempting a direct install on modern Windows without extensive tweaking. Given the installation hurdles, why not use a newer version

However, it’s not universally impossible — skilled users on MHH Auto have workarounds, but no simple “next, next, finish” solution.

The issue is that the 2013 installer uses an expired digital certificate and an old Microsoft SQL Server 2005 Express component that Windows 10/11 rejects outright. Here’s the step-by-step:

Version 3 has an additional license timer check that looks for a date before 2015. After installation, run the “Date Cracker” from MHH user xenozzz (post #406 in the original 2013 thread). Set system date to June 1, 2014 only for first launch, then you can change it back.