Hotfix Package 2 for Microsoft Application Virtualization 4.6 All Languages: February 2011

This article describes a hotfix package that contains the latest hotfixes for Microsoft Application Virtualization 4.6 All Languages and that is dated February 2011.

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 fixes that were included with the previous update package. We recommend that you apply the most recent hotfix release that contains the hotfixes that you want.

This hotfix package addresses the following issues:

• The Application Virtualization Client may cause your computer to stop responding when you shut down a virtual package under certain circumstances. 
• The Application Virtualization Client does not stop an application when the ABORTRESULT attribute matches the exit code of the script.
• You have a computer that is running Windows Vista or a newer version of Windows. When you run the vssadmin list shadowstorage command on the Q drive of Microsoft Application Virtualization 4.6, you receive an error message that resembles the following:
  Error: The shadow copy provider had an unexpected error while trying to process the specified command.
• The Application Virtualization Client may encounter a "0x00000001" Stop error.
• When you try to start an application that contains more than 32 image section headers on a client computer, you receive a "0C-00000042" error.
• When you receive the "Starting launch" message for an application on a terminal server, the application may stop responding, and you must restart the terminal server to resolve this issue.
• Certain virtualized applications that call the GetCurrentProcess method do not operate correctly, and they return the following error message:
  ERROR Invalid handle.

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, visit the following Microsoft Web site: 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.

Prerequisites

To apply this hotfix, you must have Microsoft Application Virtualization 4.6 All Languages (build 4.6.0.20200) installed.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix replaces the following hotfix:

File information

The global version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.

For all supported x86-based versions of Windows Desktop Clients

For all supported x64-based versions of Windows Desktop Clients

For all supported x86-based versions of Remote Desktop Services Clients

For all supported x64-based versions of Remote Desktop Services Clients

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