Knowledge Base

The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides
Search the VMware Knowledge Base (KB)   View by Article ID

VMware ESX 3.5, Patch ESX350-200810202-UG: Updates ESX Scripts (1007042)


Release Date: 11-06-2008

Download Size:
Download Filename:

Product Versions ESX 3.5 Update 3
Patch Classification General


Requires None
Virtual Machine Migration or Shutdown Required No
Host Reboot Required No
PRs Fixed 292427 298500 293214 278194 328090 308352 300927 322739 315746 330895 310670
Affected Hardware N/A
Affected Software N/A
RPMs Included VMware-esx-scripts
Related CVE numbers None


Summaries and Symptoms

This patch fixes the following issues:

  • The esxupdate utility should exit if the bundle specified cannot be installed because of missing dependencies.

    Symptoms: Previously, if you used the command esxupdate –d <depot> -b <bundle> to install a bundle with one or more dependencies missing from the depot, the esxupdate utility did not install the specified bundle (as expected). However, if some dependencies existed in the depot and could be installed, esxupdate installed these dependencies, even though the specified bundle could not be installed. This unexpected behavior no long occurs with this release. Now, when you specify a bundle with the -b option and the specified bundle has one or more dependencies missing from the depot, esxupdate exits with an error message. The message notes the missing top-level dependency.

  • The esxupdate query command does not display obsolete bundles.

    Symptoms: In prior releases of ESX, the esxupdate query command does not list the obsolete bundles. To resolve this issue, the esxupdate utility adds two new options:
    -a or --listall: This option displays all installed bundles, including obsolete bundles.
    -o or --onlyobsolete: This option displays only obsolete installed bundles.

  • Add experimental support for a new utility, the VMDK Recovery Tool.

    You can use this tool to recover .vmdk files that have been corrupted or deleted. For more information, see

  • The esxupdate utility fails to resolve multi-level dependencies during patch installation.

    Symptoms: ESX 3.5 Update 2 introduced the use of a baseline for patch bundle installation. However, the baseline handles only one level of bundle requirements.

    Example: The following bundles exist in the depot, but they are not installed. Bundle A requires B, which requires C. Here, the command esxupdate -b <A> fails because C is not in the baseline.

Deployment Considerations

None beyond the required patch bundles and reboot information listed in the table, above.

Patch Download and Installation

See the VMware Update Manager Administration Guide for instructions on using Update Manager to download and install patches to automatically update ESX Server 3.5 hosts.

To update ESX Server 3.5 hosts when not using Update Manager, download the most recent patch bundle from and install the bundle using esxupdate from the command line of the host. For more information, see the ESX Server 3 Patch Management Guide.

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.


  • 0 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)
  • 0 Ratings