New
#11
axe0
Thanks, I was having a hard time finding it.
cork
axe0
Thanks, I was having a hard time finding it.
cork
axe0
I haven't heard back on this yet.
I do have my original Windows 7 disk. Would it be worth trying to do a system repair with it?
Thanks,
cork
Yes, it certainly would be worth it.
It is unlikely that your Windows 7 disk would contain corruption/is corrupted.
Thanks axe0
With my workload today it might be a bit before I can get back with you.
I'll do a repair and then run the sfc/scannow a couple of times and see what it says.
appreciate the help.
There's two errors in the SFC scan that need attention - I don't think either are serious in themselves, but one may indicate more severe problems elsewhere...
Please download and save the CheckSUR tool from http://support.microsoft.com/kb/947821Code:Line 21120: 2015-10-19 15:37:57, Info CSI 0000035a [SR] Repairing 2 components Line 21121: 2015-10-19 15:37:57, Info CSI 0000035b [SR] Beginning Verify and Repair transaction Line 21122: 2015-10-19 15:37:57, Info CSI 0000035c [SR] Cannot verify component files for Microsoft-Windows-International-Keyboard-00010480, 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, manifest is damaged (FALSE) Line 21125: 2015-10-19 15:37:57, Info CSI 0000035e [SR] Cannot repair member file [l:22{11}]"sidebar.exe" of Microsoft-Windows-Sidebar, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_IA32_ON_WIN64 (10), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch Line 21134: 2015-10-19 15:37:58, Info CSI 00000360 [SR] Repair complete
(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.
NoelDP,
Here is the CheckSUR file
Thank you,
cork
There's the summary from the CheckSUR log - not as bad as I was expecting (and it managed to fix the one from the SFC scan as well).
I'll post a fix for this laterCode:Summary: Seconds executed: 1164 Found 2 errors Fixed 1 errors CSI Manifest Missing Total count: 1 Fixed: CSI Manifest Missing. Total count: 1 CSI Manifest Failed Catalog Check Total count: 1 Unavailable repair files: winsxs\manifests\amd64_microsoft-windows-mediaplayer-core_31bf3856ad364e35_6.1.7601.23041_none_69f5bbc37ef22fc6.manifest
NoelDP,
That's good to hear. I appreciate all the time axe0 and you have put into this.
I don't know how these files became corrupted/damaged, or whatever the proper term is. Anything I should do in the way of preventative maintenance I should do?
Thanks,
Cork
This is what I would call corruption
It could occur by a buggy update or malware, likely some other ways too but I wouldn't know them.
To prevent these problems, I always run sfc/scannow after a Windows Update has been installed.