This article describes a hotfix package for January 2009 that contains the latest hotfixes for Microsoft Application Virtualization (App-V) 4.5.
Note We recommend that you test hotfixes before you deploy the hotfixes in a production environment. Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with earlier update packages. We recommend that you consider applying the most recent hotfix release that contains the hotfix that you need.
The following issues are fixed in the hotfix package:
- When you add or remove a user from an Active Directory security group that is used to control access to an application, App-V does not correctly publish the application after a domain controller refresh. For example, the user does not see the new application if the following conditions are true:
- The user is added to a security group.
- The user is removed from the security group, but the user does not log off and then log back on. In this case, the application is not removed.
- The Microsoft Application Virtualization for Terminal Services client intermittently generates a 0xA stop error.
- Empty virtual directories may become inaccessible. Therefore, later file operations on that virtual directory fail. When this problem occurs, you receive the following error message:
- When you run ArcGIS as a virtual application, ArcGIS stops responding on some systems when you start ArcGIS.
- When you use Symantec Endpoint Protection with the Application and Device Control feature enabled, virtual applications cannot start. Additionally, you receive the following error message:
The application failed to initialize properly (0xc000007b)
- When you run SmarTerm Essential as a virtual application, SmarTerm Essential cannot validate its license. Therefore, SmarTerm Essential does not start.
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 installed to apply this hotfix.
Restart requirement
You have to restart your computer after you apply this hotfix.
Hotfix replacement information
This hotfix replaces hotfix 959834.
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
959834
(http://support.microsoft.com/kb/959834/
)
Hotfix Package 2 for Microsoft Application Virtualization 4.5: December 2008
File information
The English version of this hotfix has the file attributes (or later file attributes) 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 item in Control Panel.
Collapse this tableExpand this table
| File name | File version | File size | Date | Time | Platform |
|---|
| Mavcperf.dll | Not applicable | 894 | 06-Jan-2009 | 16:43 | Not applicable |
| Mavcperfres.dll | Not applicable | 817 | 06-Jan-2009 | 16:42 | Not applicable |
| Mavcperfres.dll | Not applicable | 811 | 06-Jan-2009 | 16:42 | Not applicable |
| Mavcperfres.dll | Not applicable | 821 | 06-Jan-2009 | 16:43 | Not applicable |
| Mavcperfres.dll | Not applicable | 821 | 06-Jan-2009 | 16:42 | Not applicable |
| Mavcperfres.dll | Not applicable | 815 | 06-Jan-2009 | 16:42 | Not applicable |
| Mavcperfres.dll | Not applicable | 811 | 06-Jan-2009 | 16:42 | Not applicable |
| Mavcperfres.dll | Not applicable | 815 | 06-Jan-2009 | 16:42 | Not applicable |
| Mavcperfres.dll | Not applicable | 819 | 06-Jan-2009 | 16:42 | Not applicable |
| Mavcperfres.dll | Not applicable | 815 | 06-Jan-2009 | 16:42 | Not applicable |
| Mavcperfres.dll | Not applicable | 817 | 06-Jan-2009 | 16:42 | Not applicable |
| Mavcperfres.dll | Not applicable | 821 | 06-Jan-2009 | 16:42 | Not applicable |
| Mavcperfres.dll | Not applicable | 821 | 06-Jan-2009 | 16:42 | Not applicable |
| Nlsdl.dll | Not applicable | 603 | 06-Jan-2009 | 16:43 | Not applicable |
| Sentinel.dll | Not applicable | 799 | 06-Jan-2009 | 16:43 | Not applicable |
| Sftclientres.dll | Not applicable | 886 | 06-Jan-2009 | 16:43 | Not applicable |
| Sftclientres.dll | Not applicable | 898 | 06-Jan-2009 | 16:42 | Not applicable |
| Sftclientres.dll | Not applicable | 892 | 06-Jan-2009 | 16:43 | Not applicable |
| Sftclientres.dll | Not applicable | 892 | 06-Jan-2009 | 16:43 | Not applicable |
| Sftclientres.dll | Not applicable | 896 | 06-Jan-2009 | 16:42 | Not applicable |
| Sftclientres.dll | Not applicable | 898 | 06-Jan-2009 | 16:42 | Not applicable |
| Sftclientres.dll | Not applicable | 888 | 06-Jan-2009 | 16:42 | Not applicable |
| Sftclientres.dll | Not applicable | 886 | 06-Jan-2009 | 16:43 | Not applicable |
| Sftclientres.dll | Not applicable | 894 | 06-Jan-2009 | 16:43 | Not applicable |
| Sftclientres.dll | Not applicable | 890 | 06-Jan-2009 | 16:43 | Not applicable |
| Sftclientres.dll | Not applicable | 900 | 06-Jan-2009 | 16:43 | Not applicable |
| Sftclientres.dll | Not applicable | 886 | 06-Jan-2009 | 16:43 | Not applicable |
| Sftclientres.dll | Not applicable | 888 | 06-Jan-2009 | 16:42 | Not applicable |
| Sftcmc.dll | Not applicable | 63,533 | 06-Jan-2009 | 16:42 | Not applicable |
| Sftcmcres.dll | Not applicable | 1,168 | 06-Jan-2009 | 16:43 | Not applicable |
| Sftcmcres.dll | Not applicable | 1,174 | 06-Jan-2009 | 16:43 | Not applicable |
| Sftcmcres.dll | Not applicable | 1,154 | 06-Jan-2009 | 16:42 | Not applicable |
| Sftcmcres.dll | Not applicable | 1,150 | 06-Jan-2009 | 16:43 | Not applicable |
| Sftcmcres.dll | Not applicable | 1,182 | 06-Jan-2009 | 16:43 | Not applicable |
| Sftcmcres.dll | Not applicable | 1,170 | 06-Jan-2009 | 16:43 | Not applicable |
| Sftcmcres.dll | Not applicable | 1,168 | 06-Jan-2009 | 16:43 | Not applicable |
| Sftcmcres.dll | Not applicable | 1,164 | 06-Jan-2009 | 16:43 | Not applicable |
| Sftcmcres.dll | Not applicable | 1,178 | 06-Jan-2009 | 16:43 | Not applicable |
| Sftcmcres.dll | Not applicable | 1,176 | 06-Jan-2009 | 16:43 | Not applicable |
| Sftcmcres.dll | Not applicable | 1,172 | 06-Jan-2009 | 16:43 | Not applicable |
| Sftcmcres.dll | Not applicable | 1,178 | 06-Jan-2009 | 16:43 | Not applicable |
| Sftcmcres.dll | Not applicable | 1,170 | 06-Jan-2009 | 16:43 | Not applicable |
| Sftcomp.dll | Not applicable | 1,038 | 06-Jan-2009 | 16:43 | Not applicable |
| Sftcore.dll | Not applicable | 137,356 | 06-Jan-2009 | 16:43 | Not applicable |
| Sftdcc.exe | Not applicable | 5,904 | 06-Jan-2009 | 16:42 | Not applicable |
| Sftdde.exe | Not applicable | 11,845 | 06-Jan-2009 | 16:43 | Not applicable |
| Sftevent.dll | Not applicable | 998 | 06-Jan-2009 | 16:43 | Not applicable |
| Sftfs2k3.sys | Not applicable | 25,535 | 06-Jan-2009 | 16:43 | Not applicable |
| Sftfsi.dll | Not applicable | 139,945 | 06-Jan-2009 | 16:43 | Not applicable |
| Sftfslh.sys | Not applicable | 26,819 | 06-Jan-2009 | 16:44 | Not applicable |
| Sftfsxp.sys | Not applicable | 25,513 | 06-Jan-2009 | 16:44 | Not applicable |
| Sftintf.dll | Not applicable | 22,369 | 06-Jan-2009 | 16:44 | Not applicable |
| Sftldr.dll | Not applicable | 49,650 | 06-Jan-2009 | 16:44 | Not applicable |
| Sftlist.exe | Not applicable | 32,800 | 06-Jan-2009 | 16:44 | Not applicable |
| Sftlp.exe | Not applicable | 10,283 | 06-Jan-2009 | 16:44 | Not applicable |
| Sftmime.com | Not applicable | 365 | 06-Jan-2009 | 16:42 | Not applicable |
| Sftmime.exe | Not applicable | 19,624 | 06-Jan-2009 | 16:42 | Not applicable |
| Sftplay2k3.sys | Not applicable | 15,800 | 06-Jan-2009 | 16:44 | Not applicable |
| Sftplaylh.sys | Not applicable | 15,276 | 06-Jan-2009 | 16:44 | Not applicable |
| Sftplayxp.sys | Not applicable | 15,798 | 06-Jan-2009 | 16:44 | Not applicable |
| Sftpsr.dll | Not applicable | 1,228 | 06-Jan-2009 | 16:44 | Not applicable |
| Sftsharedres.dll | Not applicable | 824 | 06-Jan-2009 | 16:43 | Not applicable |
| Sftsharedres.dll | Not applicable | 818 | 06-Jan-2009 | 16:43 | Not applicable |
| Sftsharedres.dll | Not applicable | 824 | 06-Jan-2009 | 16:44 | Not applicable |
| Sftsharedres.dll | Not applicable | 820 | 06-Jan-2009 | 16:43 | Not applicable |
| Sftsharedres.dll | Not applicable | 812 | 06-Jan-2009 | 16:43 | Not applicable |
| Sftsharedres.dll | Not applicable | 812 | 06-Jan-2009 | 16:43 | Not applicable |
| Sftsharedres.dll | Not applicable | 826 | 06-Jan-2009 | 16:43 | Not applicable |
| Sftsharedres.dll | Not applicable | 814 | 06-Jan-2009 | 16:43 | Not applicable |
| Sftsharedres.dll | Not applicable | 822 | 06-Jan-2009 | 16:43 | Not applicable |
| Sftsharedres.dll | Not applicable | 816 | 06-Jan-2009 | 16:43 | Not applicable |
| Sftsharedres.dll | Not applicable | 818 | 06-Jan-2009 | 16:43 | Not applicable |
| Sftsharedres.dll | Not applicable | 820 | 06-Jan-2009 | 16:43 | Not applicable |
| Sftsync.dll | Not applicable | 3,570 | 06-Jan-2009 | 16:44 | Not applicable |
| Sfttray.exe | Not applicable | 28,694 | 06-Jan-2009 | 16:42 | Not applicable |
| Sftuser.dll | Not applicable | 2,872 | 06-Jan-2009 | 16:44 | Not applicable |
| Sftvol2k3.sys | Not applicable | 849 | 06-Jan-2009 | 16:44 | Not applicable |
| Sftvollh.sys | Not applicable | 849 | 06-Jan-2009 | 16:44 | Not applicable |
| Sftvolxp.sys | Not applicable | 849 | 06-Jan-2009 | 16:44 | Not applicable |
| Sftvsa.exe | Not applicable | 11,495 | 06-Jan-2009 | 16:44 | Not applicable |
| Sgcliprv.dll | Not applicable | 1,494 | 06-Jan-2009 | 16:42 | Not applicable |
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684
(http://support.microsoft.com/kb/824684/LN/
)
Description of the standard terminology that is used to describe Microsoft software updates