For users running ESX 8.0 Update 3 releases prior to Update 3g, applying patches may result in a pre-check failure with a SHA-1 signature error due to memory exhaustion, as outlined in KB 433124. The knowledge base article also describes a resolution that involves increasing the memory limit for one of the ESX system resource pools by using localcli.
Since localcli is the local version of ESXCLI, the command must be executed directly on the ESX host, typically requiring SSH access. An alternative approach is to use the vSphere API, which exposes the ESX system resource pool configuration, which means we can use tools like PowerCLI. This allows the same workaround to be applied remotely without requiring SSH or direct access to the ESX host.
