About this article: This article is reviewed against the cited sources. This is source research, not lab validation. Check the stated versions and your own requirements before making changes.
When vSphere Lifecycle Manager (vLCM) fails to remediate an ESXi host, the vSphere Client message is usually general, for example "Remediation failed for Host. An internal error occurred while staging/remediating the host." The cause is written in two logs: lifecycle.log on the host and vmware-vum-server.log on vCenter. Run the remediation pre-check first, then read those logs, match the line to one of the documented causes below, and fix only that one. Most failures fall into five groups: the image would downgrade a component, the host's staging area is stale, a package signature is not trusted, the depot is missing or corrupt, or the host cannot enter maintenance mode.
What the error means
Remediation makes the host match the cluster image: vLCM checks the host, stages the new packages on it, puts it in maintenance mode, installs and, if needed, reboots. A failure at any step gives a task error. The TechDocs page Remediating a Cluster or a Standalone Host Against a Single Image explains why one host can stop the whole job: "the ESXi hosts in the cluster are remediated sequentially by default. So, if the remediation for a single host in the cluster fails, the remediation of the entire cluster stops."
The pre-check is the read-only first step. TechDocs Run a Remediation Pre-Check: "These checks include extensive health checks to determine whether the cluster or host is in a stable state and to ensure successful remediation." After it, "you can view compliance information for each host and whether host reboot or maintenance mode are necessary for successful remediation."
Likely causes
| Cause | What you see | How to confirm |
|---|---|---|
| Image would downgrade a component | "Downgrades of manually added Components <Component_Name> in the desired ESXi version are not supported." | Compare esxcli software component list with the image (KB 426960, 440252) |
| Stale staging directory | "An internal error occurred while staging/remediating the host." | lifecycle.log: "Can not open /var/vmware/lifecycle/stagebootbank/vmx.v00" (KB 393457) |
| Untrusted package signature | "VIB contains an invalid or corrupted signature" | lifecycle.log: "Could not find a trusted signer" (KB 449493) |
| Component missing from depot | "The specified solution cannot be found in depots." | vCenter log SolutionNotFound (KB 446554) |
| Corrupt depot metadata | com.vmware.vcIntegrity.ScanFailed, or a VIB checksum error |
vCenter log "Failed to get filesize for" a metadata zip (KB 392118, 389798) |
| Mixed vendor components | Remediation times out; "Component {1} has unmet dependency {2}." | vCenter log Validate.Depend (KB 381675) |
| vCenter VM on the host, DRS off | Pre-check "May Not Remediate" | Full pre-check report names the vCenter VM (KB 417492) |
| Host cannot enter maintenance mode (standalone or non-DRS host) | Task stuck at 22% or fails | vCenter log "The operation is not allowed in the current state." (KB 434515) |
| Package fails image rules | "Staging did not succeed for the ESXi Host." | VibValidationError in logs (KB 443416) |
| Two packages claim one file | "Remediate entity: Cannot execute upgrade script on host" | "claimed by multiple non-overlay VIBs" (KB 334592) |
| Host storage full (title says 6.x and 7.x; environment line says 7.0 and 8.0) | "error code:15" | esxupdate.log "No space left on device" (KB 322888) |
Prove the cause before changing anything
1. Run the pre-check. On the cluster, Updates > Image > "In the Image Compliance card, click the Run pre-check button." TechDocs: "If issues are reported, resolve the issues before you remediate the cluster or the standalone host." To see an earlier result, the View Last Remediation or Remediation Pre-Check Results page says to "select Last pre-check results" or "select Last remediation results."
2. Read the host log. On the failed host, the image install log is /var/run/log/lifecycle.log (KB 393457; KB 449493 writes it as /var/log/lifecycle.log). Look for lines marked Er(11). On 6.x and 7.x hosts, also read /var/log/esxupdate.log.
3. Read the vCenter log. On the vCenter appliance: /var/log/vmware/vmware-updatemgr/vum-server/vmware-vum-server.log (KB 446554). Search for com.vmware.vcIntegrity and the host name around the task time.
4. Match the line.
- Downgrade. KB 426960: "the target ESXi image defined in the vLCM cluster contains a version of a component that is older than the version currently installed on the host. vLCM does not support automatic downgrades during the remediation process." KB 440252 gives read-only checks to see which drivers are installed and which are in use:
esxcli software component list
esxcli software vib list
esxcli hardware pci list | awk '/Module Name:/ {print $3}' | sort -u
esxcli network nic list
esxcli storage core adapter list
- Stale staging. KB 393457's lifecycle.log line ends "No such file or directory: '/var/vmware/lifecycle/stagebootbank/vmx.v00'". Its cause: "The error is caused by a stale or corrupted stagebootbank directory." Read-only check:
ls -lah /var/vmware/lifecycle/stagebootbank. - Signature. KB 449493: "the VIB package is signed by a certificate authority that is not included in the ESXi’s trusted certificate store." The page notes the host time is correct in this case, so check time first.
- Depot. KB 446554: "a specific software component or solution … defined in the cluster's desired state image is missing from the vSphere Lifecycle Manager depot." KB 392118 shows "Failed to get filesize for: /storage/updatemgr/patch-store/hostupdate/<VENDOR_DIRECTORY>/metadata_####.zip". KB 389798: "This is due to corrupt metadata in the VUM database backing vCLM."
- Mixed vendors. KB 381675: "The host is configured with an image from one vendor (here, Dell), but the additional components that have been added are from another vendor (here, Cisco)."
- File claimed twice. KB 334592 gives a test that changes nothing:
esxcli software vib remove --vibname=<VIB_NAME> --dry-run, which runs "without making any changes to the ESXi host".
5. Check maintenance mode readiness. TechDocs: "When you remediate a cluster that contains a single ESXi host or that has vSphere DRS deactivated or in manual mode, the remediation process cannot put that host into maintenance mode." KB 434515 shows the vCenter log line "DRS reported issues that prevent host '<HOST_FQDN_OR_IP>' from entering maintenance mode." If the host is stuck entering maintenance mode, the stage-by-stage checks in the related maintenance-mode article apply.
Example (illustrative): cluster prod-b stops at host esx12 with the internal staging error. lifecycle.log shows the missing stagebootbank/vmx.v00 file. That points at KB 393457, not the image or the depot.
Fix
Fix only the cause the logs show.
Image downgrade. KB 426960 Option 1: "Update the Cluster Image … include a version of the component that is equal to or higher than the version currently installed on the ESXi host." Option 2 removes the component from the host; KB 426960 only says to use ESXCLI, and the command is in KB 440252: esxcli software component remove -n <name>. Risk: KB 440252: "Do not remove or replace driver components until confirming they are not used by active hardware. Removing a driver that is bound to an active storage, network, or boot device causes host connectivity or boot issues." Disruptive step: KB 440252 requires the host to be in maintenance mode with "all virtual machines are migrated or powered off", then "Reboot the host: reboot". Way back: exit maintenance mode; reinstall the removed component from the vendor's offline bundle. vLCM shows the host non-compliant until the image and host match. Prefer Option 1.
Stale staging. KB 393457: rename the directory so vLCM builds a fresh one, then stage again:
mv /var/vmware/lifecycle/stagebootbank /var/vmware/lifecycle/stagebootbank.bak
"If the issue persists, ensure there is sufficient space on the host ramdisk by running vdf -h."
Untrusted signature. KB 449493 Option 1 (Recommended): "Contact the third-party vendor to obtain an updated VIB bundle that is officially signed by a VMware-trusted Certificate Authority." Its Option 2 lowers the host acceptance level and installs with --no-sig-check. Risk: it turns off signature checking for that package, and "Installing VIBs manually via CLI will cause the ESXi host to become 'Non-Compliant' in vLCM." Use only with the vendor's agreement.
Missing component in depot. KB 446554: "Navigate to Lifecycle Manager > Image Depot. Select the Actions menu or the Import Updates link." Import the missing add-on or component, then re-run compliance. KB 389798 also starts with a re-import of the component or vendor add-on.
Corrupt depot metadata. KB 392118 resets the update manager database and patch store:
service-control --stop vmware-updatemgr
python /usr/lib/vmware-updatemgr/bin/updatemgr-utility.py reset-db
rm -rf /storage/updatemgr/patch-store/*
service-control --start vmware-updatemgr
Disruptive step: "Resetting the Update Manager database is a destructive task. Custom baselines (but not Cluster Images), custom download settings and manually imported patches/ISOs will be removed". KB 392118 says to "Take simultaneous powered-off snapshots for the vCenter VM and any other nodes it is in Enhanced Linked Mode with." Do it only after re-importing has failed. The vCenter VM is powered off while those snapshots are taken, so the vSphere Client is unavailable until it is back. After the services start: "Log in to the vSphere Client, navigate to Lifecycle Manager > Settings > Patch Setup, and click Sync Updates. Once the sync is complete, retry the host scan." Then re-import the vendor add-on and image (KB 389798: Lifecycle Manager > Actions > Import Updates).
Mixed vendors. KB 381675's cause is "incorrect vendor components added to the cluster image SoftwareSpec." Edit the image so the added components belong to the same hardware vendor as the add-on. KB 381675 then removes the opposing vendor's VIBs from the host: esxcli software vib list, then esxcli software vib remove --vibname=<vib_name>, then "Reboot the ESXi Host." Disruptive step: put the host in maintenance mode first, with its VMs moved or off; the reboot takes the host down. Way back: exit maintenance mode; reinstall a removed VIB from the vendor's bundle. vLCM shows the host non-compliant until the image matches.
vCenter VM or maintenance mode. KB 417492: "Enable DRS for the cluster. Manually migrate the vCenter Server virtual machine to a different host in the cluster." For a standalone or non-DRS host, power off or move the VMs, or set the remediation policy to power them off. KB 434515 adds that if the task stays stuck after that, "it may be necessary to restart the Update Manager service". Disruptive step: powering VMs off stops their services.
Package fails image rules or file claimed twice. KB 443416's example is one legacy CommunitySupported package, circuit_rewind_bootbank_ipmitool_1.8.18. Find the name of your package in esxupdate.log (VibValidationError: VIB <name> violates extensibility rule checks). KB 443416 then places the host in Maintenance Mode and removes the package with esxcli software vib remove -n <name> after you "ensure that the vib is not currently in use"; "If the command output states Reboot Required: true, reboot the host". KB 334592 removes the conflicting package once the dry run confirms the change, after engaging the hardware vendor. Risk: removing the wrong package can remove a working driver; confirm with the hardware or software vendor. Disruptive step: the host is in maintenance mode, with VMs moved or off, and may reboot. Way back: exit maintenance mode; reinstall the package from the vendor bundle if needed. vLCM shows the host non-compliant until the host matches the image.
Host storage full (error code:15). KB 322888: "Use df /locker to find how much the disk has been consumed." If the disk is still more than half used, "Run du -ah /locker/* to find out what are in the locker, remove large files in the directory", then retry. Risk: a deleted file cannot be recovered; remove only files you can identify as unneeded.
Settings that block remediation. TechDocs Remediation Settings: "If a host has no running virtual machines, DPM might put the host in standby mode, which might interrupt a vSphere Lifecycle Manager operation." And "If FT is turned on for any of the virtual machines on a host, vSphere Lifecycle Manager does not remediate that host."
Confirm the fix
- Run the pre-check again: no issues for the host.
- Remediate the single host first, then the cluster.
- The host shows Compliant in the Image Compliance card.
esxcli software component listshows the versions in the image.- lifecycle.log has no new
Er(11)lines for the run, and the vCenter log noScanFailedorSolutionNotFound.
What to watch afterwards
- Components added by hand outside the image cause the downgrade and non-compliance cases.
- Depot imports after every vendor release, before the patch window.
- DRS, DPM and FT settings before remediation.
- Host ramdisk and storage space before staging.
Read next
Related articles you may want next.
- VMwareHow to patch an ESXi cluster with vSphere Lifecycle ManagerPrepare an image-based maintenance wave with compatibility, evacuation and application acceptance gates.Read article
- VMwareESXi host stuck entering maintenance mode at 2%, 19% or 29–32%ESXi host stuck entering maintenance mode? Use the percentage to find the cause: precheck at 2%, VM moves at 19%, DRS or vCLS at 29–32%. Prove it first.Read article
- VMwarePlanning a vSphere Major Upgrade: Order, Interoperability and a Go/No-Go RecordPlan a vSphere 7 to 8 upgrade: follow Broadcom's update sequence, check interoperability and upgrade paths, clear removed features, and record a go/no-go decision.Read article
Risks and limits
- Each Broadcom page covers one error; a log line that matches none of them belongs with Broadcom support, with the pre-check report and both logs.
- The KB 392118 reset and removing drivers or packages are the steps that can do lasting harm. Snapshot vCenter first, and never remove a driver the host is using.
NetLeverage runs its own hosting on VMware vSphere, vCenter and ESXi. Talk to an engineer.
Sources
- Run a Remediation Pre-Check for a Cluster, a Host Within a Cluster, or a Standalone Host — Broadcom TechDocs, Last Updated October 28, 2026, accessed 17 November 2026
- View Last Remediation or Remediation Pre-Check Results for a Cluster — Broadcom TechDocs, Last Updated October 28, 2026, accessed 17 November 2026
- Remediating a Cluster or a Standalone Host Against a Single Image — Broadcom TechDocs, Last Updated October 28, 2026, accessed 17 November 2026
- vSphere Lifecycle Manager Remediation Settings — Broadcom TechDocs, Last Updated October 28, 2026, accessed 17 November 2026
- Pre-check fails for image-based remediation via vLCM in the vCenter Server (KB 426960) — Broadcom, Updated On 07-30-2026, accessed 17 November 2026
- “Downgrades of manually added Components… are not supported” during vLCM image remediation on ESXi hosts (KB 440252) — Broadcom, Updated On 11-13-2026, accessed 17 November 2026
- Remediation failed for Host. An internal error occurred while staging/remediating the host. (KB 393457) — Broadcom, Updated On 07-31-2026, accessed 17 November 2026
- vSphere Lifecycle Manager remediation fails with "VIB contains an invalid or corrupted signature" (KB 449493) — Broadcom, Updated On 07-23-2026, accessed 17 November 2026
- "The specified solution cannot be found in depots" error during vLCM compliance check (KB 446554) — Broadcom, Updated On 07-01-2026, accessed 17 November 2026
- Error: com.vmware.vcIntegrity.ScanFailed due to missing metadata - vSphere Lifecycle Manager (KB 392118) — Broadcom, Updated On 08-08-2026, accessed 17 November 2026
- vLCM cluster remediation fails with VIB checksum error (KB 389798) — Broadcom, Updated On 09-22-2026, accessed 17 November 2026
- vLCM Pre-Check Shows "May Not Remediate" Status for a Specific Host (KB 417492) — Broadcom, Updated On 12-01-2025, accessed 17 November 2026
- Troubleshooting ESXi Host Remediation Tasks Hung or Failing Maintenance Mode (KB 434515) — Broadcom, Updated On 03-25-2026, accessed 17 November 2026
- ESXi Staging Fails with VibValidationError for circuit_rewind_bootbank_ipmitool in vSphere Lifecycle Manager (KB 443416) — Broadcom, Updated On 06-15-2026, accessed 17 November 2026
- ESXi upgrade failing with the error “Remediate entity: Cannot execute upgrade script on host” (KB 334592) — Broadcom, Updated On 10-09-2025, accessed 17 November 2026
- Remediation of ESXi host via vSphere Lifecycle Manager (vLCM) times out (KB 381675) — Broadcom, Updated On 09-08-2025, accessed 17 November 2026
- "The host returns esxupdate error code:15" error when remediating an ESXi 6.x and 7.x host (KB 322888) — Broadcom, Updated On 09-15-2026, accessed 17 November 2026
This article was originally published on .