1-800-691-1991 | 9am - 8pm ET

Could not invoke guest operation error in a job when using vSphere API for Guest OS connection


When Microsoft User Profile Disks (for example, in a Windows RDS farm) are used, Veeam Application Aware Image Processing through vSphere API may fail with the following error: Could not invoke guest operation.


When processing Guest OS data through vSphere API, Veeam needs to deploy a runtime component in a temporary location. C:\Windows\Temp\ folder had been used for these purposes previously. However, starting from 10.2.0 VMware tools’ version, the Temp folder location has been changed to C:\Users\username\Temp\. 

When User Profile Disks feature is used, Windows has no User’s profile temp folder unless a User is logged in (once a User is logged out, Temp folder is deleted). Hence, Veeam has no temp folder to place its components in.


VMware is planning to address this issue in one of the next VMware tools releases. As a workaround, you may want to downgrade VMware tools version to an earlier version or set up a direct network connection to the Guest OS from a Guest Interaction Proxy
Veeam Backup & Replication
Last Modified:
Please rate how helpful this article was to you:
5 out of 5 based on 1 ratings
Thank you for helping us improve!
An error occurred during voting. Please try again later.

Couldn't find what you were looking for?

Below you can submit an idea for a new knowledge base article.
Report a typo on this page:

Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!

Spelling error in text

Knowledge base content request
By submitting, you agree that your personal data will be managed by Veeam in accordance with the Privacy Policy.

ty icon

Thank you!

We have received your request and our team will reach out to you shortly.


error icon

Oops! Something went wrong.

Please go back try again later.