Hotfix Package 4 for Microsoft Application Virtualization 4.5 Cumulative Update 1: July 2009

This article describes a hotfix package for July 2009 that contains the latest hotfixes for Microsoft Application Virtualization 4.5 Cumulative Update 1 (App-V 4.5 CU1).

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:

• When you apply a disk quota to the profile directories of an user and when the disk quota is near the limit, the App-V client leaks paged pool memory.
• When run as a virtual application, a process that calls RegQueryMultipleValues experience unexpected errors or cannot start. For example, you receive error messages when you start or shutdown the Trapeze application and the application does not work correctly.
• When a App-V client tries to perform a publishing refresh procedure over HTTP or HTTPS, the procedureis not completed successfully. Specifically, the procedure is not completed successfully if a package contains pathnames that have Japanese characters. This problem occurs when the App-V client is running a Japanese version of Windows XP and has Internet Explorer 6 installed.
• When run as a virtual application, Microsoft Access 97 generates an error message 1008 when Access 97 is moving temporary files.
• When a Microsoft Application Virtualization 4.5 client tries to perform a publishing refresh 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.
• In environments that have a trust relationship and mapped user accounts between a Windows Domain and an MIT Kerberos realm, the Microsoft Application Virtualization 4.5 client cannot log on to a publishing server. 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:

1. Start Registry Editor.
2. Locate and then click the following key in the registry:
   HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SoftGrid\4.5\Client\Network
3. On the Edit menu, point to New, and then click DWORD Value.
4. Type UseMITKerberos, and then press ENTER.
5. On the Edit menu, click Modify.
6. Type 1, and then click OK.
7. Exit Registry Editor.

Important

• With this fix enabled, Microsoft Application Virtualization 4.5 does not correctly publish an application after a publishing refresh when you add or remove a user from an Active Directory security group that is used to control access to an application. The user has to log off and then log back on to see the changes.
• Running Microsoft Application Virtualization 4.5 in environments that have a trust relationship and a mapped user account between Windows Domain and MIT Kerberos realm is not supported by this hotfix. In some environments, installing this hotfix may enable this configuration to work. However, this configuration in these environments will not be supported until a future release of Microsoft Application Virtualization 4.5.

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

You must have Microsoft Application Virtualization 4.5 Cumulative Update 1 installed to apply this hotfix.

Restart Requirement

You have to restart your computer after you apply this hotfix.

Hotfix Replacement Information

This hotfix replaces the hotfix in the following KB article:

File Information

The English version of this hotfix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.

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

For more information, click the following article number to view the article in the Microsoft Knowledge Base: