Error 0x800701E3: The request failed due to a fatal device hardware error

SOURCE: I/O Device Error on External Hard Drive

try doing a disk check on it

1 hold down the windows key and press r
2 type in cmd
3 in the shell window type in chkdsk /F /X e:
Replace the E: with your harddrive letter

Posted on May 04, 2008

SOURCE: psp: I/O device error.

Its 100% because of the Bad cable.. Change the USB cable it will work fine

Posted on Jul 24, 2008

SOURCE: Windows has encountered a problem communicating

I had similar problem with a Dell Optiplex 760 desktop . I went to BIOS disable external SATA and all additional ports which is not used like parallel and serial ports and it worked. I think its with SATA settings only .

Posted on May 25, 2009

SOURCE: an mtp device cannot start due error code 10 whats that

I solved the code 10 problem on my vista 64 by using Revo uninstaller on the next to highest level to remove Acronis 10.4942 After this all media readers appeared and worked. A later version of Acronis Emergency boot disk still works to backup/ restore my system

Posted on Jun 22, 2009

SOURCE: Fatal error installing HP 3055 all in one

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

Posted on Oct 30, 2009