Microsoft KB Archive/938054

= A hotfix is available to resolve some problems with the Forefront Client Security client =

Article ID: 938054

Article Last Modified on 10/18/2007

-

APPLIES TO


 * Microsoft Forefront Client Security

-



Important This article contains information about how to modify the registry. Make sure that you back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows registry



SYMPTOMS
You experience the following symptoms when you are using Microsoft Forefront Client Security.

Symptom 1
On a computer that is running Microsoft Windows 2000 Service Pack 4, the Anti-malware user interface cannot open when you log on to the computer by using a non-administrator account.

Symptom 2
In the notification area, the Forefront Client Security icon becomes orange to indicate that an issue has occurred. When you open the Forefront Client Security client to view the issue, the client incorrectly reports that a product update is available for the Forefront Client Security client. A product update is not available.

Note In this scenario, the new product update notification differs from the new definition update notification.

Symptom 3
When you save a Microsoft Office Word document that already exists on a FAT32 volume, the file disappears unexpectedly. This occurs only when antivirus real-time protection (RTP) is enabled.

Symptom 4
The Microsoft Forefront Client Security Anti-malware Service stops unexpectedly. Then, this service does not recover automatically. This symptom occurs if the signature or the engine update is invalid.



Cause 1
Symptom 1 occurs because of a permission issue that is specific to Windows 2000. In Windows 2000, a non-administrator user is denied access to the RegisterGPNotification function. This function is used to monitor policy changes.

Cause 2
Symptom 2 occurs because a registry value is not reset as expected after a successful upgrade. To determine the current state of Forefront Client Security Agent, the Forefront Client Security client queries the following registry entry:

Note A value of 0 indicates that new updates are not needed. A value of 1 indicates that new updates are needed.

However, the Forefront Client Security client update package did not reset this registry value to 0 after the last upgrade.

Cause 3
Symptom 3 occurs for one of the following reasons:
 * Word sometimes deletes files when the temporary backup file cannot be accessed.
 * The I/O manager does not close a file correctly on a FAT32 volume if the Object Manager rejects the open action during security checks when the file is accessed.

Cause 4
Symptom 4 occurs because the Microsoft Forefront Client Security Anti-malware Service registers with the Service Control Manager (SCM) to automatically start two times after a failure. If an invalid signature causes the service to stop repeatedly, the SCM makes only two restart attempts and does not continue to restart the service.



Hotfix information
A hotfix is available to resolve these symptoms. This hotfix is available from Microsoft Update or from Windows Server Update Services. If you want to obtain the file for deployment by using a different method, contact Customer Support Services.

A supported hotfix is now 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. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Forefront Client Security service pack that contains this hotfix.

To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:

http://go.microsoft.com/?linkid=6294451

Note If additional issues occur or 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. To create a separate service request, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

Prerequisites
There are no prerequisites for installing this hotfix.

Restart requirement
You have to restart the computer after you apply this hotfix.

Hotfix replacement information
This hotfix does not replace a previously released hotfix.

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.

Forefront Client Security, x64-based versions

'Forefront Client Security, x86-based versions'



Workaround 1
To work around symptom 1, log on to the Windows 2000-based computer by using an administrator account.

Workaround 2
To work around symptom 2, follow these steps:

Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall the operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.  Click Start, click Run, type regedit, and then click OK. Locate and then click the following registry subkey:

 Right-click the AM registry subkey, and then click Permissions. Click Advance. On the Owner tab, click Other Users or Groups. In the Select User, Computer, or Group dialog box, add the Administrators group, and then click OK.</li> Click OK to exit the Advanced Security Settings dialog box.</li> Click OK to exit the Permissions dialog box.</li> Under the AM registry subkey that you located in step 2, right-click the ProductUpdateAvailable registry entry, and then click Modify.</li> In the Value data box, type 0, and then click OK.</li> Exit Registry Editor.</li></ol>

Note When the next Forefront Client Security client update becomes available, this problem will disappear because the update will reset the ProductUpdateAvailable registry entry to 0. The current resolution is for users who want to resolve the status immediately.

<div class="status_section">

STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section.

<div class="moreinformation_section">

MORE INFORMATION
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates

Keywords: kbbug kbfix kbqfe kbpubtypekc kbexpertiseinter kbprb KB938054

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.