Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

Automatic Updates and WSUS stop working after a repair install of Windows Server 2003


Author: Richard Harper MVP

View products that this article applies to.

Summary

Windows Server 2003 Repair installation causes Automatic Updates and Windows Server Update Services (WSUS) to no longer recognize that updates are needed, leaving the server in a vulnerable state until Windows Service Packs and updates are re-applied

↑ Back to the top


Symptoms

After performing a repair install of Windows Server 2003 using the Repair feature of Windows Setup, your server will no longer automatically download updates via Automatic Updates or from a Windows Server Update Services (WSUS) server even if it has been configured to do so.� There is no warning reported and no visible sign that Automatic Updates or WSUS are no longer functioning as configured.

Since the repair install will remove all Service Packs and security updates that may have been installed on your server, you cannot rely on Automatic Updates or WSUS to re-apply Service Packs or updates to protect your server.� You will need to manually install Windows�Service Packs and updates to protect your computer.� Until you do your server will be unprotected against any vulnerabilities that were previously resolved by Service Packs or security updates.

↑ Back to the top


Cause

A Repair install of Windows removes any Service Packs and updates that were previously installed.�The repair install also replaces Windows Update client files on your�server with older versions of�these�files.�As a result, Automatic Updates and WSUS believe that your server is still up-to-date and will not download or install any Service Packs or updates that your server needs after the Repair install.� Since Automatic Updates and WSUS believe the server is up to date on Service PAcks and updates, no warnings or error messages are generated

↑ Back to the top


Resolution

To resolve the Automatic Updates or WSUS problem (and to protect your server against vulnerabilities) go to either the Windows Update or Microsoft Update web sites and install any needed Service Packs or updates.� Once you have downloaded and installed at least one critical update from the Windows Update or Microsoft Update web site, Automatic Updates and WSUS will once again correctly detect, download or install Service Packs or updates depending on what settings you have selected for Automatic Updates or WSUS on your server.

↑ Back to the top


More information

Thanks to Ron Martell and Larry Samuels for helping to diagnose why the Automatic Updates and WSUS processes were failing.
Further thanks to the Microsoft Windows Update engineering team for clarifying the issues involved in causing AU to fail.

↑ Back to the top


Properties

COMMUNITY SOLUTIONS CONTENT DISCLAIMER
MICROSOFT CORPORATION AND/OR ITS RESPECTIVE SUPPLIERS MAKE NO REPRESENTATIONS ABOUT THE SUITABILITY, RELIABILITY, OR ACCURACY OF THE INFORMATION AND RELATED GRAPHICS CONTAINED HEREIN. ALL SUCH INFORMATION AND RELATED GRAPHICS ARE PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT AND/OR ITS RESPECTIVE SUPPLIERS HEREBY DISCLAIM ALL WARRANTIES AND CONDITIONS WITH REGARD TO THIS INFORMATION AND RELATED GRAPHICS, INCLUDING ALL IMPLIED WARRANTIES AND CONDITIONS OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, WORKMANLIKE EFFORT, TITLE AND NON-INFRINGEMENT. YOU SPECIFICALLY AGREE THAT IN NO EVENT SHALL MICROSOFT AND/OR ITS SUPPLIERS BE LIABLE FOR ANY DIRECT, INDIRECT, PUNITIVE, INCIDENTAL, SPECIAL, CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF USE, DATA OR PROFITS, ARISING OUT OF OR IN ANY WAY CONNECTED WITH THE USE OF OR INABILITY TO USE THE INFORMATION AND RELATED GRAPHICS CONTAINED HEREIN, WHETHER BASED ON CONTRACT, TORT, NEGLIGENCE, STRICT LIABILITY OR OTHERWISE, EVEN IF MICROSOFT OR ANY OF ITS SUPPLIERS HAS BEEN ADVISED OF THE POSSIBILITY OF DAMAGES.

↑ Back to the top


Community solutions content disclaimer

Microsoft corporation and/or its respective suppliers make no representations about the suitability, reliability, or accuracy of the information and related graphics contained herein. All such information and related graphics are provided "as is" without warranty of any kind. Microsoft and/or its respective suppliers hereby disclaim all warranties and conditions with regard to this information and related graphics, including all implied warranties and conditions of merchantability, fitness for a particular purpose, workmanlike effort, title and non-infringement. You specifically agree that in no event shall Microsoft and/or its suppliers be liable for any direct, indirect, punitive, incidental, special, consequential damages or any damages whatsoever including, without limitation, damages for loss of use, data or profits, arising out of or in any way connected with the use of or inability to use the information and related graphics contained herein, whether based on contract, tort, negligence, strict liability or otherwise, even if Microsoft or any of its suppliers has been advised of the possibility of damages.

↑ Back to the top


Keywords: KB555616, kbhowto, kbpubtypecca, kbpubmvp

↑ Back to the top

Article Info
Article ID : 555616
Revision : 1
Created on : 5/26/2006
Published on : 5/26/2006
Exists online : False
Views : 258