First time here? Check out the FAQ!

32 Bit HP CIO Components Installer -- Configuration completed successfully

+1 vote
asked by (130 points) about 32 Bit HP CIO Components Installer

In a Windows 2003 Terminal server the event viewer is showing MsiInstaller running every few minutes, this is taking up cpu usage.

The message in the subject is the one in the event.

How can this be stopped from running?

2 Answers

0 votes
answered by (140 points)

I am having the same problem in the same sort of environment. Check the registry and you will probably find tons of erroneous entries under Hewlett-Packard in the following parts of the registry:

HKEYLOCALMACHINESOFTWAREMicrosoftWindows NTCurrentVersionTerminal ServerInstallSoftware

I have not figured out a solution to this. My hunch is that it is related to the HP Universal Print Driver. Are you running that too?

I'd love to find a solution to this as well.

0 votes
answered by (140 points)

Check this link, related to HP Univ driver

Several users inform us that they have problem on Microsoft Windows 2003 – Terminal Servers with latest version of HP Universal Print Driver (4.7). Installation of this driver was not finished successfully and now after each user login to the system the installer tries to continue with installation of “32 Bit HP CIO Components”. This installer is running for a long time without success and blocked also installation of another applications which are using Microsoft Installer (MSI). We identify that Microsoft Installer related to the “32 Bit HP CIO Components” creates thousands registry API calls as a result of over 2000 – 4000 subkeys created in the registry for every mapped printer. The HP Support provides to us information that issue will be fixed in next update for HP Universal Print Driver (version 4.7.x).

Your answer

Your name to display (optional):
Privacy: Your email address will only be used for sending these notifications.
Anti-spam verification:
To avoid this verification in future, please log in or register