Norton removed-NO chkdsk on restart

[Arc]

I finally removed and replaced Norton Internet Security, whereupon Windows 7 began reporting disk volume errors. Chkdsk reports errors, but is unable to fix them.

The HDD is Seagate Momentus 2.5" Notebook Hard Drive (5400.3 ST9160821AS 160GB 5400 RPM 8MB Cache SATA 1.5Gb/s).

I would suggest you to run Seatools For DOS. It offers a better disc check than the chkdsk utility. Also it has an inbuilt mechanism to attempt to recover the disc errors. Let it have a go.

 

[NoelDP]

That run of CHKDSK was only the minimal standard /F - you need to run the more testing /R which will find bad sectors if they exist, and attempt to fix or replace them

 

[paulyoungstrom]

Sorry. I've run chkdsk /r. The log is attached.

 

[NoelDP]

That was quick!

There don't seem to be any problems with the disk - but perhaps Arc's Seatools scan would be a good idea as well.

 

[paulyoungstrom]

I ran all the Basic tests in Seatools (including the fix tests) - all of them passed with no reported problems. I have also run SpinRite, which reported no problems.

Currently, chkdsk reports no problems, and Action center is no longer nagging me about disk volume errors. Chkdsk, run from an elevated command prompt, will schedule to run on reboot, but still does not do so. It will only run on reboot immediately after running pysaa.

I would also mention that, since removing Norton, the Action Center has been nagging me about installing updates. There are now 3 (kb2604121, kb2656405 and kb2737019), and I have tried repeatedly to install them, but the installation always fails. I don't know if this is part of the current problem, or the subject of another thread.

Regarding the chkdsk/reboot problem, in light of the current state of disk "health," would I be better off ignoring the reboot issue? This computer is running better than it has in a long time, without Norton.

 

[Arc]

Currently, chkdsk reports no problems, and Action center is no longer nagging me about disk volume errors.

Nice. Either of the tests must have fixed any possible disc error. And you need not be worried about the disc health right now.

I would also mention that, since removing Norton, the Action Center has been nagging me about installing updates. There are now 3 (kb2604121, kb2656405 and kb2737019), and I have tried repeatedly to install them, but the installation always fails. I don't know if this is part of the current problem, or the subject of another thread.

NoelDP is the best person to resolve this updates issue. Before he suggests you the specific steps applicable to your system, you may take a general step: http://www.sevenforums.com/tutorials/91738-windows-update-reset.html

Regarding the chkdsk/reboot problem, in light of the current state of disk "health," would I be better off ignoring the reboot issue? This computer is running better than it has in a long time, without Norton.

IMHO you can ignore it right now, but I will wait to see what Noel suggests in this regard.

 

[NoelDP]

I've uploaded a file - pysac.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 pysac in the same place.
Open this folder - there should be one folders 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.

 

[paulyoungstrom]

CheckSUR logs attached.

 

[paulyoungstrom]

I subsequently tried to install the updates again. The installation failed, with error code 66A.

 

[NoelDP]

The manifest replacements all worked OK - but the CheckSUR also showed these errors...

(f) CSI Payload File Missing 0x00000000 XpsRasterService.dll x86_microsoft-windows-c..nt-xpsrasterservice_31bf3856ad364e35_6.1.7600.20830_none_1b2e65b1a64e1e58 
(f) CSI Payload File Missing 0x00000000 XpsGdiConverter.dll x86_microsoft-windows-c..ent-xpsgdiconverter_31bf3856ad364e35_6.1.7600.16699_none_12bc029b4ca8d5bc 
(f) CSI Payload File Missing 0x00000000 timedate.cpl x86_microsoft-windows-timedate_31bf3856ad364e35_6.1.7600.21118_none_905ab33c3dffd1d4

We're getting there

I still don't like the idea that new errors keep coming up - but it could be simply that they are being exposed by the corrections that we are making to the system

I'll post a fix for these ones later.

 

[NoelDP]

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



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



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

 

[paulyoungstrom]

New CBS.log file attached. While I can't read it, and I correct in guessing that autocheck.exe is the only file it now reports as corrupted?

 

[NoelDP]

It's impossible to tell, using the file you posted.
We really need to see the whole CBS.log file - as I've repeatedly requested.


There appears also to still be a failed manifest file(!) - please completely follow the
Windows Update Posting Instructions
and post ALL the requested data - not extracts.
If the file is too large for the forum, delete the older CBSPersist logs - but I need the full CBS.log and CheckSUR.log files as a minimum.

 

[paulyoungstrom]

Sorry for the frustration - I misunderstood (thanks for the link explaining Log Collection). I hope the attached file is what you're looking for; please let me know if not.

 

[NoelDP]

's OK
Strange - the system reports that it cant't repair autochk at the start of the run - but says nothing at the end in the summary.

2014-03-20 16:10:03, Info                  CSI    0000004e [SR] Beginning Verify and Repair transaction
2014-03-20 16:10:11, Info                  CSI    0000004f Hashes for file member \SystemRoot\WinSxS\x86_microsoft-windows-autochk_31bf3856ad364e35_6.1.7601.17514_none_e3fb573520033bfa\autochk.exe do not match actual file [l:22{11}]"autochk.exe" :
  Found: {l:32 b:UNzc/WTucefrmZ+Zwlb8S/CQk8jZH4g2J3MSDCi//ag=} Expected: {l:32 b:LgNTZumhom+xXx5IVwVuateTK86Mxou0tlVgn0JNJ1Y=}
2014-03-20 16:10:11, Info                  CSI    00000050 [SR] Cannot repair member file [l:22{11}]"autochk.exe" of Microsoft-Windows-Autochk, Version = 6.1.7601.17514, 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-20 16:10:17, Info                  CSI    00000051 Hashes for file member \SystemRoot\WinSxS\x86_microsoft-windows-autochk_31bf3856ad364e35_6.1.7601.17514_none_e3fb573520033bfa\autochk.exe do not match actual file [l:22{11}]"autochk.exe" :
  Found: {l:32 b:UNzc/WTucefrmZ+Zwlb8S/CQk8jZH4g2J3MSDCi//ag=} Expected: {l:32 b:LgNTZumhom+xXx5IVwVuateTK86Mxou0tlVgn0JNJ1Y=}
2014-03-20 16:10:17, Info                  CSI    00000052 [SR] Cannot repair member file [l:22{11}]"autochk.exe" of Microsoft-Windows-Autochk, Version = 6.1.7601.17514, 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-20 16:10:17, Info                  CSI    00000053 [SR] This component was referenced by [l:198{99}]"Microsoft-Windows-Foundation-Package~31bf3856ad364e35~x86~~6.1.7601.17514.WindowsFoundationDelivery"
2014-03-20 16:10:17, Info                  CSI    00000054 Hashes for file member \??\C:\Windows\System32\autochk.exe do not match actual file [l:22{11}]"autochk.exe" :
  Found: {l:32 b:UNzc/WTucefrmZ+Zwlb8S/CQk8jZH4g2J3MSDCi//ag=} Expected: {l:32 b:LgNTZumhom+xXx5IVwVuateTK86Mxou0tlVgn0JNJ1Y=}
2014-03-20 16:10:17, Info                  CSI    00000055 Hashes for file member \SystemRoot\WinSxS\x86_microsoft-windows-autochk_31bf3856ad364e35_6.1.7601.17514_none_e3fb573520033bfa\autochk.exe do not match actual file [l:22{11}]"autochk.exe" :
  Found: {l:32 b:UNzc/WTucefrmZ+Zwlb8S/CQk8jZH4g2J3MSDCi//ag=} Expected: {l:32 b:LgNTZumhom+xXx5IVwVuateTK86Mxou0tlVgn0JNJ1Y=}
2014-03-20 16:10:17, Info                  CSI    00000056 [SR] Could not reproject corrupted file [ml:520{260},l:46{23}]"\??\C:\Windows\System32"\[l:22{11}]"autochk.exe"; source file in store is also corrupted
2014-03-20 16:10:18, Info                  CSI    00000057 Repair results created:

from the summary...

2014-03-20 16:26:22, Info                  CSI    000001c8 [SR] Repairing 1 components
2014-03-20 16:26:22, Info                  CSI    000001c9 [SR] Beginning Verify and Repair transaction
2014-03-20 16:26:23, Info                  CSI    000001ca Repair results created:
POQ 88 starts:
 
POQ 88 ends.
2014-03-20 16:26:23, Info                  CSI    000001cb [SR] Repair complete

This is not normal! - but I have no idea why it would happen.

I'll check the file again later - in the meantime, please run CheckSUR again, and post the new CheckSUR.log file

 

[paulyoungstrom]

I ran CheckSUR again. Updated CBS log folder attached.

 

[NoelDP]

That's clear, at least

OK - I'll post a fix for the autochk file a bit later. Hopefully after that, everything should work properly

 

[NoelDP]

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



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



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