If you are seeing this error in vSphere 7.x or 8.x, the most likely cause is the retirement of legacy VMware repository URLs (like hostupdate.vmware.com ) in favor of authenticated endpoints.
This error often signifies a breakdown in the communication chain between the vCenter Server and the external patch repositories or internal ESXi hosts. Modern vSphere environments (vSphere 7.0 and later) have transitioned to a managed by Broadcom, which has deprecated many legacy "common" URLs. 1. Update Download URLs and Tokens (Modern vSphere) If you are seeing this error in vSphere 7
The task often fails because the ESXi hosts cannot reach the "patch store" on the vCenter Server (Lifecycle Manager). Replace old URLs with the new customer-specific URLs
In the vSphere Client, navigate to Lifecycle Manager > Settings > Patch Setup . Replace old URLs with the new customer-specific URLs provided by Broadcom. 2. Network and Port Configuration
Log in to the Broadcom Support Portal to generate your unique "Download Token".
Ensure your firewall allows outbound traffic to dl.broadcom.com , vvs.broadcom.com , and storage.googleapis.com . 2. Network and Port Configuration