SP1 Install fails and other problems

WhiteShark

New Member
(WARNING - LONG POST!)

If finally decided to install VISTA x64 SP1 two weeks ago, and ever since there's been nothing but hassle. I have tried unsuccessfully 8 times to get it to install but no joy - failing at stage 3 out of 3 @ 100% each time :cry:.

This problem applies to the Windows Update version and the standalone installer tried - both fail.

Here's what I've done to try and get this working:

(i) Made sure all required KB's and everything else is up to date before install.
(ii) Run sfc / scannow to test system files (this is where the problem lies I think)
(iii) Tested RAM using Memtestx86 and Windows memory tester and all 4GB pass multiple runs with no errors (left running for 24 hours to be sure).
(iv) Ran hard drive checks - all o.k there.
(v) Disabled AVG AntiVirus, Defender and all other startup programs which might interfere with SP1.
(vi) Done everything the damn MS site tells me to do in order to prepare basically and what to do if it cocks-up:mad:.

Here's the bigger picture:

Running sfc /scannow from the command prompt in Administrator mode - goes all the way to 100%, and then it tells me it found corrupted files , 'but was unable to fix some of them - check cbs.log for details'

(a- ha this is may be why SP1 doesn't want to play ball perhaps?)

I check the log, and it identifies part of the speech recognition files as corrupt (s2057.dlm) - tail end of CBS log where errors are shown I've listed below (rest of log shown no other errors btw):

POQ 99 ends.
2008-03-29 09:50:33, Info CSI 0000027d [SR] Verify complete
2008-03-29 09:50:33, Info CSI 0000027e [SR] Repairing 2 components
2008-03-29 09:50:33, Info CSI 0000027f [SR] Beginning Verify and Repair transaction
2008-03-29 09:50:34, Info CSI 00000280 [SR] Cannot repair member file [l:18{9}]"s2057.dlm" of Microsoft-Windows-SpeechRecognizerENG.ale, Version = 6.0.6000.16386, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture = [l:10{5}]"en-GB", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file cannot be checked
2008-03-29 09:50:34, Info CSI 00000281 Hashes for file member \SystemRoot\WinSxS\x86_microsoft-windows-s..chrecognizereng.ale_31bf3856ad364e35_6.0.6000.16386_en-gb_857893b11436ae5f\s2057.dlm do not match actual file [l:18{9}]"s2057.dlm" :
Found: {l:32 b:GGSpeWpPSbKCCWzU1DY9XEXX1Z1O6/u0UcI9JvfDSLU=} Expected: {l:32 b:WxRC+kf331EqPevUsp89VY5d7ZIpZFxj/24FdGgwPig=}
2008-03-29 09:50:34, Info CSI 00000282 [SR] Cannot repair member file [l:18{9}]"s2057.dlm" of Microsoft-Windows-SpeechRecognizerENG.ale, Version = 6.0.6000.16386, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture = [l:10{5}]"en-GB", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2008-03-29 09:50:35, Info CSI 00000283 Hashes for file member \SystemRoot\WinSxS\x86_microsoft-windows-s..chrecognizereng.ale_31bf3856ad364e35_6.0.6000.16386_en-gb_857893b11436ae5f\s2057.dlm do not match actual file [l:18{9}]"s2057.dlm" :
Found: {l:32 b:GGSpeWpPSbKCCWzU1DY9XEXX1Z1O6/u0UcI9JvfDSLU=} Expected: {l:32 b:WxRC+kf331EqPevUsp89VY5d7ZIpZFxj/24FdGgwPig=}
2008-03-29 09:50:35, Info CSI 00000284 [SR] Cannot repair member file [l:18{9}]"s2057.dlm" of Microsoft-Windows-SpeechRecognizerENG.ale, Version = 6.0.6000.16386, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture = [l:10{5}]"en-GB", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2008-03-29 09:50:37, Info CSI 00000285 [SR] Cannot repair member file [l:18{9}]"s2057.dlm" of Microsoft-Windows-SpeechRecognizerENG.ale, Version = 6.0.6000.16386, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture = [l:10{5}]"en-GB", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file cannot be checked
2008-03-29 09:50:37, Info CSI 00000286 Repair results created:
POQ 100 starts:
0: Move File: Source = [l:192{96}]"\SystemRoot\WinSxS\Temp\PendingRenames\4d8099568291c801ab2c0000980be40c._0000000000000000.cdf-ms", Destination = [l:104{52}]"\SystemRoot\WinSxS\FileMaps\_0000000000000000.cdf-ms"
1: Move File: Source = [l:162{81}]"\SystemRoot\WinSxS\Temp\PendingRenames\6dce99568291c801ac2c0000980be40c.$$.cdf-ms", Destination = [l:74{37}]"\SystemRoot\WinSxS\FileMaps\$$.cdf-ms"
2: Move File: Source = [l:244{122}]"\SystemRoot\WinSxS\Temp\PendingRenames\ed069b568291c801ad2c0000980be40c.$$_speech_engines_sr_en-gb_3201b387cd317f4d.cdf-ms", Destination = [l:156{78}]"\SystemRoot\WinSxS\FileMaps\$$_speech_engines_sr_en-gb_3201b387cd317f4d.cdf-ms"
3: Move File: Source = [l:254{127}]"\SystemRoot\WinSxS\Temp\PendingRenames\fd2d9b568291c801ae2c0000980be40c.$$_speech_engines_lexicon_en-gb_bd71d721f658dd56.cdf-ms", Destination = [l:166{83}]"\SystemRoot\WinSxS\FileMaps\$$_speech_engines_lexicon_en-gb_bd71d721f658dd56.cdf-ms"

POQ 100 ends.
2008-03-29 09:50:37, Info CSI 00000287 [SR] Repair complete
2008-03-29 09:50:37, Info CSI 00000288 [SR] Committing transaction
2008-03-29 09:50:37, Info CSI 00000289 Creating NT transaction (seq 1), objectname [6]"(null)"
2008-03-29 09:50:37, Info CSI 0000028a Created NT transaction (seq 1) result 0x00000000, handle @0x1104
2008-03-29 09:50:37, Info CSI 0000028b@2008/3/29:09:50:37.939 CSI perf trace:
CSIPERF:TXCOMMIT;866
2008-03-29 09:50:37, Info CSI 0000028c [SR] Verify and Repair Transaction completed. All files and registry keys listed in this transaction have been successfully repaired
2008-03-29 09:54:35, Info CBS Session: 29921666:3840242429 initialized.
2008-03-29 09:54:35, Info CBS Session: 29921666:3840242429 finalized. Reboot required: no

O.k, no problem I thought I can replace that file, and following advice found on these forums, I installed the Windows AIK (1GB:eek:!), mounted 'install.wim' off my VISTAx64 DVD onto a separate hard disc from my o/s, and then copied across a clean version of the speech engine folder so that I can replace this problematic file - so far so good.

I then take ownership of the original folder and files (otherwise it won't let you overwrite them as they are owned by the SYSTEM), and I then replace the dodgy file in question with the fresh copy.

I run sfc again - still finds the same corrupted file, so I then decide to replace the whole folder and all it's associated files - reboot, then run sfc again and it still finds it as corrupt:mad:.

In a nutshell - can anyone tell me why sfc would report it as corrupt when I've replaced it with a fresh copy straight from the DVD image? What else can I do to get this sorted? (and I REALLY don't want to do a clean re-install if I can help it).

I'm desperate to get this fixed as there's no way I'm attempting to try and re-install SP1 again until sfc passes with no errors as I really feel that's what's causing this. I'm also doubly frustrated as people are reporting decent performance gains with SP1, particularly with games or 3D apps in general, and also I might end up being stuffed for future updates from MS or other software vendors which will need sp1 installed, before they will.

Can anyone offer any other advice as I've done just about everything possible to repair the corrupted files, and checked everything else in order to make the sp1 install process as trouble free as possible.

Cheers
 

My Computer

System One

  • CPU
    QX6700 @3.2Ghz
    Motherboard
    Nforce 680i SLi (P32 BIOS)
    Memory
    4GB Corsair Dominator PC28500 (2x2GB) 5-5-5-15-2T @2.1v
    Graphics Card(s)
    EVGA 8800GTX ACS3 (SLi)
    Hard Drives
    3 x 320Gb Seagate Barracuda SATA
Back
Top