New
#11
Similar result
Thanks again.
In a depressing manner, a familiar tale of found corrupt file and unable to fix.
zip pf CBS.log attached.
Sorry this is dragging on.
Thanks again.
In a depressing manner, a familiar tale of found corrupt file and unable to fix.
zip pf CBS.log attached.
Sorry this is dragging on.
Not a problem - only one file found now...
Sometimes we get a domino effect like this - but sometimes this is caused by bad hardware, such as RAM or HD, and sometimes by malware.Code:17968: 2014-10-12 08:30:31, Info CSI 000001dd [SR] Repairing 3 components Line 17969: 2014-10-12 08:30:31, Info CSI 000001de [SR] Beginning Verify and Repair transaction Line 17974: 2014-10-12 08:30:41, Info CSI 000001e1 [SR] Could not reproject corrupted file [ml:520{260},l:46{23}]"\??\C:\Windows\System32"\[l:30{15}]"NlsData004e.dll"; source file in store is also corrupted Line 17983: 2014-10-12 08:30:45, Info CSI 000001e3 [SR] Repair complete
This doesn't look like malware or an HD problem to me - so perhaps a RAM test is in order....
RAM - Test with Memtest86+
Run at least 3 full passes - although some recommend 8, I don't really believe assertions that this is necessary in every case.
Thanks again for sticking with me - on a Sunday, too! :)
OK, still running Memtest86+, but after 3 passes, no errors flagged up.
For info, there are 2x1GB sticks, scan 1 was 18 minutes, 2 & 3 were 51 mins apiece.
Shall I continue - or can you suggest other moves?
I don't think there's anything to be gained by leaving it longer.
I have to go out now - I'll post a fix when I get back (if I'm in a fit state! )
When I picked up your reply, I found it was about to complete the 9th pass anyway - with no errors.
The timings were consistent with 50 minutes each.
Only one odd thing - on normal bootup, it advised me that Windows Firewall had blocked the "Ditto" program.
I left it blocked, but I don't remember it being flagged up before.
Will await your reply - and hope you had a good time out.
Very good
Definitely stop it now - it's not going to catch anything it hasn't already found.
I'll post a fix for the file problems when I can see straight
I've uploaded a file - wgbad.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:\wgbad
hit the enter key - if you get a 'Not Found' error try
DIR D:\wgbad
or
DIR E:\wgbad
The drive letter in use when you find the folder will need to be substituted (for<drive>) into the following command...
XCOPY <drive>:\wgbad <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
Apologies for delay - it's been a busy two days (relatives visiting etc)
Went through process & have full CBS.log.zip, but looking at the previous, this fragment may say it all:
Code:2014-10-14 14:35:17, Info CSI 000000d6 [SR] Beginning Verify and Repair transaction 2014-10-14 14:35:18, Info CSI 000000d7 Hashes for file member \??\C:\Windows\System32\C_20949.NLS do not match actual file [l:22{11}]"C_20949.NLS" : Found: {l:32 b:1v8C0NQHVkdS2Nj3TAX2SAOdBDvFnEIAWDkZG2f4CZ8=} Expected: {l:32 b:eK+SZzkDJgeTodH1ssQRsjk+W+KMBTnfSBH6BD7ugqo=} 2014-10-14 14:35:18, Info CSI 000000d8 Hashes for file member \SystemRoot\WinSxS\x86_microsoft-windows-i..onal-codepage-20949_31bf3856ad364e35_6.1.7600.16385_none_52de33df47065121\C_20949.NLS do not match actual file [l:22{11}]"C_20949.NLS" : Found: {l:32 b:1v8C0NQHVkdS2Nj3TAX2SAOdBDvFnEIAWDkZG2f4CZ8=} Expected: {l:32 b:eK+SZzkDJgeTodH1ssQRsjk+W+KMBTnfSBH6BD7ugqo=} 2014-10-14 14:35:18, Info CSI 000000d9 [SR] Could not reproject corrupted file [ml:520{260},l:46{23}]"\??\C:\Windows\System32"\[l:22{11}]"C_20949.NLS"; source file in store is also corrupted
OK, here's the full log