When I instal my Hp All-In-One then a massage come- Error1904,Module C:\Windows\system32\msxml4.dll failed to register. HRESULT -2147024770. Contact your support personnel. Please go to http;//www.hp.com/support for troubleshooting information about "/Fatak Error" and "MSI.Scan" My Laptop is Compaq 620 Email ID- [email protected]

It happens when application failed to register into registry,
1)Log On into administrator account (OR)
2)Right click the application and run as administrator

Hello,

This problem can occur when one of the following conditions is true:

• The file is not installed correctly.
• The file is corrupted.
• Other programs, including memory-resident and anti-virus programs, are running and using any version of the file.

Register the File Manually loadTOCNode(2, 'workaround'); To register a specific file again in the registry, while you are working in Microsoft Windows, follow these steps:

1. Click Start and then click Run.
2. In the Open box, type the following command, and then click OK RegSvr32 filenamewhere filename is the name of the file specified in Error 1904.

You should receive a message that the file is now correctly registered. If this doesn't fix your problem then go to http://support.microsoft.com/kb/237294 for further options.

Hope that this helps!
HelpDeskMan

Please rate this and/or leave a comment. Thank you

If it is an old printer there may not be a driver for it on your current operating system. Do a search from google and type Windows Vista/7 compatible driver for "your model" printer. I had the same problem once so i found a driver for another printer and it made mine work with windows 7.

No need to pay. Open up Add/Remove, look for anything relating to "Flash Player", and remove it.

Then go here to download Flash player again, and go along with the installation process. Once finished, try opening up DVD Copy plus.

Are you installing as administrator?

you could try:
Start->run
and type in the following line
regsvr32 "C:Program Files (x86)MasterCook 9ProgramMCWrap.dll"
or wherever the .dll path was
then try reinsalling.

When I installed it, I right clicked on the install file, and clicked RUN AS ADMINISTRATOR.

Try reading this:
mc6help.tripod.com/mastercook_and_vista.htm

Hello Gomatesh_b, I've read a article on it just a month before, i think, it will also help you. There toll-free number was +1 (844) 355-5111.

I think you're facing this problem, check out this kb article from ms, it has your syntom and possible solutions.. I hope it helps:

http://support.microsoft.com/kb/279223

Try download he right software for your OS from HP.com, typically software issue. Be sure to choose the right language for your full software solution, get fatal error when trying to install software with wrong language support.

OK, here is my debugged/tested solution.

I know your error refers to a different installer MSI file (CIOUM32.msi) but the installation component in your log file (ipm12.A4B24390_80AD_4BAF_B8FD_C670FE0DB586) is identical to the one that was giving me trouble as well (i.e. points to the same service/file). So it is definitely worth a shot to try this solution out as it will only take a few minutes.

My Scenario:

OS: MS Windows XP SP3 [Version 5.1.2600]
Printer: HP LaserJet 3390 (AiO) (Firmware datecode: 20070331)
Printer Connection: Connected via Ethernet with a static IP address
HP Driver Version: v4.0 (hp_LJ3050-3052-3055-3390-3392_Full_Solution_AMWE.exe)

Ran into same error that everyone else is experiencing. (see below)

Now Launching=X:\hpzmsi01.exe -m dot4msi -l XXX -f X:\DIVins??.DAT
Error message received: The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2753.
X:\HPZBDI32.msi failed with return code 1603
MSIInstall() failed with 1603
Exit code=1603

After debugging HP's installation scripts for 2 days, here is the cause & solution I identified to this specific install error. Once I got passed this error, everything installed without error and all functionality was working properly (including scanning!).


BACKGROUND:

Microsoft Installer (MSI) error 1603 is simply a generic "A fatal error occurred during installation" -- see http://msdn.microsoft.com/en-us/library/aa368542(VS.85).aspx. This is basically MSI telling you that something very bad has happened during the installation. In order to get more details, you can turn on MSI debug logging by following this MS Knowledge Base article (http://support.microsoft.com/kb/223300).

The MSI error code 2753 is the code for "The File '<file name>' is not marked for installation.". This error can be triggered by many scenarios, but usually, it has to do with the actual installation script not properly checking for the existence/non-existence of an installation file and then not marking it for either installation/removal. I know this sounds confusing, and it is. If your curious about all the possible causes, just Google for "msi 2753 not marked for installation" and you'll see lots of results which you can peruse for your own enjoyment.

In order to identify what was causing these 2 errors, I enabled debugging for MSI via the aforementioned MS KB article

CAUSE:

Certain HP services (and associated DLL files) were somehow partially/improperly installed. (Possibly, from a previous failed install?)

The Windows services (files) were:

Pml Driver HPZ12 (C:\Windows\System32\HPZipm12.dll)
Net Driver HPZ12 (C:\Windows\System32\HPZinw12.dll)

The existence of these 2 files in the System32 directory was causing this error in my situation. Somehow, the installation script was not identifying that these files were already installed (or improperly installed) and failing to properly set them to be installed again.

SOLUTION:

Steps:

1) Check to make sure that the 2 Windows services above are not running (or not installed).
2) Rename/delete the 2 associated service DLL files (this will only be possible once the services are stopped)
3) Run the installation again.

If all goes well, the install should now run without any issues.


Hope this helps since many people (including myself) have spent a lot of time (and HP Support chats) trying to find a workaround for this issue.

If you find this solution helped you out, please feel free to make a small donation to my PayPal ;)