SP2 - Does Not Install

[Mark]

When trying to install Vista SP2 the error code 800f0823 is returned and the
update fails. Have searched for a reason but cannot find anything with this
error code. Any ideas?

 

[Jdr]

Just google 'Vista SP2 the error code 800f0823' and see what you get

http://www.google.co.uk/search?sour...B321GB322&q=Vista+SP2+the+error+code+800f0823

 

[chas2209]

Look Here
http://support.microsoft.com/kb/KB925316

chas2209

 

[Dave]

MSFT has free support for SP2 issues....
http://support.microsoft.com/oas/de...ctl=ActiveScripting&wf=PID&ln=en-us&tzone=240

 

[Mark]

After doing all the above, still get the same error and SP2 does not
install.

 

[Tae Song]

Delete C:\Windows\Logs\CBS\CBS.log
(a persistant copy is kept in CBS.persist.log)

Run SFC /SCANNOW

After it finishes, make a copy and open it.

Once you open CBS - copy.LOG, search for "Beginning Verify and Repair". It
should
be near the end of the log. Post everything starting from "Beginning Verify
and Repair" to the end.

<to be continued>

 

[propman]

Delete C:\Windows\Logs\CBS\CBS.log
(a persistant copy is kept in CBS.persist.log)

Run SFC /SCANNOW

After it finishes, make a copy and open it.

Once you open CBS - copy.LOG, search for "Beginning Verify and Repair".
It should
be near the end of the log. Post everything starting from "Beginning
Verify and Repair" to the end.

<to be continued>

FWIW....more info here:

http://support.microsoft.com/kb/929833

 

[Dion Lee]

I update with no probs!

Do all your updates BEFORE installing a service pack.

 

[Mark]

Per Tae Song's request, here is the result of running SFC (rather long):

Per Tae Song's request, here is the result of running SFC (rather long):

2009-06-03 19:14:07, Info CBS Loaded Servicing Stack
v6.0.6001.18000 with Core:
C:\Windows\winsxs\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.0.6001.18000_none_095f6148c74a7a64\cbscore.dll
2009-06-03 19:14:07, Info CSI
00000001@2009/6/4:02:14:07.932 WcpInitialize (wcp.dll version 0.0.0.5)
called (stack @0x6e5f8504 @0x73a68439 @0x73a462a3 @0xa41392 @0xa41ed4
@0xa417cb)
2009-06-03 19:14:07, Info CSI
00000002@2009/6/4:02:14:07.947 WcpInitialize (wcp.dll version 0.0.0.5)
called (stack @0x6e5f8504 @0x73a9e615 @0x73a80dec @0xa41392 @0xa41ed4
@0xa417cb)
2009-06-03 19:14:07, Info CSI
00000003@2009/6/4:02:14:07.947 WcpInitialize (wcp.dll version 0.0.0.5)
called (stack @0x6e5f8504 @0x73c71a0d @0x73c71794 @0xa4360b @0xa42be3
@0xa417cb)
2009-06-03 19:14:07, Info CBS NonStart: Checking to
ensure startup processing was not required.
2009-06-03 19:14:07, Info CSI 00000004
IAdvancedInstallerAwareStore_ResolvePendingTransactions (call 1) (flags =
00000004, progress = NULL, phase = 0, pdwDisposition = @0x133fef4
2009-06-03 19:14:07, Info CBS NonStart: Success, startup
processing not required as expected.
2009-06-03 19:14:07, Info CSI 00000005 CSI Store 1701776
(0x0019f790) initialized
2009-06-03 19:14:10, Info CSI 00000006 [SR] Verifying
100 (0x00000064) components
2009-06-03 19:14:10, Info CSI 00000007 [SR] Beginning
Verify and Repair transaction
2009-06-03 19:14:14, Info CSI 00000008 Repair results
created:
POQ 0 starts:
0: Move File: Source =
[l:192{96}]"\SystemRoot\WinSxS\Temp\PendingRenames\0453dc27bae4c9016500000054111c10._0000000000000000.cdf-ms",
Destination =
[l:104{52}]"\SystemRoot\WinSxS\FileMaps\_0000000000000000.cdf-ms"
1: Move File: Source =
[l:218{109}]"\SystemRoot\WinSxS\Temp\PendingRenames\5eb5de27bae4c9016600000054111c10.program_files_ffd0cbfc813cc4f1.cdf-ms",
Destination =
[l:130{65}]"\SystemRoot\WinSxS\FileMaps\program_files_ffd0cbfc813cc4f1.cdf-ms"
2: Move File: Source =
[l:244{122}]"\SystemRoot\WinSxS\Temp\PendingRenames\5eb5de27bae4c9016700000054111c10.program_files_common_files_d7a65bb2f0e854e7.cdf-ms",
Destination =
[l:156{78}]"\SystemRoot\WinSxS\FileMaps\program_files_common_files_d7a65bb2f0e854e7.cdf-ms"
3: Move File: Source =
[l:278{139}]"\SystemRoot\WinSxS\Temp\PendingRenames\5eb5de27bae4c9016800000054111c10.program_files_common_files_microsoft_shared_818c5a0e45020fba.cdf-ms",
Destination =
[l:190{95}]"\SystemRoot\WinSxS\FileMaps\program_files_common_files_microsoft_shared_818c5a0e45020fba.cdf-ms"
4: Move File: Source =
[l:286{143}]"\SystemRoot\WinSxS\Temp\PendingRenames\5eb5de27bae4c9016900000054111c10.program_files_common_files_microsoft_shared_ink_3c86e3db0b3b254c.cdf-ms",
Destination =
[l:198{99}]"\SystemRoot\WinSxS\FileMaps\program_files_common_files_microsoft_shared_ink_3c86e3db0b3b254c.cdf-ms"
5: Move File: Source =
[l:292{146}]"\SystemRoot\WinSxS\Temp\PendingRenames\b817e127bae4c9016a00000054111c10.program_files_common_files_microsoft_shared_ink_en_7a951cedcb9a5105.cdf-ms",
Destination =
[l:204{102}]"\SystemRoot\WinSxS\FileMaps\program_files_common_files_microsoft_shared_ink_en_7a951cedcb9a5105.cdf-ms"
6: Move File: Source =
[l:162{81}]"\SystemRoot\WinSxS\Temp\PendingRenames\7a03ed27bae4c9016b00000054111c10.$$.cdf-ms",
Destination = [l:74{37}]"\SystemRoot\WinSxS\FileMaps\$$.cdf-ms"
7: Move File: Source =
[l:208{104}]"\SystemRoot\WinSxS\Temp\PendingRenames\7a03ed27bae4c9016c00000054111c10.$$_ehome_40103e2da1d
2009-06-03 19:14:14, Info CSI 121de.cdf-ms", Destination
= [l:120{60}]"\SystemRoot\WinSxS\FileMaps\$$_ehome_40103e2da1d121de.cdf-ms"

POQ 0 ends.
2009-06-03 19:14:14, Info CSI 00000009 [SR] Verify
complete
2009-06-03 19:14:14, Info CSI 0000000a [SR] Verifying
100 (0x00000064) components
2009-06-03 19:14:14, Info CSI 0000000b [SR] Beginning
Verify and Repair transaction
2009-06-03 19:14:18, Info CSI 0000000c Repair results
created:
POQ 1 starts:

POQ 1 ends.

 

[Mark]

2009-06-03 19:14:18, Info CSI 0000000d [SR] Verify
complete
2009-06-03 19:14:19, Info CSI 0000000e [SR] Verifying
100 (0x00000064) components
2009-06-03 19:14:19, Info CSI 0000000f [SR] Beginning
Verify and Repair transaction
2009-06-03 19:14:20, Info CSI 00000010 Repair results
created:
POQ 2 starts:

POQ 2 ends.
2009-06-03 19:14:20, Info CSI 00000011 [SR] Verify
complete
2009-06-03 19:14:20, Info CSI 00000012 [SR] Verifying
100 (0x00000064) components
2009-06-03 19:14:20, Info CSI 00000013 [SR] Beginning
Verify and Repair transaction
2009-06-03 19:14:21, Info CSI 00000014 Repair results
created:
POQ 3 starts:

POQ 3 ends.
2009-06-03 19:14:21, Info CSI 00000015 [SR] Verify
complete
2009-06-03 19:14:21, Info CSI 00000016 [SR] Verifying
100 (0x00000064) components
2009-06-03 19:14:21, Info CSI 00000017 [SR] Beginning
Verify and Repair transaction
2009-06-03 19:14:22, Info CSI 00000018 Repair results
created:
POQ 4 starts:

POQ 4 ends.
2009-06-03 19:14:22, Info CSI 00000019 [SR] Verify
complete
2009-06-03 19:14:22, Info CSI 0000001a [SR] Verifying
100 (0x00000064) components
2009-06-03 19:14:22, Info CSI 0000001b [SR] Beginning
Verify and Repair transaction
2009-06-03 19:14:23, Info CSI 0000001c Repair results
created:
POQ 5 starts:

POQ 5 ends.
2009-06-03 19:14:23, Info CSI 0000001d [SR] Verify
complete
2009-06-03 19:14:24, Info CSI 0000001e [SR] Verifying
100 (0x00000064) components
2009-06-03 19:14:24, Info CSI 0000001f [SR] Beginning
Verify and Repair transaction
2009-06-03 19:14:25, Info CSI 00000020 Repair results
created:
POQ 6 starts:

POQ 6 ends.
2009-06-03 19:14:25, Info CSI 00000021 [SR] Verify
complete
2009-06-03 19:14:25, Info CSI 00000022 [SR] Verifying
100 (0x00000064) components
2009-06-03 19:14:25, Info CSI 00000023 [SR] Beginning
Verify and Repair transaction
2009-06-03 19:14:27, Info CSI 00000024 Repair results
created:
POQ 7 starts:

POQ 7 ends.
2009-06-03 19:14:27, Info CSI 00000025 [SR] Verify
complete
2009-06-03 19:14:28, Info CSI 00000026 [SR] Verifying
100 (0x00000064) components
2009-06-03 19:14:28, Info CSI 00000027 [SR] Beginning
Verify and Repair transaction
2009-06-03 19:14:30, Info CSI 00000028 Repair results
created:
POQ 8 starts:

POQ 8 ends.
2009-06-03 19:14:30, Info CSI 00000029 [SR] Verify
complete
2009-06-03 19:14:30, Info CSI 0000002a [SR] Verifying
100 (0x00000064) components
2009-06-03 19:14:30, Info CSI 0000002b [SR] Beginning
Verify and Repair transaction
2009-06-03 19:14:31, Info CSI 0000002c Repair results
created:
POQ 9 starts:

POQ 9 ends.
2009-06-03 19:14:31, Info CSI 0000002d [SR] Verify
complete
2009-06-03 19:14:32, Info CSI 0000002e [SR] Verifying
100 (0x00000064) components
2009-06-03 19:14:32, Info CSI 0000002f [SR] Beginning
Verify and Repair transaction
2009-06-03 19:14:34, Info CSI 00000030 Repair results
created:
POQ 10 starts:

POQ 10 ends.

 

[Tae Song]

Per Tae Song's request, here is the result of running SFC (rather long):

<snip>


I should amend that... only if SPC finds problems it can't fix.

 

[Tae Song]

I recommend running the System Update Readiness Tool. System resources,
such as file data, registry data, and even in-memory data, can develop
inconsistencies during the lifetime of the operating system. These
inconsistencies can be caused by various hardware failures or software
issues. In some cases, these inconsistencies can affect the Windows
servicing store, and they can cause software updates not to work. We can
run the System Update Readiness Tool to resolve these inconsistencies.
When the System Update Readiness Tool detects incorrect manifests,
files, or registry data, it might replace the incorrect data with a
corrected version. Please make sure that the current operating system is
Windows Vista SP1 and follow the steps below.

Step 1: Run the System Update Readiness Tool
====================================
1. Please download the System Update Readiness Tool from the link below
according to the System Type:

System Update Readiness Tool for Windows Vista 32-bit
'_http://www.microsoft.com/downloads/...c-ee87-4607-8aa5-812e8078ab27&DisplayLang=en_'
(wlmailhtml:{A1050D68-8633-4FF6-A124-AB4F57805E51}mid://00000002/!x-usc:http://www.microsoft.com/downloads/...9c-ee87-4607-8aa5-812e8078ab27&DisplayLang=en)

System Update Readiness Tool for Windows Vista 64-bit
'_http://www.microsoft.com/downloads/...3-007c-493f-bece-243bc21ac73d&DisplayLang=en_'
(wlmailhtml:{A1050D68-8633-4FF6-A124-AB4F57805E51}mid://00000002/!x-usc:http://www.microsoft.com/downloads/...73-007c-493f-bece-243bc21ac73d&DisplayLang=en)

I tried the System Update Readiness Tool for Windows Vista 32-bit. It
didn't work for me, but it may work for somebody else.

I ended up having to run SFC /SCANNOW and editing the registry to fix my
problem.