Hello - I apologize if this is not in the proper location. We are having difficulty installing SP2 on a W2K8 SP1 x64 server. When we try to do this through Windows Updates, it runs for about 1 minute and then says that it completed successfully (when clearly it did not). When we run the file manually via the download, the install fails with the following error code: 0x800f0823 I have tried running the System Update Readiness Tool (KB947821), but that did not work. Additional info about the server: It is a domain controller, also running MS-Exchange 2007 SP1 (v8.01.0336.000). Any assistance that could be provided would be greatly appreciated. In you need any more info about the server, please let me know! Thanks!

1) Go to Settings / Control Panel (2) Go to Program Files and Features (3) Go to "Turn Windows Features On and Off" (4) Uncheck these: Microsoft .NET Framework 3.0 \XPS Viewer Remote Differential Compression Window DFS Replication Services (5) Install SP2 (6) Make sure to turn the three features above on after the installation completes

Hi , can you post the error message listed under windowsupdatelog.log

Hi, Error code 0x800f0823 occurs if either of the following reasons is true: l There are corrupt or missing systems files l The Windows Modules Installer needs to be updated To resolve this kind of problem, I would like to propose the following suggestions: 1. Perform a System File Check in offline mode to check and repair corrupt system files. 1) Boot from Windows Server 2008 DVD. 2) On the first screen of Setup, choose Next. 3) Choose Repair your computer. 4) On the System Recovery Options screen choose your installation of Windows and then click Next. 5) Click Command Prompt. 6) Type the following command: Sfc.exe /scannow /offbootdir:c:\ /offwindir=c:\windows 7) When complete type in exit to see if Windows startup now. Reference: Using System File Checker (SFC) To Fix Issues 2. Update the Windows Installer on your system, please download Windows Installer 4.5. 3. If the issue persists, let’s perform an In-place Upgrade to replace corrupted system files. In-place Upgrade is a special upgrade process to repair the system. In-place Upgrade will not affect settings like photos, movies, documents, etc. that are saved on the computer. It won’t require activation again. 1) Insert the Windows Server 2008 R2 Installation Disc to your DVD-ROM drive. If AutoPlay pops up, click “Run setup.exe” directly. 2) Click “Install now” on the “Install Windows” screen. 3) In the “Get important updates for installation” screen, it is recommended to select the first option to download latest updates for installation, if Internet access is available. 4) Check the box “I accept the license terms” to agree with the installation license and click “Next”. 5) In the “Which type of installation do you want?” screen, click “Upgrade” to perform the In-Place upgrade. Best Regards DalePlease remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

1) Go to Settings / Control Panel (2) Go to Program Files and Features (3) Go to "Turn Windows Features On and Off" (4) Uncheck these: Microsoft .NET Framework 3.0 \XPS Viewer Remote Differential Compression Window DFS Replication Services (5) Install SP2 (6) Make sure to turn the three features above on after the installation completes Hello Vinay - This is Windows 2008 Server. When I opened the 'Turn Windows Features On and Off' link, it brought me to the server manager MMC. The only role that is installed/configured is 'File Server' and 0 features are installed. Is there some place more specific that I need to look for this information? It does not pop up as the one in Vista or Win7 does.

Hi , can you post the error message listed under windowsupdatelog.log Hello Sainath - I believe this is the correct section (it was too large to paste all of the text here): 2010-12-14 13:08:54:878 440 3220 PT +++++++++++ PT: Synchronizing server updates +++++++++++ 2010-12-14 13:08:54:878 440 3220 PT + ServiceId = {7971F918-A847-4430-9279-4A52D1EFE18D}, Server URL = https://www.update.microsoft.com/v6/ClientWebService/client.asmx 2010-12-14 13:10:57:852 440 3220 Driver DriverUtil marking {B0FECA38-A371-4E8F-96BB-CBC5407957E5}.100 e_detectionStateInstallable 2010-12-14 13:10:57:852 440 3220 Driver Calculated driver attributes as 0x00000001 2010-12-14 13:10:58:974 440 3220 Agent WARNING: Failed to evaluate Installable rule, updateId = {7C7ECF1D-E808-41BA-B2BC-34E4ACBEFC12}.101, hr = 80070057 2010-12-14 13:11:05:251 440 3220 Agent WARNING: Failed to evaluate Installable rule, updateId = {5EE6BAD9-BDDE-4B1C-A297-B98AED6093E5}.100, hr = 80070057 2010-12-14 13:11:07:295 440 3220 Handler FATAL: UH: 0x800f0823: CreatePackage failed in CCbs::CreatePackage 2010-12-14 13:11:07:296 440 3220 Agent WARNING: Failed to evaluate Installed rule, updateId = {77DBCA97-29DC-42BA-9DB2-03C7B4D262D4}.107, hr = 80242017 2010-12-14 13:11:07:503 440 3220 Handler FATAL: UH: 0x800f0823: CreatePackage failed in CCbs::CreatePackage 2010-12-14 13:11:07:504 440 3220 Agent WARNING: Failed to evaluate Installable rule, updateId = {77DBCA97-29DC-42BA-9DB2-03C7B4D262D4}.107, hr = 80242017 2010-12-14 13:11:07:713 440 3220 Handler FATAL: UH: 0x800f0823: CreatePackage failed in CCbs::CreatePackage 2010-12-14 13:11:09:342 440 3220 Handler FATAL: UH: 0x800f0823: CreatePackage failed in CCbs::CreatePackage 2010-12-14 13:11:09:343 440 3220 Agent WARNING: Failed to evaluate Installed rule, updateId = {189CDA5A-A590-4520-A75E-86CF439504D7}.105, hr = 80242017 2010-12-14 13:11:09:542 440 3220 Handler FATAL: UH: 0x800f0823: CreatePackage failed in CCbs::CreatePackage 2010-12-14 13:11:09:542 440 3220 Agent WARNING: Failed to evaluate Installable rule, updateId = {189CDA5A-A590-4520-A75E-86CF439504D7}.105, hr = 80242017 2010-12-14 13:11:09:743 440 3220 Handler FATAL: UH: 0x800f0823: CreatePackage failed in CCbs::CreatePackage 2010-12-14 13:11:11:059 440 3220 Misc Validating signature for C:\Windows\SoftwareDistribution\WuRedir\7971F918-A847-4430-9279-4A52D1EFE18D\muv4muredir.cab: 2010-12-14 13:11:11:061 440 3220 Misc Microsoft signed: Yes 2010-12-14 13:11:11:262 440 3220 Misc Validating signature for C:\Windows\SoftwareDistribution\WuRedir\7971F918-A847-4430-9279-4A52D1EFE18D\muv4muredir.cab: 2010-12-14 13:11:11:264 440 3220 Misc Microsoft signed: Yes

Hi, Error code 0x800f0823 occurs if either of the following reasons is true: l There are corrupt or missing systems files l The Windows Modules Installer needs to be updated To resolve this kind of problem, I would like to propose the following suggestions: 1. Perform a System File Check in offline mode to check and repair corrupt system files. 1) Boot from Windows Server 2008 DVD. 2) On the first screen of Setup, choose Next. 3) Choose Repair your computer. 4) On the System Recovery Options screen choose your installation of Windows and then click Next. 5) Click Command Prompt. 6) Type the following command: Sfc.exe /scannow /offbootdir:c:\ /offwindir=c:\windows 7) When complete type in exit to see if Windows startup now. Reference: Using System File Checker (SFC) To Fix Issues 2. Update the Windows Installer on your system, please download Windows Installer 4.5. 3. If the issue persists, let’s perform an In-place Upgrade to replace corrupted system files. In-place Upgrade is a special upgrade process to repair the system. In-place Upgrade will not affect settings like photos, movies, documents, etc. that are saved on the computer. It won’t require activation again. 1) Insert the Windows Server 2008 R2 Installation Disc to your DVD-ROM drive. If AutoPlay pops up, click “Run setup.exe” directly. 2) Click “Install now” on the “Install Windows” screen. 3) In the “Get important updates for installation” screen, it is recommended to select the first option to download latest updates for installation, if Internet access is available. 4) Check the box “I accept the license terms” to agree with the installation license and click “Next”. 5) In the “Which type of installation do you want?” screen, click “Upgrade” to perform the In-Place upgrade. Best Regards Dale Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ” Hello Dale - unfortunately the server is in production, as well as being physically located in a remote office, so I cannot reboot into Safe mode, nor can I do an in-place upgrade (this is also an Exchange Server and a Domain Controller). I did try to install Windows Installer v4.5, but it told me that the file did not apply to my system (presumably because it is already installed). In addition, I did run "SFC /scannow", and it did report errors that were found, corrected and errors that could not be repaired (a system reboot is required as well, which I need to schedule with the site for off-hours).

I'm afraid to say that you need to schedule a time to do a handy repair other than remote assistance online. Best Regards DalePlease remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Hello, Dale. I seem to be having the same issue that Matt was having last month on this thread. I have a separate thread opened because I am receiving the 0x800F0823 error code in System Manager. It wasn't until I came across this post that I realized I was also getting that error with Windows Updates, as well. If you could, please visit the thread that I have going. I have followed all of the steps you advised above, but my issue persists. http://social.technet.microsoft.com/Forums/en-US/winservermanager/thread/95d8f0fb-3e5e-435b-9f08-d2882334cec0 Thanks.

Hello - jut an update - the problem persists, and we have actually taken a more radical approach, and are completely rebuilding the server. Ever since this server crashed a few years ago, there have been more and more problems culminating with the latest issue: W3SVC refuses to start, resulting in staff not being able to access webmail. We are following this guide for the rebuild: http://technet.microsoft.com/en-us/library/bb332343(EXCHG.80).aspx

Matt, it seems that Microsoft is pointing us to do the same thing. I spoke to Microsoft Professional Support on the phone for over 9 hours yesterday. They are now saying that if an in-place upgrade does not work, we'll have to rebuild the server. I don't see how this issue could have such little documentation. It seems to be a rare and obscure error, but that shouldn't mean it can't be resolved. We just built this server around 5 months ago. I can't believe it needs to be rebuilt already.