No repair Install with Dell Supplied Vista Disk

stueycaster

Millennium Celebration Award Winner
Premium Supporter
My wife's Dell Inspiron 1521 laptop came with Vista Home Premium on it. She couldn't deal with Vista so I set it up to dual boot XP Home also.

This is it's hardware:

Motherboard:
CPU Type Mobile DualCore AMD Turion 64 X2 TL-58, 1900 MHz (9.5 x 200)
Motherboard Name Dell Inspiron 1521
Motherboard Chipset AMD M690T, AMD Hammer
System Memory 1920 MB (DDR2-667 DDR2 SDRAM)
Display:
Video Adapter ATI Radeon X1270 (700 MB)
Video Adapter ATI Radeon X1270 (700 MB)
3D Accelerator ATI RS690M
Storage:
IDE Controller Ricoh Memory Stick Controller
IDE Controller Ricoh MMC Host Controller
IDE Controller Ricoh xD-Picture Card Controller
IDE Controller Standard Dual Channel PCI IDE Controller
IDE Controller Standard Dual Channel PCI IDE Controller
Disk Drive ST9160821AS (160 GB, 5400 RPM, SATA)
Optical Drive Optiarc DVD+-RW AD-5560A
SMART Hard Disks Status OK

The problem is Vista can't apply Windows Updates. They seem to download properly but when it tries to install them it reaches a certain point then it stops, says it can't finish and backs out of the installation. I'm sorry but I don't have a copy of the error message.

This is what SFC says about it:

2009-11-15 21:02:42, Info CSI 00000054 [SR] Cannot repair member file [l:22{11}]"HpCISSs.sys" of hpcisss.inf, Version = 6.0.6002.18005, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type = [l:24{12}]"driverUpdate", TypeName neutral, PublicKey neutral in the store, file is missing
2009-11-15 21:02:49, Info CSI 00000055 [SR] Cannot repair member file [l:22{11}]"HpCISSs.sys" of hpcisss.inf, Version = 6.0.6002.18005, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type = [l:24{12}]"driverUpdate", TypeName neutral, PublicKey neutral in the store, file is missing
2009-11-15 21:02:49, Info CSI 00000056 [SR] This component was referenced by [l:158{79}]"Package_25_for_KB948465~31bf3856ad364e35~x86~~6.0.1.18005.948465-77_neutral_GDR"
2009-11-15 21:02:50, Info CSI 0000005a [SR] Beginning Verify and Repair transaction
2009-11-15 21:02:52, Info CSI 0000005b [SR] Cannot repair member file [l:22{11}]"msimain.sdb" of Microsoft-Windows-Application-Experience-Mitigations-C2, Version = 6.0.6002.18005, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
2009-11-15 21:02:57, Info CSI 0000005c [SR] Cannot repair member file [l:22{11}]"msimain.sdb" of Microsoft-Windows-Application-Experience-Mitigations-C2, Version = 6.0.6002.18005, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
2009-11-15 21:02:57, Info CSI 0000005d [SR] This component was referenced by [l:160{80}]"Package_25_for_KB948465~31bf3856ad364e35~x86~~6.0.1.18005.948465-113_neutral_GDR"
2009-11-15 21:02:57, Info CSI 0000005e [SR] Could not reproject corrupted file [ml:520{260},l:46{23}]"\??\C:\Windows\apppatch"\[l:22{11}]"msimain.sdb"; source file in store is also corrupted
009-11-15 21:12:38, Info CSI 00000193 [SR] Beginning Verify and Repair transaction
2009-11-15 21:12:38, Info CSI 00000194 [SR] Cannot repair member file [l:22{11}]"HpCISSs.sys" of hpcisss.inf, Version = 6.0.6002.18005, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type = [l:24{12}]"driverUpdate", TypeName neutral, PublicKey neutral in the store, file is missing
2009-11-15 21:12:38, Info CSI 00000195 [SR] Cannot repair member file [l:22{11}]"msimain.sdb" of Microsoft-Windows-Application-Experience-Mitigations-C2, Version = 6.0.6002.18005, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
2009-11-15 21:12:38, Info CSI 00000196 [SR] Cannot repair member file [l:22{11}]"msimain.sdb" of Microsoft-Windows-Application-Experience-Mitigations-C2, Version = 6.0.6002.18005, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
2009-11-15 21:12:38, Info CSI 00000197 [SR] This component was referenced by [l:160{80}]"Package_25_for_KB948465~31bf3856ad364e35~x86~~6.0.1.18005.948465-113_neutral_GDR"
2009-11-15 21:12:38, Info CSI 00000198 [SR] Could not reproject corrupted file [ml:520{260},l:46{23}]"\??\C:\Windows\apppatch"\[l:22{11}]"msimain.sdb"; source file in store is also corrupted
2009-11-15 21:12:38, Info CSI 00000199 [SR] Cannot repair member file [l:22{11}]"HpCISSs.sys" of hpcisss.inf, Version = 6.0.6002.18005, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type = [l:24{12}]"driverUpdate", TypeName neutral, PublicKey neutral in the store, file is missing
2009-11-15 21:12:38, Info CSI 0000019a [SR] This component was referenced by [l:158{79}]"Package_25_for_KB948465~31bf3856ad364e35~x86~~6.0.1.18005.948465-77_neutral_GDR"

Now it won't allow me to run a Windows Repair Installation. It wants to install from the Recovery Console and do a Factory Installation. The last time I did that it trashed the XP boot loader.

Is there a way I can trick it into allowing a repair installation with the Vista disk provided by Dell? If not is there a way I can replace the missing or corrupted files that SFC found? I'm a little afraid to go blundering into something like that without a little expert advice.
 
Last edited:

stueycaster

Millennium Celebration Award Winner
Premium Supporter
Hi Stuey,
if you use this utility found here:

Download EasyBCD For Windows 7

It will allow you to easily repair any problems with the bootloader. This means you can use the recovery console as required....
The last time I did this I couldn't get XP to work with EasyBCD or VistaBootPro. I don't know. Maybe there was a problem with XP that I didn't realize I had. I'll look things in XP over a little. Maybe run SFC on it and make sure it's alright before I try. I'd hate to mess up her XP again though. I've messed things up for her more than once.

Does EasyBCD for Windows 7 work on Vista? Or should I look for a Vista version?
 

kemical

Windows Forum Admin
Staff member
Premium Supporter
I think it should fine.. All it's really saying is that it will work on win 7 so it should be fine for vista.. If in doubt though....


If it does mess up the XP install you could always try running the repair option for xp and that should cure the problem..
 
Last edited:

stueycaster

Millennium Celebration Award Winner
Premium Supporter
Thanks Kemical buddy. I'll see what I can do. One more question if you don't mind. Do other people have trouble with dual booting or is it just me. I'd reached the point where I swore I'd never do it again but here I am, trying again.
 

kemical

Windows Forum Admin
Staff member
Premium Supporter
Lol...nope others get problems just the same so don't feel too disheartened.. :)
 

kemical

Windows Forum Admin
Staff member
Premium Supporter
Don't forget man, if you need any help just shout..
mixed-smiley-021.gif
 

stueycaster

Millennium Celebration Award Winner
Premium Supporter
I found I was able to do a clean install with out going the Factory reset route. It kept my XP boot loader. This issue is solved.
 
Last edited:

kemical

Windows Forum Admin
Staff member
Premium Supporter
As far as I'm aware you can only do this when creating the thread (which seems a little pointless) so I'm gonna ask Mike if he can make some changes.. I'm going use this thread as an example so hope you don't mind..:)
 

stueycaster

Millennium Celebration Award Winner
Premium Supporter
As far as I'm aware you can only do this when creating the thread (which seems a little pointless) so I'm gonna ask Mike if he can make some changes.. I'm going use this thread as an example so hope you don't mind..:)
Not at all Buddy.
 
Top