J
Jwhitmor
I am having intermittent problems with Windows 7 sp1 32 bit stopping during the splash screen. I have run the startup repair many times and it never finds anything, or changes anything, unless of course I allow it do a system restore. It does not matter if I do a repair, a restore, or nothing at all, after several tries Windows 7 will successfully start up. Then my Acer Aspire laptop will function normally until I shut it down.
I did a sfc /scannow, and it completed with a message that it had found corrupt files it could not repair. See the log file.
Next, I was advised to install, Windows6.1-KB947821-v32-x86.msu hotfix, which I did, and it completed successfully
The next sfc /scannow ended up exactly as before so I decided to check the log entries associated with the corrupt files and found this:
2014-03-28 12:39:00, Info CSI 0000037c [SR] Cannot repair member file [l:30{15}]"WatAdminSvc.exe" of Microsoft-Windows-Security-WindowsActivationTechnologies, Version = 7.1.7600.16395, 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
2014-03-28 12:39:00, Info CSI 0000037e [SR] Cannot repair member file [l:30{15}]"WatAdminSvc.exe" of Microsoft-Windows-Security-WindowsActivationTechnologies, Version = 7.1.7600.16395, 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
2014-03-28 12:39:00, Info CSI 0000037f [SR] This component was referenced by [l:220{110}]"Microsoft-Windows-Security-WindowsActivationTechnologies-Package~31bf3856ad364e35~x86~~7.1.7600.16395.KB971033"
2014-03-28 12:39:00, Info CSI 00000381 [SR] Repair complete
2014-03-28 12:39:00, Info CSI 00000382 [SR] Committing transaction
2014-03-28 12:39:00, Info CSI 00000386 [SR] Verify and Repair Transaction completed. All files and registry keys listed in this transaction have been successfully repaired
This copy of Windows 7 came from a legitimate trusted source, and it activated successfully after it was installed, so I do not believe it is a pirated or modified
copy. Obviously anything that tampers with "WatAdminSvc.exe" concerns me. I am running the current malicious software removal tool, and , Microsoft Security Essentials with up to date signatures. I also ran an external virus scanner from a highly respected anti-virus / anti-malware company, which found no problems.
It looks to me, like the last line of the log says, that everything was repaired, so why did sfc /scannow report that it could not repair the corrupt files?
Continue reading...
I did a sfc /scannow, and it completed with a message that it had found corrupt files it could not repair. See the log file.
Next, I was advised to install, Windows6.1-KB947821-v32-x86.msu hotfix, which I did, and it completed successfully
The next sfc /scannow ended up exactly as before so I decided to check the log entries associated with the corrupt files and found this:
2014-03-28 12:39:00, Info CSI 0000037c [SR] Cannot repair member file [l:30{15}]"WatAdminSvc.exe" of Microsoft-Windows-Security-WindowsActivationTechnologies, Version = 7.1.7600.16395, 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
2014-03-28 12:39:00, Info CSI 0000037e [SR] Cannot repair member file [l:30{15}]"WatAdminSvc.exe" of Microsoft-Windows-Security-WindowsActivationTechnologies, Version = 7.1.7600.16395, 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
2014-03-28 12:39:00, Info CSI 0000037f [SR] This component was referenced by [l:220{110}]"Microsoft-Windows-Security-WindowsActivationTechnologies-Package~31bf3856ad364e35~x86~~7.1.7600.16395.KB971033"
2014-03-28 12:39:00, Info CSI 00000381 [SR] Repair complete
2014-03-28 12:39:00, Info CSI 00000382 [SR] Committing transaction
2014-03-28 12:39:00, Info CSI 00000386 [SR] Verify and Repair Transaction completed. All files and registry keys listed in this transaction have been successfully repaired
This copy of Windows 7 came from a legitimate trusted source, and it activated successfully after it was installed, so I do not believe it is a pirated or modified
copy. Obviously anything that tampers with "WatAdminSvc.exe" concerns me. I am running the current malicious software removal tool, and , Microsoft Security Essentials with up to date signatures. I also ran an external virus scanner from a highly respected anti-virus / anti-malware company, which found no problems.
It looks to me, like the last line of the log says, that everything was repaired, so why did sfc /scannow report that it could not repair the corrupt files?
Continue reading...
