Directly contact our Support Team

How to troubleshoot saving Office files on VMware with vShield virtual machines

Bitdefender GravityZone provides full visibility into organizations' overall security posture, global security threats, and control over its security services that protect virtual or physical desktops, servers and mobile devices. All Bitdefender's Enterprise Security solutions are managed within the GravityZone through a single console, Control Center, that provides control, reporting, and alerting services for various roles within the organization

Security for Virtualized Environments (SVE) is the first comprehensive security solution for virtualized datacenters. The solution protects virtualized Windows, Linux, and Solaris systems, both servers and desktops. While integrated with VMware vShield, the unique architecture of the solution allows it to be leveraged when using any system virtualization offering.

This article provides help to troubleshoot issues regarding saving Microsoft Office files to Windows Shares on virtual machines protected by VMware vShield Endpoint and Bitdefender Security for Virtualized Environments.


One of the following situations may occur when trying to save a document to a shared folder:

  • Microsoft Office files fail to save to a Windows Share.
  • Files saved to the share are empty and 0KB in size.
  • When saving files from a Microsoft Office 2007/2010 application to a share on a virtual machine, which is protected with GravityZone Security for Virtualized Environments vShield, agentless solution, you see errors similar to:
    File is currently in use. Try again later.
    Cannot save the file to this location.


For virtual machines (running on ESXi 5.1 or 5.5 hosts) which are protected by GravityZone Security for Virtualized Environments Integrated with vShield Endpoint, agentless solution, you need to install VMware Tools

This issue is resolved by ESXi 5.1 Update 2, available at VMware Downloads. For more information, see the ESXi 5.1 Update 2 Release Notes.

Note: After upgrading to ESXi 5.1 Update 2, you must also perform a full upgrade of VMware Tools to resolve the issue.

Due to NTFS architecture change, this only affects Windows 7 and Windows 2008 machine.

Related articles

For more technical details, refer to the following articles:

Rate this article: