Recipe: App-V 5 Workpace 5.0.3

Wellnomics Workpace 5.03

The application workpace is used to monitor the behaviour and advice the users to reduce RSI (Repetitive strain injury) Through videos and popups the user is informed to exercise or to take a break

This application is supplied with an administrative guide, “Wellnomics WorkPace 5.0.3 IT Administrators Guide.pdf”. You can configure the first run and even force configuration.

Note: You need to force “OptionSuspendInRemoteSession=Locked:N” setting inside C:\Installationdirectory\system\default.ini for VDI and RDS.

App-V 5 Recipe

My colleague Randy von Bannisseht started packaging “Workpace”. This application is usually an easy package. We didn’t expect any problems with this application. The main shortcut works without any issues. The shortcut “WorkPace Training” gave errors. It started with “Directory Player Error” with message “Unable to load movie playlist. …”


The sequencer informed us of about excluded files of the %TEMP% directory. Our first step was removing the exclusions %LOCALAPPDATA%\TEMP and %LOCALAPPDATA%. We solved the “Director Player Error” but we received an “Application Error” with the message “The application cannot start as it cannot create needed files. There may not be enough free disk space”.


After this error message we tried to write into all the parts of the VFS (%ProgramFiles% and %TEMP%). We were able to successful write to the VFS.


The solution was found by trail and error. The application shouldn’t be started during the monitoring fase and the application needs to be installed to the PVAD. The installation didn’t change for creating the App-V package. Removing the %TEMP% directory from the exclusion list is not needed.


Recipe: Corel Paintshop Pro X4

Start with a good installation

At the start of packaging Corel Paintshop Pro X4 I searched the internet for recipes. A couple of silent installations are found on the internet. The application kept asking for registration and updates. I found the solution in a deployment guide of the product.

The documentation of suppliers are usually written for attended installation and not for enterprise environments. I was surprised with a decent deployment guide, see

Prepare the installation

For my customer i have downloaded the latest updates for the application. The service packs of the application are found at . You need to download the service pack 2 and 3 because the service pack 2 is a dependency for 3.

The deployment guide has several options for the installation. Pick the options you need for your environment. The parameters IOFF and NEVERREGISTER are important for enterprise environments.The parameters are executed after the “setup.exe”. I created the following silent installation:

Set THISDIR=%~dp0
“%thisdir%setup.exe” INSTLANG=EN,FR,DE,ES,NL IOFF=1 FORCENOSHOWLIC=1 NEVERREGISTER=1 DESKTOP=NONE SERIALNUMBER=”xxxxxxx-xxxxxxx-xxxxxxx-xxxxxxx” /norestart /qn

“%thisdir%PSPX4_SP2.exe” IOFF=1 /QN
“%thisdir%PSPX4_SP3.exe” IOFF=1 /QN

First use popup

The application has a couple “first use” popup options. You need to capture the popups during the monitoring fase.

clip_image002    clip_image004

The settings are stored at  %localappdata%\Corel Paintshop Pro\. clip_image006

To include the settings within your package, the %localappdata% settings needs to be removed from the exclusionist.


PVAD (Primary Virtual Application Directory)

The application will detect duplicated items if the first use is captured during monitoring.clip_image009

The application detects the items from the VFS and “C:\Programdata\App-v\packageguid\Versionguid\”. You need to install the application into the PVAD directory to solve the double library because the VFS will not be used. The PVAD option is hidden since App-V 5.0 SP3. You can enable the PVAD feature through the command line “sequencer.exe –EnablePVADControl” or the following registry:

Windows Registry Editor Version 5.00


The “Create new package” wizard would add the PVAD option to the sequencer. The application will install in C:\Program Files (X86)\Corel\. Use the same directory for the PVAD option.


Enjoy Corel Paintshop Pro X4! Knipogende emoticon

Microsoft App-V 5 Connectiongroups and errors

Edit: The issue is solved in App-V 5 SP2. The connectiongroups can’t be added with these conflicting settings

Microsoft App-V 5 Connectiongroups and errors

Error: This may be due to a network failure

After importing App-V 5 packages and setting up connectiongroups I was experiencing problems with starting up the applications. I got several errors:the may be due to a network failure

Error: this may be due to a network failure

Error code: 0x8e90060a-003000F

On a Windows 2008 R2 server i got a additional error.

error: MSVCR100.dll

MSVCR100.DLL missing from the system

The following error is in the eventviewer:

failed to start due to Virtual COM subsystem failure

Process 2744 failed to start due to Virtual COM subsystem failure. Package ID {715f39d8-1b48-4b9a-95e6-d33370564b33}. Version ID {9cdf46f3-6716-43d3-b533-5c697878f51f}. Error: 0x8E90060A-0x3000F


With troubleshooting these errors i didn’t find a solution on the internet. There are some similar errors around with different solutions. My problem wasn’t about local rights, because I tried local administrator account and domain admin account. The application would startup correctly after removing the connectiongroup.

The connectiongroup was giving the problem with these applications. A new connectiongroup with different applications worked fine. My suspicion instantly went to “allow all named objects to interact with the local system” and “Allow all COM objects to interact with the local system”. In Microsoft App-V 4.* this settings was “ALLOW LOCAL INTERACTION”.

Testing my suspicion

For my test I created two new applications:

  • A Link to notepad without any registry or files
  • A Link to odbcad32 without any registry or files with BOTH Com and Named objects allowed

Both applications worked fine as a single App-V package. I connected both App-V packages through a connectiongroup.


The connectiongroup imported without any errors or warnings. After the creation of the connectiongroup the applications started with the errors again.


The connectiongroups aren’t able to handle a choice between using or not using “allow all named objects to interact with the local system” and “Allow all COM objects to interact with the local system”. The Microsoft App-V 5 client will generate several errors with startup, because it can’t make a choice between them.

App-V 5 Shared Content Store SCS


In my first blog i want to talk about App-V 5 Share Content Store. At my work we are developing a App-V 5 training for our customers. In my lab i have tried to use Shared Content Store (SCS). With SCS in App-V 5 we are able to keep the footprint of the cache application to a minimal. Because the application inst fully downloaded at run-time.

The use of SCS could be useful for VDI infrastructure, to spare on the storage usages.

I have noticed my test account was able to download his own applications. Because the test user downloaded all his applicationcache, the use of SCS is nullified. Microsoft has fixed this issue during beta. Soo i was surprised of this option.

Other people aren’t having the same problem as my lab. Why is my lab having this option for the users?

I have tried out three options:

Situation A:

Installing App-V 5 Client with the correct paramenters  “appv_client_setup.exe SHAREDCONTENTSTOREMODE=1 /q” and rebooting and setting all the settings through GPO

Situation B:

Installing App-V 5 Client with the installer gui and rebooting and setting all the settings through GPO

Situation C:

Working after situation B, but removing all the cache through powershell “Get-AppvClientPackage -All | Stop-AppvClientPackage | Remove-AppvClientPackage”  and rebooting and setting all the settings through GPO

The results,

With the situation A en C the test user wasnt able to cache the applications

Although Situation B the test user was able to cache the applications.

Conclusion: Install App-V 5 with unattented installation through or rebuild your local cache through Powershell.