PowerCLI new-vm fails with operation is not valid due to current state of object

Products

• VMware vCenter Server

Issue/Introduction

Execution of the new-vm cmdlet via PowerCLI within VSCode results in the following console error: "operation is not valid due to the current state of the object".

Despite this error in the client, the corresponding virtual machine creation task completes successfully within the vCenter Server Recent Tasks. Executing the PowerCLI debug command get-errorreport yields no explicit failure data or root cause indicators.

Environment

vCenter Server 8.0
VMware PowerCLI 9.0

Cause

A stale or corrupted cache/state within the active PowerShell session or VSCode environment causes the PowerCLI cmdlet to return a false failure state locally.

Resolution

1. Terminate the active VSCode application and all associated PowerShell sessions.

2. Launch a new instance of VSCode to initialize a fresh PowerShell session.

3. Re-authenticate to the vCenter Server using the Connect-VIServer cmdlet.

4. Execute the required new-vm PowerCLI cmdlets within the clean runtime environment.