How do I fix a corrupt file in Windows 7 that Scannow can't.

I have tried all Windows updates, checked for viruses, done everything within my power, but nothing seems to work. Whenever I open anything that requires Windows Explorer, it that program crashes. I can watch videos online, but not in Windows Media Player, Real Player or Quick Time. I cannot access "My Computer" because it tells me Windows has stopped working. I run the Command Prompt and do a Scannow, and when it comes to the report, it tells me it has stopped working and needs to close. It started when both Flash Player and Java started to malfunction, but I updated those and they work just fine on the internet. For some reason, I don't have any System Restore Points, so that is not an option. My CBS log file shows a couple of issues, but I am not a computer geek so have no idea if this is my problem, and if it is, what do I do to fix it?

POQ 128 ends.
2014-01-19 19:03:20, Info CSI 00000308 [SR] Verify complete
2014-01-19 19:03:20, Info CSI 00000309 [SR] Repairing 1 components
2014-01-19 19:03:20, Info CSI 0000030a [SR] Beginning Verify and Repair transaction
2014-01-19 19:03:20, Info CSI 0000030b Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-s..chrecognizerenu.ale_31bf3856ad364e35_6.1.7600.16385_en-us_2a26b846c28f1791\l1033.ngr do not match actual file [l:18{9}]"l1033.ngr" :
Found: {l:32 b:ngDe8JuZpX5yWU1Iz0x0TVkg0LVDb6kY4VImrIBhoQ8=} Expected: {l:32 b:wq7Nf8+TNyCEXeeVYi/bcRBnWJMnXxl0GdkrOvt94eI=}
2014-01-19 19:03:20, Info CSI 0000030c [SR] Cannot repair member file [l:18{9}]"l1033.ngr" of Microsoft-Windows-SpeechRecognizerENU.ale, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), 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-01-19 19:03:21, Info CSI 0000030d Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-s..chrecognizerenu.ale_31bf3856ad364e35_6.1.7600.16385_en-us_2a26b846c28f1791\l1033.ngr do not match actual file [l:18{9}]"l1033.ngr" :
Found: {l:32 b:ngDe8JuZpX5yWU1Iz0x0TVkg0LVDb6kY4VImrIBhoQ8=} Expected: {l:32 b:wq7Nf8+TNyCEXeeVYi/bcRBnWJMnXxl0GdkrOvt94eI=}
2014-01-19 19:03:21, Info CSI 0000030e [SR] Cannot repair member file [l:18{9}]"l1033.ngr" of Microsoft-Windows-SpeechRecognizerENU.ale, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), 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-01-19 19:03:21, Info CSI 0000030f [SR] This component was referenced by [l:288{144}]"Microsoft-Windows-Client-Features-Package~31bf3856ad364e35~amd64~en-US~6.1.7601.17514.Microsoft-Windows-SpeechRecognizer-Deployment-LanguagePack"
2014-01-19 19:03:22, Info CSI 00000310 Hashes for file member \??\C:\Windows\Speech\Engines\SR\en-US\l1033.ngr do not match actual file [l:18{9}]"l1033.ngr" :
Found: {l:32 b:ngDe8JuZpX5yWU1Iz0x0TVkg0LVDb6kY4VImrIBhoQ8=} Expected: {l:32 b:wq7Nf8+TNyCEXeeVYi/bcRBnWJMnXxl0GdkrOvt94eI=}
2014-01-19 19:03:22, Info CSI 00000311 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-s..chrecognizerenu.ale_31bf3856ad364e35_6.1.7600.16385_en-us_2a26b846c28f1791\l1033.ngr do not match actual file [l:18{9}]"l1033.ngr" :
Found: {l:32 b:ngDe8JuZpX5yWU1Iz0x0TVkg0LVDb6kY4VImrIBhoQ8=} Expected: {l:32 b:wq7Nf8+TNyCEXeeVYi/bcRBnWJMnXxl0GdkrOvt94eI=}
2014-01-19 19:03:22, Info CSI 00000312 [SR] Could not reproject corrupted file [ml:520{260},l:76{38}]"\??\C:\Windows\Speech\Engines\SR\en-US"\[l:18{9}]"l1033.ngr"; source file in store is also corrupted
2014-01-19 19:03:23, Info CSI 00000313 Repair results created:
POQ 129 starts:

Hello Piper52 and welcome to Seven Forums.

Try running the System File Checker scan at least three times as recommended in this tutorial (Option Two, Step 4, "Note".) Reboot the computer immediately following each scan. That might fix the damaged or corrupt files.

SFC /SCANNOW Command - System File Checker

If the problem persists you could follow the additional "Note" suggestions. If still no success you could try extracting a clean copy of the damaged/corrupt file(s) from a Windows 7 installation disk. The instructions are in the "Tip" box at the bottom of Option Three. Or, in the alternative, you could wait to see if one of the Forum experts can provide a specific fix for your computer. Personally, I'd go straight to a Repair Install.

Repair Install

If successful, the Repair Install should fix your currently installed Windows 7 and preserve your user accounts, data, programs, system drivers, etc. The third item in the "Warning" box explains how to obtain a legal Windows 7 installation disk should you need one.

I have already tried the Scannow option over seven times with no luck. I did read this tutorial earlier and tried what was suggested but do not have access to an installation disk as the computer came pre-loaded with Windows 7 and no disc. As I have already exhausted my other options, I will check the website to see if I can obtain a legal copy of the disc. Thanks so much for your help.

Thank you so much for your help! It worked and my corrupted files are fixed. The sfc /scannow entry shows no integrity issues and other than having to re-install 136 Windows updates, all is well. Thank you, thank you, thank you!

Glad to hear everything worked out for you. Thanks for posting back.

One additional suggestion if I may. When you get the Windows updates installed and your computer is working as it should, I'd make a System Image and save it to an external hard drive. You could use the native Windows 7 imaging tool or the free Macrium.

Backup Complete Computer - Create an Image Backup

Imaging with free Macrium

You could use the System Image to restore your computer to the exact condition it was in at the time the image was made. All Windows updates, all programs, all personal settings, etc will be restored in usually less than an hour. That's a lot faster than running a repair install and then waiting even longer for updates to download.