Updating an ESXi host through 'esxcli software profile update' command fails with message "Host is not changed".

Products

• VMware vSphere ESXi

Issue/Introduction

When attempting to update an ESXi host using the esxcli software profile update command, the operation fails with the message "Host is not changed".

The command line (vmware -v) and the vSphere Client UI Hypervisor version display the upgraded target version (e.g., 7.0 U3w). However, the active image profile name still reflects the older version (e.g., 7.0 U3v).

Environment

VMware vSphere ESXi

Cause

The 'esxcli software profile update' command evaluates the VIBs in the target profile against the VIBs currently installed on the host. It will only apply VIBs that are newer. If the host's VIBs were already updated to the target version via an alternative method (such as installing individual VIBs directly) rather than a holistic profile update, the command calculates that there are no newer VIBs to apply. Consequently, the update transaction is bypassed, and the old image profile name is retained despite the host running the updated binaries.

Resolution

The update using the profile can be skipped here since the ESXi host is already at the target version.

If you are very particular about the profile showing the old version, the profile must be forcefully installed rather than updated.

1. Connect to the ESXi host via SSH using root credentials.

2. Place the host in maintenance mode.

3. Verify the currently active profile:

   esxcli software profile get

4. Execute the profile installation. This forces the host to adopt the exact VIB state and profile name of the target depot, bypassing the newer-version check:

   esxcli software profile install -d <path_to_depot.zip> -p <profile_name> 

   Note: Replace <path_to_depot.zip> with the absolute datastore path to the offline bundle and <profile_name> with the exact name of the target profile (e.g., ESXi-7.0U3w-standard).

5. Reboot the ESXi host to finalize the profile application.

Note: The update command is the standard and safer method for routine patching, as it safely preserves third-party or newer custom VIBs. The install command strictly overwrites the host's active state to match the target profile identically. Administrators should verify that no required third-party drivers (such as custom network or storage VIBs) will be downgraded or removed during an install operation.