My HP All-in-one 6400 has lost a dll somewhere in the HP Solution

Well, it sounds like you went the proper route. My first suggestion is to UNINSTALL the old driver and software first before installing the new one.

Also, take care to note whether you have the 32-bit or 64-bit version of Windows 7, because they take very different drivers and software. Also, you have to watch closely on the HP site that it specifically says "64 bit" on the drivers if you do happen to have 64 bit Win 7. It's a pain sometimes.

1) Go to C:\program files\HP\digital imaging\bin\ and check how many folders are there for HPQSCLOC .If there are only one folder for HPQSCLOC in that case don't touch the folder.

2) Go to command prompt

TYPE THERE "CD..." AND HIT ENTER

KEEP TYPING "CD." AND HIT ENTER UNTIL WE SEE C:\

WHEN C:\ COMES

TYPE THERE- "regsvr32 /u hpqscloc.dll"

We may get an error in vista which says module failed to load

Follow Step 3

3) Open cmd prompt

Go to C:\

Type there

"regsvr32 hpqscloc.dll on"

4) Download and install

http://www.microsoft.com/downloads/details.aspx?FamilyID

=32BC1BEE-A3F9-4C13-9C99-220B62A191EE&displaylang=en

Download and install

http://www.microsoft.com/downloads/details.aspx?familyid

=A5C84275-3B97-4AB7-A40D-3802B2AF5FC2&displaylang=en

Try to scan

Or else follow step 5

5) Uninstall the imaging device and the solution centre

6) Download msicuu2 from microsoft.com

http://www.filewatcher.com/m/msicuu2.exe.189920.0.0.html

Run the windows cleanup utility

Delete AIO Scan from it

7) GO TO CMD PROMT

Then type CD programfiles\hp\digital imaging\bin

8) Type regsvr32 /u hpqscloc.dll

try scanning and check if it works or not

if not follow another step

9) Tried to uninstall the software

10) then install the software back

It will scan fine

You will have to re-install the Skype application in order to get rid off the error.
Please follow the below step:
1. download and install the Revo uninstaller application online(It's free).
2. Look for the "Skype" application and select the "uninstall" option.
3. Select "Advance" scan and remove all the remaining files of skype.
4. Reboot the computer.
5. download the d3d9.dll file from the following website http://www.dll-files.com/pop.php?dll=d3d9
6. Copy the d3d9.dll file and paste it at the following location C:\windows\system32
7. You will have to register the dll file before installing the skype application. To register the dll file:
Click on "Start" menu and select the "Run" option or Simply Windows key+R
Then, type regsvr32 d3d9.dll and click 'OK" .
8. Once the dll file is registered, you can install the Skype application and continue using it.
I hope this should fix the issue.
Thanks, Vicky

Its always best to reinstall the Printer software, if you encounter any DLL missing issue.

Uninstall and reinstall of printer software will fix the issue.

Delete and reinstall printer.

Uninstall the Windows defender and install am updated version. If it doesn't work, try this:
To resolve this problem, follow these steps:

1. Uninstall Windows Defender, and then reinstall Windows Defender. To do this, follow these steps:
1. Click Start, click Run, type appwiz.cpl, and then click OK.
2. Click Windows Defender, and then click Remove.
3. Follow the prompts to uninstall Windows Defender.
4. To reinstall Windows Defender, visit the following Microsoft Web site:
http://www.microsoft.com/athome/secu...yware/software (http://www.microsoft.com/athome/secu...yware/software)
2. If this issue is not resolved after you complete step 1, uninstall Windows Defender, use the Windows Installer CleanUp utility, and then reinstall Windows Defender. To do this, follow these steps:
1. Click Start, click Run, type appwiz.cpl, and then click OK.
2. Click Windows Defender, and then click Remove.
3. Follow the prompts to uninstall Windows Defender.
4. To use the Windows Installer CleanUp utility, click the following article number to view the article in the Microsoft Knowledge Base:
290301 (http://support.microsoft.com/kb/290301/ ) Description of the Windows Installer CleanUp utility
5. To reinstall Windows Defender, visit the following Microsoft Web site:
http://www.microsoft.com/athome/secu...yware/software (http://www.microsoft.com/athome/secu...yware/software)
3. If this issue is not resolved after you complete step 2, follow this step:
1. Click Start, click Run, type regsvr32 file name, and then click OK.

Note In this step, file name is a placeholder for the following files.

Repeat this procedure for the following files:
* wuapi.dll
* wuaueng.dll
* wucltui.dll
* wups.dll
* wuweb.dll
* atl.dll
* softpub.dll
* wintrust.dll
* initpki.dll
* mssip32.dll"

cheers ...

Solution:

i) usually whenever there is virus, spyware, ... in your system some of the .dll will be lost or will lead to curruption or partial currption(some data or all the data in the .dll will be lost)

ii) as such some .dll files are heart or important to run system, some .dll files play mere role.

iii) when such .dll files are lost the program using these .dll files cannot locate or find their .dll files in such you get errors message as u said......

iv) as u debuging is not possible in the normal way until unless you have some debugging program or software such as "Visual Studio 2005" or Visual BASIC TOOLS....

v) due to loss of some important .dll files your system might shutdown frequently..... but you are fortunate that you are getting error message....and these .dll play mere role....

vi) i would suggest to install some best rated antivirus, spyware( Bit Defender -rated top, AVG, Norton....) after perform full system scan try reinstall your OS or format your system or load OS Freshly....

Thanking you

M. Sridhar

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 ;)

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 ;)