Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: Norton removed-NO chkdsk on restart

20 Mar 2014   #31

Microsoft Community Contributor Award Recipient

Win 7 x64 Home Premium (and x86 VirtualBox VM)
 
 

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

My System SpecsSystem Spec
.

20 Mar 2014   #32

windows 7 32 bit
 
 

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?


Attached Files
File Type: txt sfcdetails.txt (133.1 KB, 1 views)
My System SpecsSystem Spec
20 Mar 2014   #33

Microsoft Community Contributor Award Recipient

Win 7 x64 Home Premium (and x86 VirtualBox VM)
 
 

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.
My System SpecsSystem Spec
.


20 Mar 2014   #34

windows 7 32 bit
 
 

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.


Attached Files
File Type: zip CBS.zip (4.87 MB, 1 views)
My System SpecsSystem Spec
21 Mar 2014   #35

Microsoft Community Contributor Award Recipient

Win 7 x64 Home Premium (and x86 VirtualBox VM)
 
 

'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.
Code:
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...
Code:
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
My System SpecsSystem Spec
21 Mar 2014   #36

windows 7 32 bit
 
 

I ran CheckSUR again. Updated CBS log folder attached.


Attached Files
File Type: zip CBS.zip (4.87 MB, 2 views)
My System SpecsSystem Spec
21 Mar 2014   #37

Microsoft Community Contributor Award Recipient

Win 7 x64 Home Premium (and x86 VirtualBox VM)
 
 

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
My System SpecsSystem Spec
22 Mar 2014   #38

Microsoft Community Contributor Award Recipient

Win 7 x64 Home Premium (and x86 VirtualBox VM)
 
 

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
My System SpecsSystem Spec
Reply

 Norton removed-NO chkdsk on restart




Thread Tools



Similar help and support threads for2: Norton removed-NO chkdsk on restart
Thread Forum
CHKDSK cancelled at restart message: Performance & Maintenance
BSOD on restart, no startup after unless battery removed BSOD Help and Support
Windows 7 won't boot up after Norton removed virus General Discussion
How do you know when chkdsk /r is done from a restart? Performance & Maintenance
Chkdsk runs everytime I restart Performance & Maintenance

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 04:52 AM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33