Not able to start windows firewall

I suspect that you have more problems than just these file errors - but we'll work on them first as we have the data to hand...

Code:

2014-08-21 23:23:56, Info                  CSI    000001f4 [SR] Repairing 4 components
2014-08-21 23:23:56, Info                  CSI    000001f5 [SR] Beginning Verify and Repair transaction
2014-08-21 23:23:56, Info                  CSI    000001f6 [SR] Cannot verify component files for 640caf3bd1f82b7746e522a21a8e8799, Version = 6.1.7601.18275, 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)
2014-08-21 23:23:56, Info                  CSI    000001f7 [SR] Cannot repair member file [l:24{12}]"hidclass.sys" of input.inf, Version = 6.1.7601.18199, 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
2014-08-21 23:23:57, Info                  CSI    000001f9 [SR] Cannot repair member file [l:38{19}]"DiagPackage.dll.mui" of Microsoft-Windows-MaintenanceDiagnostic.Resources, Version = 6.1.7601.17514, 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, hash mismatch
2014-08-21 23:23:57, Info                  CSI    000001fa [SR] Cannot repair member file [l:22{11}]"usbscan.sys" of sti.inf, Version = 6.1.7601.18199, 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

I'll post a fix later today.

While I hunt down the needed files for the SFC fix,


Please download and save the CheckSUR tool from http://support.microsoft.com/kb/947821
(you'll need to look in the details for Windows 7, downloading from the Microsoft Download Center)

Run it - The tool can take anywhere from 5 mins to a couple of hours to run (or 'Install') depending on how much it has to do, and may exit silently - it may appear to freeze for most of that time, but be patient.
The result is logged in the C:\Windows\Logs\CBS\CheckSUR.log file - and an archive …\checksur.persist.log file

Then zip the CheckSUR.log and upload it to your reply.

The CheckSUR scan found a number of new errors, and fixed all except one..

Code:

Unavailable repair files:
 winsxs\manifests\msil_system.transactions.resources_b77a5c561934e089_6.1.7601.22617_en-us_f7e397befe7512f7.manifest

It also spotted the same errors as the SFC scan (and gave me better ID information) -

Here's the first part of the fix...



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



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



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

...and here's the second part...


I've uploaded a file - vtiab.zip - to my OneDrive at Noel's OneDrive
Please download and save it.
Right-click on the downloaded file, and select Extract all…
Extract to the default location - which will create a new folder vtiab in the same place.
Open this folder - there should be one folder inside it (Manifests)

Copy the content of the manifests folder (.manifest files) into this folder:

C:\Windows\Temp\CheckSur\Winsxs\Manifests

Now run the CheckSUR tool again (it may take a while)

Post the new CheckSUR.log file, and the CheckSUR.persist.log file.