Solved Windows 7 installation presumably corrupt - CBS.logs inside

[Herrasmies]

Hey,

This is my first post on this forum and as the title says my Windows 7 files might be broken, atleast according to CMD -> sfc /scannow.

Command prompt also asks me to refer to the CBS.logs for more information, but I can't comprehend any of the file's content.

Could someone help me out a bit?

 

[NoelDP]

Just the one error in SFC...

 Line 3035: 2015-04-04 16:48:28, Info                  CSI    000002b8 [SR] Repairing 1 components
 Line 3036: 2015-04-04 16:48:28, Info                  CSI    000002b9 [SR] Beginning Verify and Repair transaction
 Line 3039: 2015-04-04 16:48:28, Info                  CSI    000002bb [SR] Cannot repair member file [l:44{22}]"defaultlocationcpl.dll" of Microsoft-Windows-MobilePC-DefaultLocationPremium, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch

I'll post a fix protocol a little later.

 

[NoelDP]

I've uploaded a file - hssaa.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:\hssaa
hit the enter key - if you get a 'Not Found' error try
DIR D:\hssaa
or
DIR E:\hssaa



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



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

 

[Herrasmies]

Alright, so according to System File Check everything is A-okay!
But still here's the CBS you asked for.

My humblest thanks to you sir, but if I may ask what was that all about?

 

[NoelDP]

The original file was corrupted - possibly a RAM or HD problem, or malware - and the SFC scan you did found that.

It needed to be replaced with a good version but the backup copy in your system was also damaged so SFC was unable to do that.

We replaced the backup copy with a good version of the file, and that enabled SFC to fix the rest of the problem.

Everything looks good now.

Good luck!