Win 7 Service Pack 1 installation fails - AND messes up drive letters!

I suspected that'd be the case with the drive letters - it implies that there may be a problem with your MBR.
SFC should take anywhere from 5 minutes (with an SSD) to an hour or so (slow machine)- an instantaneous completion is always a bad sign (which is why we always ask for the full CBS.log)

Here's the Summary output from SFC this time...

Code:

 Line 29820: 2014-09-29 11:21:56, Info                  CSI    000001d5 [SR] Repairing 9 components
 Line 29821: 2014-09-29 11:21:56, Info                  CSI    000001d6 [SR] Beginning Verify and Repair transaction
 Line 29824: 2014-09-29 11:21:57, Info                  CSI    000001d8 [SR] Cannot repair member file [l:24{12}]"M1033DSK.CSD" of Microsoft-Windows-MulanTTSVoiceENUDsk, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
 Line 29825: 2014-09-29 11:21:58, Info                  CSI    000001d9 [SR] Cannot repair member file [l:32{16}]"nete1g32.inf_loc" of nete1g32.inf.Resources, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
 Line 29826: 2014-09-29 11:21:58, Info                  CSI    000001da [SR] Cannot repair member file [l:32{16}]"netefe32.inf_loc" of netefe32.inf.Resources, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
 Line 29827: 2014-09-29 11:21:58, Info                  CSI    000001db [SR] Cannot repair member file [l:32{16}]"netevbdx.inf_loc" of netevbdx.inf.Resources, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
 Line 29828: 2014-09-29 11:21:58, Info                  CSI    000001dc [SR] Cannot repair member file [l:28{14}]"netgb6.inf_loc" of netgb6.inf.Resources, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
 Line 29829: 2014-09-29 11:21:58, Info                  CSI    000001dd [SR] Cannot repair member file [l:32{16}]"prnsv003.inf_loc" of prnsv003.inf.Resources, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
 Line 29830: 2014-09-29 11:21:58, Info                  CSI    000001de [SR] Cannot repair member file [l:32{16}]"prnrc002.inf_loc" of prnrc002.inf.Resources, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
 Line 29831: 2014-09-29 11:21:58, Info                  CSI    000001df [SR] Cannot repair member file [l:32{16}]"prnso002.inf_loc" of prnso002.inf.Resources, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
 Line 29832: 2014-09-29 11:21:58, Info                  CSI    000001e0 [SR] Cannot repair member file [l:32{16}]"prnsv004.inf_loc" of prnsv004.inf.Resources, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing

I'll post a fix protocol later - but it looks to me as if this is the same list as earlier (with 1 addition), at least at first glance.
If that's the case, then we may have a problem - there could be serious problems with the drive, or there may be a rootkit present.

Please run a full CHKDSK and see what it reports.

Click on Start > All Programs > Accessories
Right-click on the Command Prompt entry
Select Run as Administrator and accept the UAC prompt - the Elevated Command Prompt window should pop up.
At the Command prompt, type
CHKDSK C: /R
and hit the Enter key.
You will be told that the drive is locked, and the CHKDSK will run at the next boot - hit the Y key, and then reboot.
The CHKDSK will take a few hours depending on the size of the drive, so be patient!
After the CHKDSK has run, Windows should boot normally (possibly after a second auto-reboot)

Also, please run the Kaspersky TDSSKiller tool and see if that finds anything - TDSSKiller Free Download | Rootkit Remova | Kaspersky Lab US

Are you dual-booting with anything?

The listed files are the same

Please open an Elevated COmmand Prompt and run the following commands...

DIR C:\cndaa
DIR C:\Windows\cndaa
DIR C:\Windows\winsxs\cndaa

post the results.

That'll hopefully give us a clue...

please run the fix again - as below - and make notes of exactly what happens as you do it.
Once complete, post the new CBS.log and your notes

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:\cndaa
hit the enter key - if you get a 'Not Found' error try
DIR D:\cndaa
or
DIR E:\cndaa

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

XCOPY <drive>:\cndaa <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

Hmmm - here's the important bits from the summary of the SFC...

Code:

 Line 33817: 2014-10-02 10:08:01, Info                  CSI    000001bf [SR] Repairing 8 components
 Line 33818: 2014-10-02 10:08:01, Info                  CSI    000001c0 [SR] Beginning Verify and Repair transaction
 Line 33819: 2014-10-02 10:08:01, Info                  CSI    000001c1 [SR] Cannot verify component files for Macrovision-Protection, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral, manifest is damaged (FALSE)
 Line 33820: 2014-10-02 10:08:01, Info                  CSI    000001c2 [SR] Cannot verify component files for Macrovision-Protection-SafeDisc, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral, manifest is damaged (FALSE)
 Line 33823: 2014-10-02 10:08:02, Info                  CSI    000001c4 [SR] Cannot repair member file [l:24{12}]"M1033DSK.CSD" of Microsoft-Windows-MulanTTSVoiceENUDsk, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch

The fix appears to have done what it was supposed to do this time - but another error has appeared, which we'll have to use CheckSUR to fix, before we go back to fix the remaining file error.

Please run the CheckSUR tool again and post the new CheckSUR.log file,