Fix the Windows installer dialog that hangs when HMI software starts

Why does a Windows Installer dialog open when my HMI software starts?

The dialog opens because the HMI software asks Windows, at launch, for a component that Windows Installer is registered to provide; when the registration and the files on disk disagree, the service stalls and the dialog never finishes. The fault sits in the Windows installation, not in the HMI package.

Windows Installer is the Windows service that installs and repairs software on demand. An HMI package declares the Windows components it needs, and the runtime asks for them at launch. When a component is missing, or its registration points at files that are not on the disk, the service opens that dialog and stalls.

One dependency is documented from a machine with this exact fault: the software's Object Help feature uses Internet Explorer, a standard component of Windows XP Pro. A PC whose Windows install was built with components removed from the base installation can be short of exactly that kind of part.

The Windows Installer service can also be the damaged part. The sign is broader: every install and every uninstall on the PC hangs, often with the dialog stuck at Gathering required information. No application package repairs that state; only a Windows-side repair does.

What does the hang look like at the PC?

Every sign in this hang sits on the Windows side: the dialog that never completes, the Cancel button that does nothing, the runtime executable reported hung, and the unchanged result after each new download.

• A dialog titled Windows Installer opens at runtime start and never finishes. A component lookup has stalled. Go to the event-log check below.
• Cancel does nothing, and Task Manager is the only way out. The service is stuck, not busy. The error afterwards names the runtime executable; EA.exe was the name on the failing machine. The hang sits under the application, inside Windows.
• A fresh download plus an uninstall in Add or Remove Programs changes nothing. The package is not the variable. Stop downloading; every loop costs an hour and repairs no Windows component.
• Other software installs and runs normally. The OS broadly works, and one component or one registration entry is broken. General health is a poor excuse to skip the checks.
• The dialog is already open before you launch anything. Check the Startup tab for an msiexec entry, disable that entry, reboot and retest; that is the documented fix for an installer that starts with the PC.

Which checks separate a Windows problem from a bad download?

Run the checks in order and stop at the first result that convicts Windows: an install test outside the HMI package, the component history of the PC, a second PC on the same edition and service pack, and the software vendor's own position.

1. Install or uninstall anything else. If every installer on the PC hangs at Gathering required information, the Windows Installer service is the fault and the HMI package was never in the question.
2. Read the component history. Did the Windows install remove components from the base installation? Is Internet Explorer present, for the Object Help dependency? A new PC with a trimmed OS install is the classic host for this hang.
3. Compare a second PC on the same edition and the same service pack. An older machine on Windows XP SP1 that launches the software with errors answers nothing about an XP Pro SP2 machine; bring it to SP2 before its result counts. Record the edition, the service pack, and whether the software installs and launches, not just whether the setup program opens.
4. Ask the software vendor, once. The vendor in this class of case reported no known installation failures on Windows XP Pro and asked for exactly the second-PC test. Treat the answer as one input, and keep the discipline of diagnosing before repair, the same one behind HMI editor crash diagnosis before software repair.

What should the event log tell me?

Open Event Viewer and read the Application log entries stamped in the minute the runtime starts; the decisive finding is a component logged as registered while its files are absent from the disk.

One PC with this exact dialog, running Windows XP Pro SP2 with Office 2002 Pro SP3, logged four files registered but not installed:

• C:\Program Files\msaccrt\Access 97\msacc8.olb
• C:\Program Files\msaccrt\Access 97\msain800.dll
• C:\Program Files\msaccrt\Access 97\msaccess.exe
• C:\WINDOWS\system32\Odbcjet.hlp

All four pointed back to an old Office install CD whose files were not on that machine. The registration table and the disk disagreed, which is exactly the state that leaves the dialog open. Filter the log to the Windows Installer entries around the launch minute and read them against the file system; entries far from the launch time belong to other jobs and only add noise.

When is a Windows repair or reinstall the right fix?

Rebuild Windows when the evidence sits in the machine's history: components removed from the base install, a repair install already run on it, an activation that expired before a phone activation, or event-log entries that name registered files missing from the disk.

The failing PC in the worked example carried the full set. Its activation expired past the 30-day grace period, a Windows lock-up ended in a phone activation, the USB ports died after it, and a setup repair brought the ports back. The installer hang appeared inside that sequence. Nothing in it describes a healthy base, and no download can repair one.

Before you rebuild, do two things. Back up the HMI project files and the machine configuration, and open the copy on another PC to verify it; if an old backup disc refuses to open, clear the read-only flag first, as in an HMI project backup that will not open. Then gather your licensed Windows media, the drivers and the approved HMI software installers, so the rebuild never waits on a download.

What does a worked example look like?

One real case lost 59 days to re-downloads and cleared the same afternoon the operating system was reinstalled, which is the arithmetic that makes the diagnosis worth doing first.

• The machine. A new shop-floor editing PC on Windows XP Pro SP2 from the OEM disc, 2 GB of RAM, four hard disks on a RAID controller, not connected to the internet.
• 14 February. The HMI software installs. The first launch opens the Windows Installer dialog, Cancel is dead, Task Manager closes the application, and the error names EA.exe.
• The following weeks. Several fresh downloads of the same package, each followed by an uninstall in Add or Remove Programs, each ending in the same dialog.
• The comparison PC. An older machine on Windows XP SP1 launches the software with several errors; a different service pack, so the result is set aside until that machine reaches SP2.
• The history. The 30-day activation grace had expired, a lock-up forced a phone activation, the USB ports failed after it, and a setup repair restored them.
• 14 April. Windows XP Pro is reinstalled from licensed media with every standard component kept. The HMI software is installed and launched before anything else, and it installs and runs correctly on the first attempt.

The arithmetic: 14 days left in February, plus 31 in March, plus 14 into April, is 59 days between the first hang and the working install (14 + 31 + 14 = 59). Every re-download in those 59 days addressed the wrong layer.

What order should the rebuild follow?

Follow one order and test at every step: verified backup, licensed media in hand, Windows reinstalled complete, activation done inside the grace period, HMI software first, other software in groups.

1. Back up and verify. Copy the HMI project files, the machine configuration and anything else the cell needs, and open the backup on another PC before you touch the disk.
2. Gather media. Licensed Windows media, the board drivers and the approved HMI installer go on the bench first. On a RAID or SATA machine with an XP-era disc, press F6 early in setup and supply the storage driver, because the disc does not carry it.
3. Reinstall Windows complete. Keep every standard component, and activate inside the grace period; never put the machine to work on an expired activation.
4. Install drivers and record each change, so a later regression has a paper trail.
5. Install the HMI software and launch it before any optional utility, and use the same build that ran before the wipe; matching the build to the project avoids a second class of failure, covered in matching HMI software upgrades to the installed build.
6. Add the remaining software in groups and retest the HMI software after each group.

Recommendation: Diagnose before you rebuild: read the Application log at the launch minute and test a second PC on the same edition and service pack. Rebuild Windows from licensed media when the log shows files registered but not installed, or when the setup history shows a repair run after an expired activation, and install the HMI software first on the rebuilt machine, before any other software.

How to check the rebuild worked: the runtime opens with no dialog, Cancel is never touched, and the Application log shows no registered-but-missing entries at the launch minute. If the same hang appears on a clean, documented install, stop the download loop, keep the installer and the log, and take both to the software vendor's support path.

The editing PC stays a Windows job throughout. If the cell also needs a notice or status screen for cycle counts, quality alerts or shift notes, that separate job is what our shop-floor screens are built for, with the exact configuration confirmed in the quote.

Questions