Home » appv5

Tag: appv5

AppV 5 Publishing Error 0x74F00F0C


Added a new list of Computers to begin accessing our App-V 5 Infrastructure.

The access to the servers and share are driven by AD Group “App-V Citrix Computers” and “App-V LT or DT Computers” etc


AppV 5 Publishing Error 0x74F00F0C

Event ID: 1008, Error, Logname Microsoft-AppV-Client/Admin

With creating the new group for desktops and laptops to start accessing the AppV infrastructure we started getting

Package {b10fe46f-1d9e-449e-94dc-b6f3e1b0bf47} version {c8df57be-6ed3-49f6-8611-bb7e1c896a3a} failed configuration in folder ” with error 0x74F00F0C-0x80070043


Ensure the above groups (that App-V is publishing too) have read access to the App-V content store. Otherwise they will get the publication from App-V Infrastructure mode – but have none of the rights to access the packages and files it contains.


AppV 5 File Type Associations

I wanted to document the AppV5 File Type Associations and how they work when published down to an end user device or server.

If publishing globally the FTAs will apply to every user of the machine

If publishing to a group of users (and not globally) the FTA’s will only work for those group members.

Its great that the FTA’s can be separated like that.

Sounds simple I know, but its a fundamental publishing property that is often forgotten and overlooked.

App-V 5.0 apps not working when published as seamless applications


Our AppV Applications on Citrix are published globally to the citrix servers computer accounts so the apps are available before the users login. These applications all launch and integrate with AppV either directly calling the AppV exe or by using the /appvve or switch on a hosted Citrix desktop. When the same AppV application is launched seamlessly the app opens but without AppV integration.


*UPDATED* – The /Appvve: switch will work if published via Citrix, but only if the Application/s (in APPV) are published to the end user account (not just the computer accounts)

The /appvve switch doesnt work with Citrix published applications. Use the APP-v console to make the applications available for the end user/s or user groups and then script the launch of the app with powershell.


—— begin script——–

$appvname = get-appvclientpackage “James”
start-appvvirtualprocess -appvclientobject $appvname excel.exe

—— end script——–

I then publish this PS1 script from Citrix in the published app command line:

“C:WindowsSystem32WindowsPowerShellv1.0powershell.exe” -windowstyle hidden “\lonfs001xenapp$AppsSAPLaunch_APPV_JAMES.ps1”


There is a myriad of other ways you can integrate or launch apps inside the APPV bubble see below link for more details. We were unable to use the ‘file type associations’ as we want normal excel to load without the APPV integration and add-ins and for select users have this APPV integration be available.


Reinstall of APPv 5.0 SP1 Server fails after Hotfix Installation / upgrade


We had errors with the App-V publishing service on one of our AppV 5 infrastructure servers. Hotfix KB2940354 had already been installed. But during the remove of the APp-V 5.0 SP1 client, the hotfixes are not removed, nor can they be uninstalled.


The Application Virtualization setup has failed because a more recent version of the App-V is already installed. To Complete the setup, uninstall the existing version of App-V.


Delete this key:

Simply delete any keys related to any App-V hotfixes prior to reinstalling a lower version of the App-V server.

Citrix PVS 7.1 and AppV 5 applications crashing, launching once

This issue absolutely did my head in. I had to publish it for you all to save you the time if you ever come across it as I was close to QUITTING because I couldn’t get this to work.


  1. Windows 2008 R2, Citrix XenApp 6.5 and Microsoft AppV 5 SP2.
  2. Applications published globally to the XA Servers
  3. All Servers streamed from Citrix PVS 7.1
  4. User profiles managed with Citrix User Profile Manager

This article for the Citrix UPM was already followed and the AppV Exclusions were definitely set


Some App-V packaged applications would launch once, then never again when the Package Installation Root was pointing to the Read Only PVS Image (%programdata%AppV) and ONLY when the server was in Read only mode. If I was editing the image in PVS maintenance mode to update the vDisk – the issue never presented itself.

Ideally I wanted the App-V cache to point to the ‘out of the box’ %programdata%AppV – and in conjunction with PVS you can guarantee its fresh everytime

A temporary work around was to move the Package Installation Root to the D: (Read Write Disk) < but we soon started getting errors with this as no amount of scripting and startup scripts would cleanly remove this directory 100% all the time. I.E:

Get-AppvClientPackage -All | Remove-AppVClientPackage

remove-item -Recurse -Force d:app-v

get-appvpublishingserver | sync-appvpublishingserver -Global

This script would only remove the currently published applications, too bad for any legacy packages that were no longer published to the servers,


and for whatever reason the SYSTEM account was unable to delete the d:app-v folder (access denied even though it was owner and had full rights) sporadically the folder wouldn’t update at all and no applications would be refreshed until a user logged into the server. (Poinless on a citrix server where the applications have to exist if delivered as published apps’  Citrix could not find / see the executable and the published app would not run.

Eventually App-V Clients services started failing unable to start.


The Microsoft App-V Client service terminated with service-specific error The system cannot find the path specified.. EventID 7024 (Update: After further troubleshooting it turn out this was because some of the legacy packages were referenced in the Windows registry)

There had to be a better solution.


Change the PVS 7.1 Disk Cache mode to  “RAM with Overflow to Disk”, Return the Package Install Root to %programdata%AppV and generalise the AppV 5 Client before shutting down the image after each PVS update.




AppV 5 Generalise:

c:admintoolspstoolspsexec.exe -s powershell.exe “Get-AppvClientPackage -All | Remove-AppVClientPackage”
regedit.exe /s “C:adminToolsAppV_Generalise.reg”

AppvGeneralise.reg Contents:

Windows Registry Editor Version 5.00





Articles / References:

http://discussions.citrix.com/topic/348198-app-v-5-client-citrix-provisioning/ – Explains the situation clearly, and finally provided me the solution to fix it once and for all. Much thanks to Carl Fallis!

Launch Internet Explorer in APP-V 5 environment & passthrough the URL

We have a package that needs to be installed and run inside the APP-V 5.0 ‘virtual environment’ or ‘bubble’.

The following command ran Internet Explorer inside the APP-V package / environment then passed Internet explorer the URL

Its a powershell script we have housed on a network share for all such XenApp scripts and specific application launching etc

Powershell Script

$AppVName = Get-AppvClientPackage “Published AppV Name”
Start-AppvVirtualProcess -AppvClientObject $AppVName iexplore.exe “http://website/page”


Citrix Published App Path:

“C:WindowsSystem32WindowsPowerShellv1.0powershell.exe” -windowstyle hidden “\serversharescript.ps1”