Main Forum > Tweaking.com Support & Help

Chkdsk

(1/4) > >>

Omnivore:
In running the free version several times, I continually got a "disk errors" message on the initial disk check and it indicated chkdsk had to be run.  After running chkdsk and another utility that checks the drive (spinrite), I received the same error again on your check.  Is this normal??

Steve

Boggin:
When you run chkdsk from within the program, it just runs it in read-only mode and if the hard drive is being written to at the time you run it in that mode - then it can report errors.

While you don't say which version of Windows you are using, run a command prompt as an administrator - type chkdsk /f then press enter.

What happens next will depend upon your version of Windows but regardless of which, you will be able to read the full report in Event Viewer.

Go Start - type eventvwr and press enter.

When Event Viewer opens, ensure that Event Viewer (Local) in the upper left pane is highlighted by clicking on it if necessary and when it has read the data, expand Windows Logs - click on Application - Action/Find then type chkdsk of wininit into the Find box and press enter.

Cancel the Find box and read the report in the scrollable window.

If you aren't sure what it is reporting, then click on Copy/Copy details as text in the lower right pane - right click in the forum reply box and select Paste.

whiggs:
I get this error all the time too when running chkdsk in read only mode.  The way I get a 100% accurate reading of what is going is by either creating a windows Pre-installation environment and booting to it, or by booting to windows recovery environment and launching command prompt, then run the chkdsk from there.  Windows recovery environment is located on a separate partition altogether and windows pre-installation environment you boot from a usb stick or disk, so gets rid of that issue right there.

Boggin:

--- Quote from: whiggs on September 17, 2016, 09:17:50 am ---I get this error all the time too when running chkdsk in read only mode.  The way I get a 100% accurate reading of what is going is by either creating a windows Pre-installation environment and booting to it, or by booting to windows recovery environment and launching command prompt, then run the chkdsk from there.  Windows recovery environment is located on a separate partition altogether and windows pre-installation environment you boot from a usb stick or disk, so gets rid of that issue right there.

--- End quote ---

Can you run a cmd prompt as an admin in normal mode and see what a chkdsk /f reports then ?

whiggs:
I'm sorry.  Is this a request for me to do this or is this a question?  If it is a question, then both of the options I mentioned do not actually boot into windows.  It boots into an entirely separate, very very small, operating system that has many of the command line utilities that Windows has available to it.  You can run chkdsk from this environment in any way you could run it from  regular windows environment.  HOWEVER, if you build a Windows Pre-installation environment using the Windows adk, it VERY, VERY important to use the same version of the adk that corresponds to the version of the Windows you have installed (there are multiple adks for windows 10).  So you do not need "administrator rights" when running the command prompt sing either method mentioned above: all it is is a blank background and a single command prompt.  When you exit the command prompt, the computer restarts.  I hope this answered your question.

Navigation

[0] Message Index

[#] Next page