This article describes a hotfix package for September 2009 that contains the latest hotfixes for Microsoft Application Virtualization 4.5 Cumulative Update 1.
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 addresses the following issues:
In some scenarios, an application may not start, and you receive a DLL error or a "File Not Found" error. This issue is most likely to occur on a multiprocessor computer.
It takes significantly longer to stream a package over the RTSPS protocol than to stream a package over the RTSP protocol.
When you use TrueCrypt for drive encryption, any tries to mount an encrypted volume may generate a 0xA stop error.
The Microsoft Application Virtualization 4.5 client leaks paged pool memory. This problem occurs when you apply a disk quota to the profile directories of a user and when the disk quota is near the limit.
A virtual application that calls the RegQueryMultipleValues function may experience unexpected errors or cannot start. For example, you receive error messages when you start or shutdown the Trapeze application. Then, the application does not work correctly.
When an Application Virtualization 4.5 client tries to perform a publishing update procedure over HTTP or over HTTPS, the procedure is not completed successfully. Specifically, the procedure is not completed successfully if a package contains pathnames that have Japanese characters. This problem occurs when the Application Virtualization 4.5 client has Windows Internet Explorer 6 installed and runs a Japanese version of Windows XP.
When it is run as a virtual application, Microsoft Office Access 97 generates an error message 1008 when Office Access 97 is moving temporary files.
When an Application Virtualization 4.5 client tries to perform a publishing update procedure over HTTP or over HTTPS on an IPv6 network, the procedure is not completed successfully.
When you expand a %APPDATA% environment variable to a universal naming conventions (UNC) path, application-specific failures occur when you start virtual applications.
The Microsoft Application Virtualization 4.5 client cannot log on to a publishing server. This problem occurs in environments that have a trust relationship and a mapped user account between a Windows domain and an MIT Kerberos realm. Additionally, you receive an error message 8009030C. Note You can resolve this problem by creating a UseMITKerberos registry value.
Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
On the Edit menu, point to New, and then click DWORD Value.
Type UseMITKerberos, and then press ENTER.
On the Edit menu, click Modify.
Type 1, and then click OK.
Exit Registry Editor.
Consider the following scenario. You add or remove a user from an Active Directory security group that is used to control access to an application. Then you enable this hotfix. In this scenario, Application Virtualization 4.5 does not correctly publish the application after a publishing update procedure. The user must log off and then log back on to see the changes.
This hotfix does not support Application Virtualization 4.5 in environments that have a trust relationship and a mapped user account between a Windows domain and an MIT Kerberos realm. In some environments, this configuration may work if you install this hotfix. However, this configuration will not be supported in these environments until a future version of Application Virtualization 4.5 is released.
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 this specific problem.
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, submit a request to 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.
To apply this hotfix, you must have Application Virtualization 4.5 Cumulative Update 1 installed.
You must restart the computer after you apply this hotfix.
Hotfix replacement information
This hotfix replaces Hotfix Package 5 for Application Virtualization 4.5 Cumulative Update 1.
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
Hotfix Package 5 for Microsoft Application Virtualization 4.5 Cumulative Update 1: August 2009
The English (United States) version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and times for these files are listed in Coordinated Universal Time (UTC). The dates and times for these files on your local computer are displayed in your local time and with your current daylight saving time (DST) bias. Additionally, the dates and times may change when you perform certain operations on the files.