Debugging App-V 5.0 Error Code – 0x45500D27-0x80190191

Hi all,

We’ve seen this error a few times in App-V 5.0 deployments and thought it was time to show you why this error can occur.


This error code occurs when completing a global refresh on the client, but interestingly a user sync works correctly.



Looking into why it occurs we need to understand what the error code actually means. The Gladiator@MSFT has discussed this on his blog -

If we convert the error to the short code we are presented with:


So that means its a publishing error with the hex code 7 and the 2 states that its a windows error. The error description from Powershell provides this also.

Hex Code


Where you might further Info



Client-Publishing Log, Client-PackageConfig Log, or
  FileSystemmetadataLibrary Log

So if we decode the 0x80190191 HRESULT, the return description is:

Unauthorized (401).

To confirm this on the App-V Publishing Server we enabled failed request logging, an unauthorized 401.2 error is returned which states an Access denied to the server.

“Typically, HTTP 401.1 and 401.2 errors are encountered when the authentication process fails in some way — either because the mechanism that IIS used to obtain the credentials has failed or because the credentials themselves are invalid. This is an important distinction that is a critical to the problem isolation process. These errors tell you that, before performing any other function, IIS has failed to authenticate the user.”

Note: The following article is a great reference to using failed request logging -



The resolution for this case was due to user permissions. If you check the “Users” group on the publishing server:


The member of “Users” should be similar to the below:


In this case the “NT AUTHORITY\Authenticated Users” had been removed which caused the 0x45500D27-0x80190191 for a global refresh.



Ensure that the “NT AUTHORITY\Authenticated Users” group is a member of the local users group otherwise the refresh will fail.


This may not be the cause in your environment but worth checking if you start receiving this error on a global refresh.

Hope this helps.

David Falkus | Premier Field Engineer | Application Virtualization

Comments (0)

Skip to main content