SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

One of my client did the Vulnerability test on my sharepoint production box. In the Vulnerability report they have mention the list of missing windows KB patches.

Now i wanted to know how to validate the this windows KB patches. Whether its creating any impact on sharepoint or not.

Please advice me....

Thanks in advance

share|improve this question

For a list of patching levels Dave Coleman maintains a list of

In your SharePoint farm, under System there is a link showing the Upgrading and Patching level for each server, with the KB next to each update, some might be in red, which clearly indicates an update needed. Use that KB number to identify in which Cumulative Update it exists and then you could plan for its installation.

Same KB numbers are also visible in Windows>Control Panel, under System Updates.

share|improve this answer
Thanks for the quick reply. – Optimus May 19 '12 at 6:26
But the list which is provided by the client its not related to sharepoint. Its related to windows 2008 server security. I am worried if any patch will create any bad impact on the sharepoint. then my live site will down. So need to validate each of this patches. – Optimus May 19 '12 at 6:28
Regularly no patches have impact on a SharePoint farm. You should plan however before installing updates such as .NET framework, or manipulating IIS Components, etc, but security patches should be fine. My explanation should help you identify which of those patches coincide with those installed by SharePoint. REMEMBER: CUs only replaces (updates) software packages ALREADY installed - all others are ignored! – Marius Constantinescu - MVP May 20 '12 at 11:06

Very few patches have had a direct, negative impact on SharePoint 2010. The single patch I can think of that has created a direct impact on 2010 was MS11-100 which a fix was issued for SharePoint in the April 2012 CU.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.