Bosch Esi Tronic 2013 1 2 And 3 Versions Will Not Install Mhh Auto New 〈95% RECOMMENDED〉
If you are determined to install directly on a machine (e.g., an old workshop laptop):
For a stable installation, avoid using MHH Auto patches on the same OS instance where you intend to run ESI tronic 2013. A clean virtual machine with an unmodified installer is the only reliable solution.
To avoid the "New" installation errors often discussed on MHH Auto, you must follow the sequence exactly:
Once you manage to get the progress bar moving, ensure you install the versions in chronological order if you are attempting a multi-version setup. Installing 2013/3 over a clean system sometimes works, but 2013/1 is often required as the "base" for the data architecture to map correctly. If you are determined to install directly on a machine (e
If you are struggling with the installation, especially after attempting to use resources from MHH Auto or similar forums, you are not alone. This software is notoriously picky regarding system preparation, license activation, and the proper sequence of installation.
This public link is valid for 7 days and shares a thread, including any personal information you added. This link or copies made by others cannot be deleted. If you share with third parties, their policies apply. Can’t copy the link right now. Try again later.
Use file verification tools (like 7-Zip’s built-in CRC tool) to ensure your downloaded archives match their target file sizes perfectly. Installing 2013/3 over a clean system sometimes works,
When setting up the license, keep the VM disconnected from the internet to prevent the activation from failing or resetting. 3. Alternative Solution: Direct Installation Checklist
: After a successful installation, create a full system image backup. If the software fails later, you can restore rather than reinstalling from scratch.
The claim: “Will not install” → likely a technical issue, not a false rumor. This public link is valid for 7 days
Click and let Windows Download the required system packages via Windows Update. Step 4: Purge Old Cache and Registry Errors
: Once 2013/3 is working, disable automatic updates. Updates from Bosch may attempt to migrate the software to ESI 2.0, which will break diagnostic functionality.
Many users prefer VMware Workstation to isolate the old OS from modern Windows 10/11 conflicts.
Ben Whitmore
Simon Skotheimsvik
Sandy Zeng
Hello,
We followed your guide to the letter on a 2016 and 2019 server but we keep running into the problem that the SCEP application pool keeps crashing for no real reason. We already ruled out a mistake in the templates or wrong CA certs in the intermediate.
We can see the Cert requests arrive but IIS dies everytime we see this in the NDES log:
NDES COnnector:
Sending request to certificate registration point. NDESPlugin 18-4-2019 17:04:05 3036 (0x0BDC)
Event viewer just shows us that w3wp.exe has crashed and that the faulty module is ntdll.dll.
We’ve been banging our heads against this problem for a week now so we hope you have any idea where to look.
Regards,
Herman
Nick, your stuff is amazing as always! .NET 3.5 appears to be required, so may be worth mentioning somewhere since some installations will need to specify an alternate path for that.
Using your script, I was failing on “Attempting to install Windows feature: Web-Asp-Net” and it wasn’t until I manually added 3.5–specifying the alternate path to the Server installation media–that I could continue.
Appreciate you sharing your findings Matt.
Regards,
Nickolaj
Internalurl in the app proxy config should be https and not http.
Yes, you’re correct.
Regards,
Nickolaj
Does this work for Android for Work or Android Enterprise devices? I can’t find the certificate issued to the end mobile devices even – iOS?
Yes it works for all platforms you mention.
Regards,
Nickolaj
Hey Nickolay,
there are two mistakes in your two pictures showing the configuration of the AAP. In the internal URL field you have to write https instead of http, because of the later binding / requiring of SSL. Your other older posts showing this also with https configured.
Best regards and nice work!,
Philipp
I’ve wasted way too much time troubleshooting this before I checked the IIS log files and they showed port 80. After changing AAD Proxy to HTTPS everything works.
Great guide though!
It appears that the script is expecting to find only 1 client authentication certificate with the specified subject. Could you modify it to handle cases where there are multiple certificates with the same subject?
Hello – Is there a mistake with the steps regarding the client and server certificates? At first you emphasized the points of each type which in turn have different Extended Key Usages. Are you stating to use the same template that contains both types?
Hi Carlos,
Could you please reference the pieces that you’re talking about?
Regards,
Nickolaj
Awesome step by step guide, many thanks. As per usual the MS TechNet lacks a lot of steps and inside information. Regarding the two certs, can they also be 3rd party and trusted certs (wildcard) ?