Jul 29, 2013 - 6 Comments - Virtual Vibes -

App-V 5.0 Client Footprint

Hello VirtualVibes readers,

In this post I am going to share with you the App-V 5.0 SP1 client footprint while idle. Please bear in mind this information will naturally vary between environments and serves only as a guideline.

First lets understand what processes actually run on our App-V client machines and what they do:


This process relates to the Microsoft App-V Client service which you will see running on your machine, it is responsible for the management of users and App-V applications forming the backbone of the App-V client itself.


This process is only ever present when the client GUI is launched which allows common tasks to be initiated, all which issue the equivalent PowerShell command, for example a refresh with a publishing server (Sync-AppvPublishingServer) or the repair of a package (Repair-AppvClientPackage).


This comes into play during the publish or unpublish of an App-V package and is responsible for notifying the Windows shell about the integration or disintegration of the package.


As the name suggests, this process relates to the streaming of our App-V applications, it monitors the stream of the blocks of our application and displays the progress bar which you may have seen giving feedback to users before the application launches.

The Footprint

Now you understand what processes form our App-V Client let’s take a look at how the footprint looks while idle.

The following data was collected over a 5 minute sample period.

Process Average RAM (Working Set)
AppVClientUX 42.7 MB
AppVStreamingUX 18.5 MB
AppVClient 12.6 MB
AppVShNotify 2.9 MB


The highest RAM resource consumption was from the AppVClientUX process, this is only loaded when the App-V Client GUI is running. The App-V GUI would not be running by default or typically launched by end users in most environments. In fact this has been excluded from the default installation and made available as an App-V package in SP2 for 5.0.


Remember the numbers above are based on an idle App-V client and I would expect the processes to spike if and when they are called into action in an active environment. Also just to reiterate these are purely for rough guidance only as I would expect the idle footprint of the App-V client to vary from environment to environment so please do your own testing!