CHKDSK Recommended During Boot-Stopped-Checked Later Autorepair Off

[baumgrenze]

Recently Win7/Pro x64 has been recommending a chkdsk of my System Disk during the boot. I've used the 'any key to ignore' option and then run it once booted.

To do so I select "Start" then "Computer" and right click the System Drive and select "Properties" and then the tab "Tools" and select the "Check Now" option. This opens a dialog box "Check Disk Win 7 x64 System Disk (C" in which the "Automatically fix file system errors" is checked by default and I uncheck it I run this version of chkdsk and open "See details." I have attached an image of the report it generates.

Would CHKDSK find something different if I allowed "Automatically fix file system errors?"

thanks,
baumgrenze

 

[samuria]

It has to run at boot before windows loads as windows may lock files or maybe in use

 

[baumgrenze]

https://www.sevenforums.com/newreply.php?do=postreply&t=418985

Thank you, Samuria for your reply,

The CHKDSK message shows just after the "splash" image forms but before the Password Request is displayed, if that is a helpful clue.

Is there a technique for running this 'version' of CHKDSK and seeing what problems it uncovers without running the risk of the System Disk being rendered inoperable by the 'repairs' run by CHKDSK? The answer to this is not immediately apparent.

I did a surface scan of the SDD and it is clean, but I'm unclear on what 'surface' of a drive that is not a spinning disk is tested.

CrystalDiskInfo 8.0.0 reports it as "Good - 88%), having run 19,032 hours, 793 days, or 22.17 hours.

I only have 5 items checked in my Startup System Configuration:

Avast (2 instances but locations are different)
MS Windows
Java
MS Office

thanks,
baumgrenze

 

[Megahertz07]

Check disk didn't found any problems so there is no need for a fix.
If you want to do a check disk with the fix option:
Open a CMD window as admin and type:
chkdsk c: /f
It will say your disk is in use and if you what to schedule to next start=yes
Reboot

 

[baumgrenze]

Thanks, Megahertz07

I want to be able to 'control' the CHKDSK before Win7 fully loads and it appears to me that letting that happen during the loading process will allow the routine to do whatever it wants once it is started.

Is my memory of past experiences with this process faulty? In every case I've been taken unawares and if the option to pause and reflect is offered, I don't recall it.

Are there aspects of running CHDKSK before Win7 loads that are different than after? Your initial reply seems to say that.

The system seems to run fine without the proposed 'repair' during the boot sequence loading of Win7.

I'm trying to avoid having to reinstall Win7 and all my program files.

thanks
baumgrenze

 

[samuria]

If there are errors it fixes they need fixing if you don't fix then the files are corrupted anyway so may bring the system down

 

[Megahertz07]

Samuria, on the image on post #1 it says "Windows has checked the file system and found NO problems.

Baumgrenze, you can run check disk under Windows any time but to fix problems (chkdsk c: /f) it can't be done under Windows as the drive is in use. It must be on boot.

 

[samuria]

I know it said no errors but was trying to point out if there are errors not fixing them doesn't solve anything

 

[baumgrenze]

Samuria, thanks for being so patient.

I tried chkntfs C: at an elevated command prompt and got the reply below, so Win7 is 'upset' about something.

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Windows\system32>chkntfs C:
The type of the file system is NTFS.
C: is dirty. You may use the /C option to schedule chkdsk for this drive.

I've been trying to get my Mozilla profile back together so that all my mail files are where they belong in the email client in SeaMonkey as time permits. I hope that is what has it 'upset.'

I'll reboot soon and let it run its course.

thanks again,
baumgrenze

 

[baumgrenze]

It seems there is a Catch 22.


I snapped a digital image of the transient message during the boot. It is probably in a log file, too, no?



Windows will now check the disk.
Cannot open volume for direct access.
Autochk cannot run due to an error caused by a recently installed software package
Use the System Restore feature from the control panel to restore the system to a point prior to the recent software package installation.
An unspecified error occurred (766f6c756d652e63 3f1)



I have a System Restore point from 3/23/19 when Java 8 Update 201 8.0.2010.9 was installed. Unfortunately System Restore cannot restore. I have images but chose too transpose the text just now.



System Restore
The disk Win 7 x64 System Disk (C has errors.
Windows has detected file system corruption on Win 7 x64 System Disk (C. You must check the disk for errors before it can be restored.

Check the disk for errors. (underlined - a hyperlink to)
Windows can't check the disk while it's in use
Do you want to check the hard disk errors next time you start your computer?
The option "Schedule disk check" was selected.
On rebooting the same process occurred.


Is there a way around this Catch 22?


thanks,
baumgrenze

 

[Snick]

Have you tried pressing <ESC> or one of the F keys as you boot to enter menus?

On my desktop <F8> enters screen to choose safe mode, safe mode with networking, etc., and the one you should try: Start Computer with last known good configuration (advanced).

I had to boot and repeatedly press <F8> about every 1 second, to get to that screen. Sometimes my machine goes straight to loading windows and I have to try the process again.

 

[gemhunter]

...
Windows will now check the disk.
Cannot open volume for direct access.
Autochk cannot run due to an error caused by a recently installed software package
Use the System Restore feature from the control panel to restore the system to a point prior to the recent software package installation.
An unspecified error occurred (766f6c756d652e63 3f1)

I have a System Restore point from 3/23/19 when Java 8 Update 201 8.0.2010.9 was installed. Unfortunately System Restore cannot restore. I have images but chose too transpose the text just now.

System Restore
The disk Win 7 x64 System Disk (C has errors.
Windows has detected file system corruption on Win 7 x64 System Disk (C. You must check the disk for errors before it can be restored.
...

Is there a way around this Catch 22?

thanks,
baumgrenze

I had this exact problem and error message, and it took me a couple of weeks to figure out what was causing it. In my case, it was the Avast (free version) AV I was using on my Win7 Pro box. Somehow, even when completely disabled, Avast is locking something on the disk that prevents boot time chkdsk from running.

Before any attempt to fix it, I cloned the drive to an external drive, just in case something died.

What did fix it was completely uninstalling Avast, and making sure all remaining Avast files were deleted, as uninstall leaves a service behind called "Overseer". That's located in c:\Program Files\Common Files\Avast Software\, and I just deleted the Avast Software folder to remove.

Once the Avast gremlin was removed, boot time chkdsk worked fine.

This appears to have been caused by the latest version update of Avast, as I've been using it for years. Now that it's gone, I've install good ol MS Security Essentials.


Al McCann in Cape May, NJ

 

[baumgrenze]

Thank you, gemhunter

I did a bit searching on my own.

The most recent on the Avast forum as of this evening is

Impossible to execute Autochk on disc C: - error (766f6c756d652e63 3f1)

It says 'be patient, it is hard work to sort this out.'