Error 1720 indicates a Windows Installer problem running a custom action script. Since Windows Installer is already re-registered and the service is running, use these additional steps:
- Verify Windows Installer engine health
- Open Command Prompt as administrator.
- Run:
msiexec
If no error appears, the MSI engine is functioning.
- Confirm Windows Installer service startup type
- Press Win+R →
services.msc → Enter.
- Locate Windows Installer → right‑click Properties.
- Ensure Startup type is Manual, click OK.
- Right‑click Windows Installer → Start.
- Retry the HMIWeb Display Builder installation.
- Enable verbose MSI logging for the failing install
- Open an elevated Command Prompt.
- Run the HMIWeb MSI with logging, for example:
msiexec /i "C:\Path\To\HMIWeb.msi" /L*v "C:\Temp\HMIWebInstall.log"
- After it fails, open the log and search for
Return Value 3. The lines immediately before that show which script/custom action failed. Use that information with the vendor’s support to identify the exact cause.
- Check for corrupted or incomplete installation media
- If installing from CD/DVD or network share, copy the entire installer folder locally (for example to
C:\Install\HMIWeb) and run setup.exe or Autorun.exe from there.
- If downloaded, download a fresh copy from the official source and run it locally.
- Use the Program Install and Uninstall troubleshooter
- Run the “Fix problems that programs cannot be installed or uninstalled” troubleshooter to repair MSI-related registry issues that can break custom actions.
- Retry the installation.
- Analyze the MSI log with Wilogutl (optional, advanced)
- Install the Windows SDK and use Wilogutl.exe against the log file:
wilogutl /q /l C:\Temp\HMIWebInstall.log /o C:\Temp\HMIWebDiag
- Review the generated report for the failing custom action or missing DLL referenced by the script.
If the log shows a specific DLL or script file cannot be run, that typically must be fixed by the HMIWeb Display Builder vendor (updated package, prerequisites, or a repair script), so provide them the log section around Return Value 3.
References: