Antivirus exclusions for VMware Horizon Mirage

To use VMware Horizon Mirage in your environment it is crucial to set some specific Antivirus exclusions. Not setting the exclusions mentioned below can result in slow performance or even failure of any Mirage operation. Also, on the server-side, not setting the proper exclusions can result in Mirage storage inconsistencies.

As you can see it is absolutely a must to set the following exclusions when using Mirage.

Client-side Antivirus exclusions

Configure your Antivirus solution to exclude the Mirage stating area from being scanned:

C:\Wanova Volume Information

White-list the following process in your Antivirus solution:


Both exclusions need to be applied to every machine with the Horizon Mirage client installed.

Server-side Antivirus exclusions

Configure your Antivirus solution to exclude the Mirage local cache on each Mirage server from being scanned. The location of the local cache may vary in each installation as the path is configurable when installing the Mirage server. If you have not changed the location of the cache the following path should be added to the exclusion list:


Mirage local cache location

If you have forgotten where you placed the Mirage local cache you can check the location by having a look at the Mirage server service configuration file (“Wanova.Server.Service.exe.config”) placed in the Mirage server install directory (“C:Program FilesWanovaMirage Server”).

You need to search for the parameter “serverCacheDir” and then you will find the location of your cache directory. As you can see in the screenshot (? marks the line) below in this example cache is located on C:MirageLocalCache.


Your Mirage storage volume (containing all the layers, CVDs, etc.) should be excluded from being scanned too. When it is placed on a Windows file server or on storage directly attached to the Mirage server this is easy. Just add your storage path, e.g. E:MirageStorage, to the list of exclusion in your Antivirus software.

If you use a third-party unified storage it may not be possible to exclude a whole directory from being scanned instead you can only configure file extensions from being excluded. Luckily in Mirage version 4.3 all relevant files and folders on the Mirage storage will be saved with the extension .vhm (VMware Horizon Mirage) and therefore you can just add this extension to the exclusion list. Please be aware that this setting is only valid for the Mirage storage (not the local cache or the client) and is only applied if you create a new storage with version 4.3 of Mirage. Mirage volumes upgraded from an older version to 4.3 will not get this setting.

White-list the following server process in your Antivirus solution on each Mirage server:


White-list the following server process in your Antivirus solution on the server running the Mirage management server:



On the server-side exclude the following location/processes from being scanned by your Antivirus solution:

  • Mirage volume (e.g. E:MirageStorage) or use the .vhm extension
  • Mirage local cache (default location: C:ProgramDataWanovaMirageLocalCache)
  • Wanova.Server.Service.exe (on each Mirage server)
  • Wanova.Management.Service.exe (on the Management server)

On the client-side add the following path and process from being scanned by your Antivirus product:

  • C:Wanova Volume Information (Mirage staging area)
  • Wanova.Desktop.Service.exe

For more information about the Antivirus configuration have a look at the official knowledgebase article Configuring Antivirus and Computer Protection Software Exclusions for VMware Horizon Mirage 3.x and 4.xwhich also served as source for this article.

One thought on “Antivirus exclusions for VMware Horizon Mirage

  1. inadvertantly, you’ve directed me to why my Mirage setup is in a mess, so thank you for that.

    Not sure what the peops at VmWare were thinking- appending .vhd to the name of every folder and file in Mirage storage. Now heaps of the file paths are too long for windows to deal with, so even after deleting all the CVD’s from Mirage, all the files/folders remain on the server and the number of CVD’s are still registered to the volume because Mirage is unable to delete the files with long file names, so leaves everything behind.

    So this
    \server01MirageMirageVolumesCVD_Volume_3CVD12387Machine1cWINDOWSsystem32configsystemprofileAppDataRoamingMicrosoftWindowsStart MenuProgramsAccessoriesSystem ToolsInternet Explorer (No Add-ons).lnk


    \Server01MirageMirageVolumesCVD_Volume_3CVD.vhm12387.vhmMachine.vhm1.vhmc.vhmWINDOWS.vhmsystem32.vhmconfig.vhmsystemprofile.vhmAppData.vhmRoaming.vhmMicrosoft.vhmWindows.vhmStart Menu.vhmPrograms.vhmAccessories.vhmSystem Tools.vhmInternet Explorer (No Add-ons).lnk.vhm

    which is over the maximum file length allowed by windows and becomes undeletable.
    Even mapping a drive to \Server01MirageMirageVolumesCVD_Volume_3 doesn’t shrink the path enough to make them deletable.


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s