Search the VMware Knowledge Base (KB)
View by Article ID

Troubleshooting issues when Update Manager is unable to stage patches to an ESX/ESXi host (1032625)

  • 5 Ratings


  • Unable to stage patches to an ESX/ESXi host using VMware vCenter Update Manager.
  • In vCenter Update Manager, you see the error:
Failed to import upgrade. Error was: failed upload
  • In the C:\Documents and Settings\All Users\Application Data\VMware\Update Manager or C:\Users\All Users\VMware\VMware Update Manager\Logs\vmware-vum-server-log4cpp.log, you see entries similar to:

    <YYYY-MM-DD>T<TIME> ['HostUpgradeMetadata' 3456 ERROR] [metadata, 796] Can not read MD5 checksums, error: ios_base::failbit set
    <YYYY-MM-DD>T<TIME> ['HostUpgradeMetadata' 3456 ERROR] [metadata, 834] Cannot process MD5 checksums in cosless upgrade package, error: integrity.fault.HostUpgradeChecksumFailure
    <YYYY-MM-DD>T<TIME> ['HostUpgradeMetadata' 3456 ERROR] [metadata, 894] Integrity verification of upgrade package failed.

  • Attempting to run the task may report the error:

    Operation failed since another task is in progress


This article helps you to troubleshoot issues when Update Manager is unable to stage patches to an ESX/ESXi host.


Validate that each troubleshooting step below is true for your environment. The steps provide instructions or a link to a document, for validating the step and taking corrective action as necessary. The steps are ordered in the most appropriate sequence to isolate the issue and identify the proper resolution. Do not skip a step. 
  1. Verify that you are applying the correct patch bundle and baseline to the ESX/ESXi host. For more information, see Using the proper upgrade bundle when upgrading an ESX/ESXi 4.x host to a newer version (1020673).
  2. Ensure that name resolution is working correctly between all ESX/ESXi hosts and your vCenter/Update Manager server. For more information, see Identifying issues with and setting up name resolution on ESX Server (1003735).

  3. Verify that network connectivity exists between the Update Manager server and the ESX//ESXi host you are trying to stage. For more information, see Cannot connect to the remote server when downloading the Update Manager or Converter plugins (1004887).

  4. Verify that your ESX host has the required disk space to perform operations on the host. For more information, see Investigating disk space on an ESX host (1003564)

  5. When a virtual machine is inaccessible from vCenter Server or is connected directly to the ESX/ESXi host using the vSphere Client, Update Manager fails because it cannot verify the power status of the virtual machine and, therefore, cannot put the host into Maintenance Mode. To troubleshoot this issue, see Assessing commonalities of an outage affecting multiple virtual machines (1019000).

  6. Ensure that the network connecting Update Manager and the ESX/ESXi host is not slow. The network speed may be slow if the host or Update Manager is across a long distance WAN. For more information, see vCenter Update Manager host tasks might fail in slow networks (1021050).

  7. If you are applying multiple updates at once, the multiple tasks may take a long time to complete. To troubleshoot this issue, see vCenter operation times out with the error: Operation failed since another task is in progress (1004790).
If the issue continues to exist after performing the steps in this article:

See Also

Update History

03/27/2014 - Added vSphere Update Manager 5.0.x/5.1.x/5.5.x to product versions.

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.


  • 5 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.

What can we do to improve this information? (4000 or fewer characters)

Please enter the Captcha code before clicking Submit.
  • 5 Ratings