Article ID: 939361 - View products that this article applies to.
When you use Microsoft Forefront Client Security to perform a full scan of a client computer, Forefront Client Security unexpectedly scans files that are stored in network locations. On a network that has low bandwidth or that has high latency, Forefront Client Security may take a long time to scan. In this situation, Forefront Client Security seems to stop responding.
Note A full scan fully evaluates local hard disk drives. A full scan is not intended to scan network hard disk drives or removable hard disk drives.
This problem occurs because Forefront Client Security evaluates shortcuts, and scans the referenced files. Forefront Client Security scans these files even if they are stored in a network location.
This problem is resolved by a hotfix package for Forefront Client Security that is now available. This hotfix updates the behavior of the Forefront Client Security anti-malware client. For more information about this hotfix, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/971026/ )A hotfix is available to resolve some problems with the Forefront Client Security anti-malware client
To work around this problem, you can try to delete any shortcuts file that point to network locations. Many shortcut files that point to network locations are stored on the computer in the following folder:
%USERPROFILE%\RecentTo delete these shortcuts, enable one of the following Group Policy settings:
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Forefront Client Security supports the following types of scans. These scans can be performed on all managed computers or on a specific managed computer.
Forefront Client Security also features a real-time scanner that responds to the "On-Access" event whenever a file is accessed. In this situation, Forefront Client Security intercepts the event and scans the file before it can be accessed. Forefront Client Security scans the file even if it is located on a shared network resource. This expected behavior is unrelated to the problem that is described in this article.