Hotfix Package 1 for Microsoft Application Virtualization 4.6 Service Pack 3

Applies to: Microsoft Application Virtualization 4.6 for Windows Desktops Service Pack 3Microsoft Application Virtualization 4.6 Sequencer Service Pack 3


This article describes a hotfix package that contains the latest hotfixes for Microsoft Application Virtualization (App-V) 4.6 Service Pack 3.

Note We recommend that you test hotfixes before you deploy them in a production environment. Because the builds are cumulative, each new hotfix release contains all the hotfixes and all the security fixes that were included with the previous update package. We recommend that you consider applying the most recent fix release that contains the most necessary hotfixes.

This hotfix package fixes the following issues.

Issue 1

When Internet Explorer tries to start in the virtual environment, it either cannot start or cannot access the virtual environment after it starts.

Internet Explorer 10 and Internet Explorer 11 include enhanced protected mode (EPM). By default, Internet Explorer 11 has this mode enabled. In this mode, Internet Explorer tabs are started as a very limited AppContainer process. In this case, the inserted App-V 4.6 .dll file cannot initialize correctly in the AppContainer process, and Internet Explorer cannot start.

Issue 2

When both App-V 4.6 Service Pack 3 (SP3) and App-V 5.0 Service Pack 2 (SP2) are installed on the same system, and when Internet Explorer is started within the App-V 4.6 virtual environment, Internet Explorer cannot access App-V 4.6 package content.

If App-V 5.0 SP2 is present on the system, App-V 4.6 will inject only into processes with executable from the virtual drive (such as drive Q), and App-V 5.0 will account for all other processes. Because Internet Explorer is always started from the native system, App-V 4.6 does not consider Internet Explorer as a virtual process, even though Internet Explorer is started within the virtual environment. Therefore, Internet Explorer cannot access App-V 4.6 package content. The fix in this package will enable App-V 4.6 SP3 to inject into processes in a co-existence scenario if the processes do not originate from the Q drive and are on the App-V 5.0 dynamic virtualization allow list. 

Issue 3

The Open XML SDK can cause Stop errors in some scenarios.

Because of certain issues in the SDK, the App-V driver fails and causes App-V to crash with a Stop error.

Issue 4

This update includes support for the latest Open XML SDK and App-V 4.6 cumulative updates.

This hotfix also includes the update for the Open XML SDK for App-V 4.6 SP3 and also a rollup of fixes that were released in Hotfix Package 4 for App-V 4.6 SP2 .


Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, go to the following Microsoft website: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.


To apply this hotfix, you must have App-V 4.6 SP3 installed.

Restart information

You must restart the computer after you apply this hotfix.

Build number

The build number for this hotfix is


Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.


Learn about the terminology that Microsoft uses to describe software updates.