App-V is not publishing

27 Jan 2015 by Ryan Ververs-Bijkerk



App-V is not publishing

During Project VRC phase 7 we noticed some issues with publishing by App-V 5.0 Hotfix 4. Somehow App-V was not publishing during logon which is very strange. After some troubleshooting we found the root cause and shared this with the product team. With the release of Hotfix 5 I checked if this was solved, but to my surprise it was not. Within this blog post I will explain what is causing this issue and how to solve it.

What is going on?

When App-V is not publishing, the first place to take a look is the task scheduler. Within the task scheduler there is a task named “1_user_logon” which is located at “\Microsoft\AppV\Publishing”. This task will make sure the sync is taking place when a user loggs on to the system. The event is both for user and global publishing. When there is a problem with publishing, the task will report this error “(0xFFFFFFE)” as the last run result. More detailed information can be found in the history tab. Event ID 201 will report the following text:

Task Scheduler successfully completed task “\Microsoft\AppV\Publishing\1_user_logon” , instance “{3567a710-c410-44a1-a435-6001a7b0ebe5}” , action “C:\Program Files\Microsoft Application Virtualization\Client\SyncAppvPublishingServer.exe” with return code 4294967294.

When the task is executed as expected the return code should be 0.

What is the SyncAppVPublishingServer.exe?

With the release of Hotfix 4 the SyncAppvPublishingServer.exe is introduced which replaces the SyncAppvPublishingServer.vbs. Comparing the code of vbs and the exe (decompiled with JetBrains dotPeek) both seem to be a wrapper that will execute the Sync-AppvPublishingServer command within powershell. The big difference is the way how powershell commands are executed. Within .NET there is the ability to directly use the powershell runtime which is a benefit on performance. This can be done with the RunspaceInvoke Class, more information can be found here.

What is causing this issue?

As described in this forum post the error is caused by powershell. Within the SyncAppvPublishingServer.exe the following command is run: ”Set-ExecutionPolicy RemoteSigned -Scope Process”. When executing the SyncAppvPublishingServer.exe there is no feedback within the console or any information in the event log. Therefore I rebuild the solution and returned the exception to understand what really is going on. Running my own version of SyncAppvPublishingServer.exe, I got the following powershell error:

Windows PowerShell updated your execution policy successfully, but the setting is overridden by a policy defined at a more specific scope. Due to the override, your shell will retain its current effective execution policy of Unrestricted. Type "Get-ExecutionPolicy -List" to view your execution policy settings. For more information please see "Get-Help Set-ExecutionPolicy".

And the following C# exception is thrown:

System.Security.SecurityException: Security error. at System.Management.Automation.MshCommandRuntime.ThrowTerminatingError(ErrorRecord errorRecord) --- End of inner exception stack trace --- at System.Management.Automation.Runspaces.PipelineBase.Invoke(IEnumerable input) at System.Management.Automation.RunspaceInvoke.Invoke(String script, IEnumerable input) at System.Management.Automation.RunspaceInvoke.Invoke(String script) at Test.Program.Main(String[] args)


As the powershell error described the execution policy is overwritten. The security exception indicates the process needs to run with higher privileges. I noticed this error is related to the group policy that is configured. The policy “Administrative Templates/Windows Components/Windows PowerShell/Turn on Script Execution” can be configured both on user and computer level. When this policy is configured to “Allow all scripts” on the user level the exception within SyncAppvPublishingServer.exe is thrown. There a two ways to solve the error.

  • Change the group policy setting to "Allow local scripts and remote signed scripts"
  • Configure the policy on a computer level
  • Update to SP3

I hope this provides a better understanding why this error occurs and how to solve it. If you have any comments or questions please leave them below.


According to the comment by Roy Essers the above issue has been solved with App-V SP3 release. Based on this feedback I took a second look and can confirm the publishing issue is fixed. A try catch has been added when the execution policy for the process is set which solves the issue that App-V is not publishing.

Ryan Ververs-Bijkerk
Written by Ryan Ververs-Bijkerk

Ryan is currently a Technical Evangelist at RawWorks focused on the End-User Computing area. Ryan is primarily focusing on the user experience in centralized desktop environments.


    Follow me