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.
Certain App-V 5.0 Service Pack 1 (SP1) packages do not work with the App-V 5.0 Service Pack 2 (SP2) clients.
This is an issue in AppV 5.0 SP2 that may appear to prevent some applications from starting. This includes packages that were sequenced on earlier versions of App-V 5.0. A valid App-V 5.0 package starts correctly and displays a GUI under App-V 5.0 SP1. Under App-V 5.0 SP2, the same package does not display a GUI, or it appears not to start.
A sharing violation occurs during profile synchronization when you use App-V 5.0.
When an App-V user on a Remote Desktop Services (RDS) server logs on after a period of inactivity, a sharing violation may occur when the profile is synchronized to the local cache. Therefore, some required files are not copied over, or they are renamed. In this situation, the profile becomes corrupted.
App-V client handlers leak in Remote Desktop Services (RDS).
When an RDS user logs off, App-V does not release some handles that it held specifically for this session, and therefore the resource cannot be reused. In this situation, the Session ID monotonically increases without reusing IDs from previously finished sessions.
A virtualized Excel Visual Basic for Applications (VBA) application fails if the path for the application contains Chinese or Japanese characters.
Certain applications don't start after Hotfix Package 1 for APP-V 5.0 Service Pack 2 is applied.
Selected registry key values were removed after the deployment of Hotfix 1 for APP-V 5.0 Service Pack 2. This prevents some applications from starting. By reverting Hotfix Package 1 for APP-V 5.0 SP2, you restore these registry values to their default state. However, any existing customizations will be lost and will have to be redone.
Note This issue only affects deployments that were upgraded from APP-V 5.0 Service Pack 1 to APP-V 5.0 Service Pack 2 before Hotfix Package 1 was applied. Remote Desktop Services (RDS) deployments are not affected by this issue.
Hotfix informationA 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.
PrerequisitesTo apply this hotfix, you must have Microsoft Application Virtualization 5.0 Service Pack 2 installed.
Installation informationIf the original client was deployed by using the .msi file, you must apply the .msp file to experience a successful update. To extract the .msp file, run the following command:
Restart informationYou must restart the computer after you apply this hotfix.
For Issue 1, Issue 2, and Issue 3
There are no workarounds available for these issues. To resolve these issues, apply Hotfix Package 2 (from the "Resolution" section), and then restart the APP-V Client service.
For Issue 4
To work around this issue, make sure that the path of the application contains only English characters. To resolve this issue, apply Hotfix Package 2, and then restart the APP-V Client service.
For Issue 5
To work around this issue, import the registry values after you deploy Hotfix Package 1 for APP-V 5.0 Service Pack 2. To resolve this issue, apply Hotfix Package 2, and then restart the APP-V Client service.
Note For deployments that are affected by this issue, these registry keys are always restored to their default values when you apply Hotfix Package 2 for APP-V 5.0 Service Pack 2, regardless of whether the workaround was applied. Therefore, configurations must be redone after the hotfix package is applied. Again, this issue occurs only on non-Remote Desktop Services (RDS) deployments that upgraded from APP-V 5.0 Service Pack 1 to APP-V 5.0 Service Pack 2 and which then applied Hotfix Package 1 for APP-V 5.0 Service Pack 2.