Sunday, May 04, 2014

AppV 5.0 SP2 HotFix 4 (HF4)

I upgraded our test environment for AppV 5.0 SP2 to HF4  and came across an issue where our packages won't load.  The error specifically was: "Package {248b49bd-39f9-471c-b655-7483c11a6f69} version {868b72ed-ac56-4b8e-ae42-60a049401330} failed configuration in folder 'D:\AppVData\PackageInstallationRoot\' with error 0x4C40330C-0x12."

We got this error for all of our packages.  I procmon'ed it and it appeared to be OK, saying that it was creating folders and loading the .appv package, but when I went into the D:\AppVData\PackageInstallationRoot folder, nothing was in there.

It turns out that with Hotfix 4 Microsoft has changed the PackageInstallationRoot permissions to require Authenticated Users (Read/Write) to the folder, without this ACL we get the above error.  Microsoft appears to have made this change to allow Globally published application to be able to be launched on network shares without requiring the local machine account added to the share.  Unfortunately, without the ACL on the local folder we get the error above.  To create the folder with the correct ACL's, just delete the existing folder and restart the AppVClient service.  The service will auto-create the folder with the correct ACL's.

If the service does not recreate the folder, you may need to run the AppV publishing scheduled task to get it created.


JustVisiting said...

If it helps anyone else, I had changed my ownership of the folder from system (while trying to clean up appv folder). Changed back... and good :)

failed configuration in folder 'C:\ProgramData\App-V\' with error 0x4C40330C-0x12

Anonymous said...

This worked for me. many thanks

Anonymous said...

This solution worked for me in Appv 5.1 as well. I had changed the GlobalRootIntegration folder to D:\. Also the appv client Package installation root was changed to D:\. Awesome. Thanks very much for the solution.

Anonymous said...

Thank you so much as this post as the procedure described above resolved the same AppV configuration error (as described above). Unfortunately, I did not find the post until after numerous google searches and many many hours of researching/troubleshooting the issue.