Hotfix Package 1 for Microsoft Application Virtualization 5.0 Service Pack 3 is now available


Hotfix160

The article below describes a hotfix package that contains hotfixes for Adobe Acrobat issues in Microsoft Application Virtualization 5.0 (App-V 5.0) Service Pack 3 (SP3). The hotfix package resolves the following issues:

Issue 1: Virtualized Adobe Acrobat running through an App-V Client on Windows 7 crashes or stops responding because of DLL issues

Virtualized Adobe Acrobat running on Windows 7 may crash or stop responding because of an interoperability issue between App-V and Adobe. This issue causes App-V to sometimes load multiple copies of the same DLL from different locations. This, in turn, causes the virtual Adobe Acrobat application to crash or stop responding when certain operations are performed. This issue is fixed in this hotfix package.

Issue 2: Stop error is triggered by DLL issues when an App-V Client tries to load Adobe Acrobat packages

Some products, such as Adobe Acrobat, use DLLs that have file name extensions other than .dll. When an App-V Client loads virtualized packages of these applications, it does not recognize these files as DLLs and does not exclude them from the copy-on-write subsystem. A Stop error may occur when a package is run that uses these DLLs.

For additional details as well as a link to an App-V hotfix that resolves these issues please see the following:

KB3039022 - Hotfix Package 1 for Microsoft Application Virtualization 5.0 Service Pack 3 (http://support.microsoft.com/en-us/kb/3039022)

J.C. Hornbeck | Solution Asset PM | Microsoft GBS Management and Security Division

Get the latest System Center news on Facebook and Twitter:

clip_image001 clip_image002

Main System Center blog: http://blogs.technet.com/b/systemcenter/

Configuration Manager Support Team blog: http://blogs.technet.com/configurationmgr/
Data Protection Manager Team blog: http://blogs.technet.com/dpm/
Orchestrator Team blog: http://blogs.technet.com/b/orchestrator/
Operations Manager Team blog: http://blogs.technet.com/momteam/
Service Manager Team blog: http://blogs.technet.com/b/servicemanager
Virtual Machine Manager Team blog: http://blogs.technet.com/scvmm

Microsoft Intune: http://blogs.technet.com/b/microsoftintune/
WSUS Support Team blog: http://blogs.technet.com/sus/
RMS blog: http://blogs.technet.com/b/rms/
App-V Team blog: http://blogs.technet.com/appv/
MED-V Team blog: http://blogs.technet.com/medv/
Server App-V Team blog: http://blogs.technet.com/b/serverappv

Forefront Endpoint Protection blog: http://blogs.technet.com/b/clientsecurity/
Forefront Identity Manager blog: http://blogs.msdn.com/b/ms-identity-support/
Forefront TMG blog: http://blogs.technet.com/b/isablog/
Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/
Application Proxy blog: http://blogs.technet.com/b/applicationproxyblog/
The Surface Team blog: http://blogs.technet.com/b/surface/


Comments (5)

  1. Bryan says:

    Is supported by SCCM2012 R2 ?

  2. shannon says:

    Hiya! Could you please consider releasing updates like these as cumulative updates? I (as an admin) would much rather just deploy a brand new MSI of AppV5.0SP3HF01 rather than a more complex scripting solution of trying to deploy AppV5SP3 MSI followed
    by a MSP, which is something Group Policy software deployment can't natively do.

  3. Howard says:

    Tried the hotfix with adobe acrobat XI. Still have the same issues. The Hot Fix didn't work.

  4. mike says:

    Also, tried the hotfix with adobe acroba XI and still have the same issues.

  5. Howard says:

    In our case, we where able to isolate to only when .Net Framework 4.5.2 is installed. Even after rolling back to .Net Framework 4.5.1, Acrobat would still crash. It would only work if 4.5.2 was never installed. Go here to see how we fixed it.
    http://roadmaptech.com/?p=709 Microsoft still has a bug...

Skip to main content