Win 7 unable to install SP1, CSI Payload File Missing

[jwhartwell]

Some time ago, Noel had a remarkable record for finding missing files. I wonder if he could do it again.
I have inherited this machine from a recently deceased friend. I think it came with Vista, and he installed Win 7 a long time ago. I'd like to keep it, but it needs SP1 to be eligible for Win 10, and that installation fails for lack of several files. Here's the list from CheckSUR.log:
Checking Component Store
(f) CSI Payload File Missing 0x00000000 sffdisk.inf amd64_sffdisk.inf_31bf3856ad364e35_6.1.7600.16438_none_00698d0a036fb7e7
(f) CSI Payload File Missing 0x00000000 sffp_sd.sys amd64_sffdisk.inf_31bf3856ad364e35_6.1.7600.16438_none_00698d0a036fb7e7
(f) CSI Payload File Missing 0x00000000 sdbus.sys amd64_sdbus.inf_31bf3856ad364e35_6.1.7600.16438_none_ce10c0cae3dcd5f8
(f) CSI Payload File Missing 0x00000000 sdbus.inf amd64_sdbus.inf_31bf3856ad364e35_6.1.7600.16438_none_ce10c0cae3dcd5f8
(f) CSI Payload File Missing 0x00000000 sffdisk.inf amd64_sffdisk.inf_31bf3856ad364e35_6.1.7600.20546_none_00e659551c9740f4
(f) CSI Payload File Missing 0x00000000 sffp_sd.sys amd64_sffdisk.inf_31bf3856ad364e35_6.1.7600.20546_none_00e659551c9740f4
(f) CSI Payload File Missing 0x00000000 sdbus.sys amd64_sdbus.inf_31bf3856ad364e35_6.1.7600.20546_none_ce8d8d15fd045f05
(f) CSI Payload File Missing 0x00000000 sdbus.inf amd64_sdbus.inf_31bf3856ad364e35_6.1.7600.20546_none_ce8d8d15fd045f05

As I read this, sdbus is listed twice, so three pairs of files (.inf & .sys) are needed to move forward.
Best regards,
John H.

 

[NoelDP]

We need ALL the data please...

Please follow the Windows Update Posting Instructions and post the requested data

If the file is too large (8MB compressed), remove the older CBSPersist cab files until the final file is below the limit - you can always post them separately after zipping them. (the forum doesn't allow the upload of bare CAB files, for a number of reasons)

Please also post the C:\Windows\windowsudpate.log file

 

[jwhartwell]

Uploaded logs

Thank you. Here are the (zipped) log files. I also ran sfc and included its CBS.log.

I can't approach this machine without thinking of Curtis. He was a biochemist at the Univ. of North Carolina who died from ALS. Quite a remarkable fellow... a black boy from Alabama with the mind of a scientist and the temperament of a saint.

 

[NoelDP]

SFC shows only these errors...

2015-09-10 20:09:22, Info                  CSI    00000313 [SR] Repairing 2 components
2015-09-10 20:09:22, Info                  CSI    00000314 [SR] Beginning Verify and Repair transaction
2015-09-10 20:09:22, Info                  CSI    00000315 [SR] Cannot repair member file [l:18{9}]"sdbus.sys" of sdbus.inf, Version = 6.1.7600.16438, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), 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
2015-09-10 20:09:22, Info                  CSI    00000316 [SR] Cannot repair member file [l:18{9}]"sdbus.inf" of sdbus.inf, Version = 6.1.7600.16438, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), 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
2015-09-10 20:09:22, Info                  CSI    00000317 [SR] Cannot repair member file [l:22{11}]"sffdisk.inf" of sffdisk.inf, Version = 6.1.7600.16438, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), 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
2015-09-10 20:09:22, Info                  CSI    00000318 [SR] Cannot repair member file [l:22{11}]"sffp_sd.sys" of sffdisk.inf, Version = 6.1.7600.16438, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), 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

While CheckSUR shows these....

Checking Component Store
(f)	CSI Payload File Missing	0x00000000	sffdisk.inf	amd64_sffdisk.inf_31bf3856ad364e35_6.1.7600.16438_none_00698d0a036fb7e7	
(f)	CSI Payload File Missing	0x00000000	sffp_sd.sys	amd64_sffdisk.inf_31bf3856ad364e35_6.1.7600.16438_none_00698d0a036fb7e7	
(f)	CSI Payload File Missing	0x00000000	sdbus.sys	amd64_sdbus.inf_31bf3856ad364e35_6.1.7600.16438_none_ce10c0cae3dcd5f8	
(f)	CSI Payload File Missing	0x00000000	sdbus.inf	amd64_sdbus.inf_31bf3856ad364e35_6.1.7600.16438_none_ce10c0cae3dcd5f8	
(f)	CSI Payload File Missing	0x00000000	sffdisk.inf	amd64_sffdisk.inf_31bf3856ad364e35_6.1.7600.20546_none_00e659551c9740f4	
(f)	CSI Payload File Missing	0x00000000	sffp_sd.sys	amd64_sffdisk.inf_31bf3856ad364e35_6.1.7600.20546_none_00e659551c9740f4	
(f)	CSI Payload File Missing	0x00000000	sdbus.sys	amd64_sdbus.inf_31bf3856ad364e35_6.1.7600.20546_none_ce8d8d15fd045f05	
(f)	CSI Payload File Missing	0x00000000	sdbus.inf	amd64_sdbus.inf_31bf3856ad364e35_6.1.7600.20546_none_ce8d8d15fd045f05

I'll post a fix protocol for the full list later.

 

[NoelDP]

I've uploaded a file - jwhaa.zip - to my OneDrive at Noel's OneDrive
Please download and save it.

Right-click on the saved file and select Extract all...
Change the target to C:\ and click on Extract
Close all windows (it would be a good idea to print these instructions!)

Now reboot to the Repair Environment - as soon as the machine restarts, start tapping F8 - this should bring up the Advanced Boot Menu, at the top of which should be the option 'Repair my Computer'
Pick that
You'll have to log in with your username and password.

Pick the option to use a Command Prompt
At the prompt type
DIR C:\jwhaa
hit the enter key - if you get a 'Not Found' error try
DIR D:\jwhaa
or
DIR E:\jwhaa

The drive letter in use when you find the folder will need to be substituted (for<drive>) into the following command...

XCOPY <drive>:\jwhaa <drive>:\windows\winsxs /y /i /s /v /h

(e.g. XCOPY P:\wfire P:\windows\winsxs /y /i /s /v /h )

run the command (it should take almost no time) and when the prompt returns, type
EXIT
and hit the Enter key to exit Command Prompt - reboot to Normal Mode Windows.

Now run SFC /SCANNOW in an Elevated Command Prompt
then reboot and upload the new CBS.log file to your reply

 

[jwhartwell]

new CBS.log

You are a fast worker, my man!
sfc reported to the screen that it found some corrupt files but was unable to fix all of them.

 

[NoelDP]

That doesn't appear to have worked
This usually means that the files ended up in the wrong place, so let's check the obvious ....
Open an Elevated COmmand Prompt, and run the following commands...

DIR C:\jwhaa
DIR C:\Windows\winsxs\jwhaa

post the results...

Here are some instructions to make life easier
1) To open an Elevated Command Prompt Window (the ECP window), click on Start, All Programs, Accessories – then right-click on Command Prompt, and select Run as Administrator. Accept the UAC prompt.
2) To run the commands easier, highlight the block of commands, and right-click on the highlight – select Copy. In the CP Window, click on the black/white icon at top left – select Paste. The commands will run but may not complete the last command, so hit the Enter Key once.
3) To copy the results... click on the Black/White icon in the top left, and select Edit... 'Select All', and hit the Enter key - then use Ctrl+V or r-click+Paste to paste it into your response.

 

[jwhartwell]

directories

Hmmm... Probably I messed this up. Inside the folder jwhaa is another folder jwhaa, and inside that are the four directories of interest to Windows.

Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Administrator>dir c:\jwhaa
Volume in drive C has no label.
Volume Serial Number is 1C66-0418

Directory of c:\jwhaa

09/11/2015 02:40 PM <DIR> .
09/11/2015 02:40 PM <DIR> ..
09/11/2015 02:40 PM <DIR> jwhaa
0 File(s) 0 bytes
3 Dir(s) 238,081,855,488 bytes free

C:\Users\Administrator>dir c:\jwhaa\jwhaa
Volume in drive C has no label.
Volume Serial Number is 1C66-0418

Directory of c:\jwhaa\jwhaa

09/11/2015 02:40 PM <DIR> .
09/11/2015 02:40 PM <DIR> ..
09/11/2015 02:40 PM <DIR> amd64_sdbus.inf_31bf3856ad364e35_6.1.7600
.16438_none_ce10c0cae3dcd5f8
09/11/2015 02:40 PM <DIR> amd64_sdbus.inf_31bf3856ad364e35_6.1.7600
.20546_none_ce8d8d15fd045f05
09/11/2015 02:40 PM <DIR> amd64_sffdisk.inf_31bf3856ad364e35_6.1.76
00.16438_none_00698d0a036fb7e7
09/11/2015 02:40 PM <DIR> amd64_sffdisk.inf_31bf3856ad364e35_6.1.76
00.20546_none_00e659551c9740f4
0 File(s) 0 bytes
6 Dir(s) 238,081,331,200 bytes free

C:\Users\Administrator>

The same structure appears in c:\windows\winsxs. That directory shows two files and fifteen thousand directories, one of which is the inner jwhaa as xcopied from c:\.

 

[NoelDP]

At a guess you used WinRAR to extract the files?

Please delete the C:\jhwaa folder and extract the files again so that you only get the base folder and contained winsxs folders, rather than the two layers of jwhaa folders, then repeat the copy process.

 

[jwhartwell]

CBS.log again

No, I remember WinRAR, but Win 7 seemed to be able to unzip as a native function. I think I just didn't look at the screen with sufficient suspicion.

I did move the expanded files up one directory level in C:\jwhaa and then XCOPY'd them again. I don't believe the graft has yet taken, though. The poor box continues to install updates every time it shuts down (about 120 of them since we started this work a couple of days back). SP1 is often attempted, as it was again just now. The configuration failed as it has before.

I was a little troubled to leave the trash \windows\winsxs\jwhaa, but when I tried to delete it, I found I needed permission from SYSTEM. Perhaps there is no harm in letting it sit there.

I am grateful for your attention. My name is John. Is your name Paul?

 

[NoelDP]

please post a new set of DIR results - the full set this time, so I can see all the results.
...and the CheckSUR.log file

 

[jwhartwell]

logs and directories

Jeesh! You are a patient fellow!
The updates continue to pour in, so I have included that log as well.
Best, John H.

 

[NoelDP]

CheckSUR is clear
The files in the winsxs folder have been replaced, apparently
Please run SFC /SCANNOW again - if it comes back with the same errors, then please post the COMPONENTS registry hive...

I need to have a look at your COMPONENTS registry hive

Please copy the C:\Windows\System32\config\COMPONENTS file (no extension) to your desktop and then compress it - upload the compressed file to your favoured fileshare site (preferably Dropbox or OneDrive) and post a link.

 

[jwhartwell]

COMPONENTS & fresh CBS

Had a hard time copying COMPONENTS. Got message saying it was open by SYSTEM. Finally booted to "repair my computer" and was able to copy it. Here's the .ZIP of it and CBS.log.
https://www.dropbox.com/s/wf4bk5l4v3s1r6e/CBS+COMPONENTS.zip?dl=0

sfc seems not to have found any problems:
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Administrator>sfc /scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.

C:\Users\Administrator>

Thanks for your persistence!

 

[NoelDP]

Bad new, I'm afraid...
This machine appears to have started life with the Preview version of Windows 7 - and part of it is still stuck there
The COMPOENTS hive is missing a LOT of information.

Your only options are either
1) a Repair install
2) a reformat/reinstall.

 

[jwhartwell]

I am saddened by this news, of course, but I am glad to get to the bottom of it.
Thank you for all your attention.
John H.

 

[jwhartwell]

Do you think I would have any luck copying a COMPONENTS file from some other machine?