FCS v1 Update

Hello all,

A short note, but on October 12th, we released an update to FCSv1.   This update contains:

  • This update is supported on Windows 7 SP1 RC or greater.  Windows 7 Service Pack 1 will check for the presence of this update or a superseding update before installing.
  • This update contains changes to the Forefront Client Security service to improve remediation of certain malicious software.
  • This update corrects two issues in the mpfilter.sys kernel component used by Client Security that cause deadlocks.
  • This update corrects an issue during definition update, computers that utilize the Volume Shadow Copy service appear to hang for several minutes. This issue may occur on computers using backup software that leverages shadow copy volumes.
  • This update corrects a stop error with the error code 0x00000050 on computers running Windows Vista, Windows 2008 Server, Windows 7 or Windows 2008 R2 Server. If Client Security is installed on a computer. 
  • This update increases the priority of the antimalware engine and definitions that are loaded during antimalware service start. The priority change enables the antimalware service to handle requests sooner, mitigating the UI unresponsiveness. However, this change may slightly increase boot time on limited systems by consuming more processor resources during system start.
  • This update corrects an issue in real-time protection when volumes are encrypted using certain 3rd party technologies.

For already installed FCS client installations, install the update for Microsoft Knowledge Base article 2394433 (http://support.microsoft.com/kb/2394433/).
For new FCS Client installations, deploy the client components listed in Microsoft Knowledge Base article
2394439 (http://support.microsoft.com/kb/2394439/).

For more information about the update, Microsoft Knowledge Base article 2394439 (http://support.microsoft.com/kb/2394439) will have the detail.


Douglas Hill
Program Manager

Comments (3)
  1. Hi Wayne,

    Thanks for the question. This update will show up in WSUS as a package to be deployed, and you can use Configuration Manager to deploy this update just like any other security update.


  2. Wayne says:

    How do you deploy this via SCCM/FCS integration?

  3. Faron (MSFT) says:

    Just to be clear, on the WSUS server, you need to do two things:

    1. approve KB2394439 (the 'deployment package') for *new* FCS installations

    2. approve KB2393433 to upgrade *existing* FCS clients.


Comments are closed.

Skip to main content