Windows 7 Professonal 32-bit checkdisk questions

[ZemplinTemplar]

Hello, good people of the AskWoody forums.

I’d like to ask some questions regarding Windows 7 and Checkdisk.

During normal evening work, I seem to have inadvertently pressed some shortcuts that sent my computer to sleep. Unluckily, I was forced to shut off its power, because I couldn’t bring it back from that state. Windows started up normally, but it did something it hasn’t done in a longer while, run Checkdisk. As much as I wouldn’t have minded to have it run, I decided to skip it this time, then run it properly from the desktop.

The desktop and everything is fine, but when I opened the cmd (command) prompt, running it on Administrator privileges, wrote chkdsk and added enter, I had the following results.

The found errors concern me a little less than the fact that I get that “read-only” related error and can’t continue. Any genuine advice on how to overcome that and finish the whole checkup ?

Thanks in advance for any good advice.

• This topic was modified 2 weeks, 5 days ago by ZemplinTemplar.
• This topic was modified 2 weeks, 5 days ago by PKCano.
• This topic was modified 2 weeks, 5 days ago by ZemplinTemplar. Reason: typo

Attachments:

You must be logged in to access attached files.

Reply | Quote

[PKCano]

In an elevated Command prompt, try running chkdsk /f
You will have to agree to the reboot – reboot the computer and it will run on startup.

If that doesn’t run, there are a couple of things you can try:
+ Start the computer and boot into Safe Mode, then reboot into normal mode.
+ Run sfc /scannow and see if it finds and repairs any System files.

Reply | Quote

[ZemplinTemplar]

Thank you for the prompt answer !

It probably won’t matter if I run sfc /sccanow, will it ? Its purpose is different than that of Checkdisk.

Is there a chance that next time I boot up the computer, it might rerun Checkdisk independently for me ? I’ve had that happen a few times in the past, including this most recent instance with the sending-to-sleep mishap and turning the power off.

The trouble with rebooting my computer is that it tends to get stuck on reboot. Whenever I needed to do a reboot (due to WU or antivirus updates, or other reasons), I simply turned off all running programmes and apps (including cmd.exe) and then turned off the computer normally through the Start menu, then turned it back on after a while.

Would that method of rebooting be acceptable, or is it technically impossible to avoid agreeing with an automatic reboot if I run it as chkdsk /f ?

Reply | Quote

[Bob99]

With the chkdsk /F command entered at the command prompt, immediately after you enter it, you will see a statement to the effect that chkdsk can’t run with the /f parameter unless it has exclusive access to the disk. It will then ask you if you’d like it to run upon the next reboot. If you don’t want to run it, all you have to do is answer the question with an “n”, signifying no. Chkdsk will then not run on the next reboot.

If you answer the question with a “y”, signifying yes, chkdsk will then begin running the very next time the computer reboots. HOWEVER, upon the computer’s next reboot, it will put up a screen saying that it is scheduled to run and if you want to abort its’ running, just press any key on the keyboard within ten seconds, and it will show a countdown of the ten seconds.

Reply | Quote

[Paul T]

ZemplinTemplar wrote:

Would that method of rebooting be acceptable

Any method of rebooting is acceptable to Windows.
Chkdsk needs to be run before any other programs, that is why it happens at startup.

cheers, Paul

Reply | Quote

[GoneToPlaid]

ZemplinTemplar wrote:

The trouble with rebooting my computer is that it tends to get stuck on reboot. Whenever I needed to do a reboot (due to WU or antivirus updates, or other reasons), I simply turned off all running programmes and apps (including cmd.exe) and then turned off the computer normally through the Start menu, then turned it back on after a while.

After you have scheduled chkdsk /f, you can instead choose to shut down the computer and then booting up later. I prefer this method for checking the OS hard drive:

1. In Explorer, right-click on drive c: and then click on Properties.
2. Click on the Tools tab and then click on the Check now… button.
3. A small popup window will appear. Click on the Start button.
4. You will see a message that Windows can’t check the disk while it’s in use. Click on the Schedule disk check button.
5. Shut down or reboot your computer when it is convenient for you to do so. Chkdsk will automatically run when you either reboot or start up your computer

That is all there is to it.

Reply | Quote

[geekdom]

sfc /scannow repairs what’s wrong with your operating system files. It you are having trouble booting, it might matter greatly that you run this command.

Make sure you type the command correctly.

Beta Work {Got backup and coffee}
offline▸ Win10Pro 2004.19041.572 x64 i3-3220 RAM8GB HDD Firefox83.0b3 WindowsDefender TRV=1909 WuMgr
offline▸ Win10Pro 20H2.19042.685 x86 Atom N270 RAM2GB HDD WindowsDefender WuMgr GuineaPigVariant
online▸ Win10Pro 2004.19041.746 x64 i5-9400 RAM16GB HDD Firefox86.0b2 WindowsDefender TRV=2004 WuMgr

Reply | Quote

[anonymous]

The /V parameter might have provided a little bit more detail here, I hope you have a complete disk image!

When check disk is run after a reboot it will make a note in the Event Viewer Application Event Log what it did or tried to fix. There is hope, I have seen this severity of emergency power off induced NTFS corruption repaired.

You can skip running check disk, but do not!

Reply | Quote

[Author]

Posts