Subject: Applicable VIX C reference for Workstation 26.0.1 build-25688693, Windows AMD64
Please identify the VIX C API revision and authoritative headers/reference applicable to the AMD64 VIX library distributed with VMware Workstation Pro 26.0.1 build-25688693 (26H1u1). A documented compatibility mapping to an existing API reference is sufficient; a newly numbered SDK is not required.
The vendor-maintained open-vm-tools declarations at commit 1634dfb42f723d2c1b3b6cf2696efc82407fae5b include VixHost_Connect, VixHost_OpenVM, VixPropertyList_AllocPropertyList, VixVM_LoginInGuest, VixVM_LogoutFromGuest, both VixVM_CopyFile functions, VixVM_RunProgramInGuest, VixJob_CheckCompletion/GetError/Wait, VixVM_PowerOff, Vix_GetProperties, Vix_ReleaseHandle/AddRefHandle, Vix_FreeBuffer, VixHost_Disconnect and Vix_GetErrorText. The legacy official VIX1.13 OpenVM and GetProperties reference URLs now return404.
Please provide the applicable C API programming/reference material answering:
1. Exact type definitions, calling convention, variadic property argument types/terminators, and API-version mapping for this Windows AMD64 implementation.
2. When path, username, password, property-list and callback clientData storage may be released or reused; which inputs are copied versus retained, including on failure or incomplete asynchronous operations; callback threading and lifetime rules.
3. Caller ownership/reference counts for host, VM, job and property-list handles, returned strings/arrays/buffers, borrowed error text, and partially populated outputs. Please specify the correct release routine and error-path obligations for each.
4. Encoding of credentials, Windows paths, program arguments, property strings and error text, including non-ASCII handling.
5. The supported use of VIX_PROPERTY_VM_ENCRYPTION_PASSWORD (7001), including allocation/copy/lifetime rules, and whether an independent process/connection can reopen an encrypted vTPM VM using an explicit in-memory password without a remembered credential or GUI unlock. Please distinguish documented limitations from behavior requiring verification.
6. Job-completion meaning, release/disconnect effects on pending work, any supported cancellation contract, hard power-off semantics and the guarantees of a subsequent power-state observation from a separate connection.
No credentials, private logs or memory dumps accompany this request. We seek the documentation and applicability statement, not remote access, troubleshooting execution or an assertion of complete secret-memory erasure.