Chkdisk Question...

[Guest John]

How often, if at all, should chkdisk be run on a computer running Windows XP?

 

John

[Guest Colin Barnhorst]

Re: Chkdisk Question...

 

Chkdsk is not routine maintenance. It should not be run without a

compelling reason.

 

"John" <John@discussions.microsoft.com> wrote in message

news:7583D8A1-8F12-431A-AD82-553285B05413@microsoft.com...

> How often, if at all, should chkdisk be run on a computer running Windows

> XP?

>

> John

[Guest Bill in Co.]

Re: Chkdisk Question...

 

Besides which, the version that comes with WinXP is just way too limited in

what it reports (as compared with that in Win9x).

 

Colin Barnhorst wrote:

> Chkdsk is not routine maintenance. It should not be run without a

> compelling reason.

>

> "John" <John@discussions.microsoft.com> wrote in message

> news:7583D8A1-8F12-431A-AD82-553285B05413@microsoft.com...

>> How often, if at all, should chkdisk be run on a computer running Windows

>> XP?

>>

>> John

[Guest ju.c]

Re: Chkdisk Question...

 

Run chkdsk:

 

1. After moving or copying many files.

2. After uninstalling a large program like Nero or Photoshop.

3. Before installing a large program like Nero or Photoshop.

4. Always run chkdsk before you run a full defrag.

5. You cannot run it too often.

6. Unless otherwise noted, always select to fix found errors.

 

 

See:

 

Seven Golden Rules for Disk Maintenance

http://www.windowsnetworking.com/articles_tutorials/Troubleshooting-File-System-Problems.html

 

"5. Run chkdsk /r on a regular basis. This command finds bad sectors on

your disk and tries to fix them by recovering data from them and moving

it elsewhere. You can run this command either from a command-prompt

window or from the Recovery Console if you can't boot your system

normally. Remember that when you try and run chkdsk.exe on your system

or boot volume, Windows configures autochk.exe (the boot version of

chkdsk.exe) to run at your next reboot. This means you'll need to

schedule downtime for your server when you perform this kind of

maintenance so that autochk.exe can run."

 

 

ju.c

 

 

"John" <John@discussions.microsoft.com> wrote in message

news:7583D8A1-8F12-431A-AD82-553285B05413@microsoft.com...

> How often, if at all, should chkdisk be run on a computer running

> Windows XP?

>

> John

[Guest windmap]

Re: Chkdisk Question...

 

After an Improper or hard shutdown.When you cant boot/login to windows.If

you recieve errors when strating windows.

CHKDSK Checks windows file system for errors.

"John" <John@discussions.microsoft.com> wrote in message

news:7583D8A1-8F12-431A-AD82-553285B05413@microsoft.com...

> How often, if at all, should chkdisk be run on a computer running Windows

> XP?

>

> John

[Guest Unknown]

Re: Chkdisk Question...

 

None of those are compelling reasons to run chkdsk. This is completely

hogwash.

"ju.c" <bibidybubidyboop@mailnator.com> wrote in message

news:umdxpo$sIHA.3604@TK2MSFTNGP03.phx.gbl...

> Run chkdsk:

>

> 1. After moving or copying many files.

> 2. After uninstalling a large program like Nero or Photoshop.

> 3. Before installing a large program like Nero or Photoshop.

> 4. Always run chkdsk before you run a full defrag.

> 5. You cannot run it too often.

> 6. Unless otherwise noted, always select to fix found errors.

>

>

> See:

>

> Seven Golden Rules for Disk Maintenance

> http://www.windowsnetworking.com/articles_tutorials/Troubleshooting-File-System-Problems.html

>

> "5. Run chkdsk /r on a regular basis. This command finds bad sectors on

> your disk and tries to fix them by recovering data from them and moving it

> elsewhere. You can run this command either from a command-prompt window or

> from the Recovery Console if you can't boot your system normally. Remember

> that when you try and run chkdsk.exe on your system or boot volume,

> Windows configures autochk.exe (the boot version of chkdsk.exe) to run at

> your next reboot. This means you'll need to schedule downtime for your

> server when you perform this kind of maintenance so that autochk.exe can

> run."

>

>

> ju.c

>

>

> "John" <John@discussions.microsoft.com> wrote in message

> news:7583D8A1-8F12-431A-AD82-553285B05413@microsoft.com...

>> How often, if at all, should chkdisk be run on a computer running Windows

>> XP?

>>

>> John

>

[Guest Colin Barnhorst]

Re: Chkdisk Question...

 

They are different utilities.

 

"Bill in Co." <not_really_here@earthlink.net> wrote in message

news:u8P1dC%23sIHA.4716@TK2MSFTNGP06.phx.gbl...

> Besides which, the version that comes with WinXP is just way too limited

> in what it reports (as compared with that in Win9x).

>

> Colin Barnhorst wrote:

>> Chkdsk is not routine maintenance. It should not be run without a

>> compelling reason.

>>

>> "John" <John@discussions.microsoft.com> wrote in message

>> news:7583D8A1-8F12-431A-AD82-553285B05413@microsoft.com...

>>> How often, if at all, should chkdisk be run on a computer running

>>> Windows

>>> XP?

>>>

>>> John

>

>

[Guest Malke]

Re: Chkdisk Question...

 

ju.c wrote:

> Run chkdsk:

>

> 1. After moving or copying many files.

> 2. After uninstalling a large program like Nero or Photoshop.

> 3. Before installing a large program like Nero or Photoshop.

> 4. Always run chkdsk before you run a full defrag.

> 5. You cannot run it too often.

> 6. Unless otherwise noted, always select to fix found errors.

 

All of the above is incorrect.

 

Chkdsk should *never* been run unless a problem is suspected *and* if all

data is backed up onto external media.

 

Malke

--

MS-MVP

Elephant Boy Computers

http://www.elephantboycomputers.com

Don't Panic!

[Guest Bill in Co.]

Re: Chkdisk Question...

 

Sorry, I was really thinking of SFC. (Not chkdsk).

Although, in retrospect, even chkdsk seems a bit more limited in its options

(and more automated).

 

Colin Barnhorst wrote:

> They are different utilities.

>

> "Bill in Co." <not_really_here@earthlink.net> wrote in message

> news:u8P1dC%23sIHA.4716@TK2MSFTNGP06.phx.gbl...

>> Besides which, the version that comes with WinXP is just way too limited

>> in what it reports (as compared with that in Win9x).

>>

>> Colin Barnhorst wrote:

>>> Chkdsk is not routine maintenance. It should not be run without a

>>> compelling reason.

>>>

>>> "John" <John@discussions.microsoft.com> wrote in message

>>> news:7583D8A1-8F12-431A-AD82-553285B05413@microsoft.com...

>>>> How often, if at all, should chkdisk be run on a computer running

>>>> Windows

>>>> XP?

>>>>

>>>> John

[Guest Colin Barnhorst]

Re: Chkdisk Question...

 

Ed Bott, in his Windows XP Inside and Out, second edition, pages 1240 ff,

does advise running chkdsk proactively to catch file system errors before

trouble breaks out.

 

However, I have never heard of anyone advising users to run chkdsk as a

clean up tool preceding or following basic copy, move, deletion,

installation, or uninstallation of files and software. Defragmentation yes,

chkdsk no.

 

"Malke" <malke@invalid.invalid> wrote in message

news:%232NqfGEtIHA.552@TK2MSFTNGP06.phx.gbl...

> ju.c wrote:

>

>> Run chkdsk:

>>

>> 1. After moving or copying many files.

>> 2. After uninstalling a large program like Nero or Photoshop.

>> 3. Before installing a large program like Nero or Photoshop.

>> 4. Always run chkdsk before you run a full defrag.

>> 5. You cannot run it too often.

>> 6. Unless otherwise noted, always select to fix found errors.

>

> All of the above is incorrect.

>

> Chkdsk should *never* been run unless a problem is suspected *and* if all

> data is backed up onto external media.

>

> Malke

> --

> MS-MVP

> Elephant Boy Computers

> http://www.elephantboycomputers.com

> Don't Panic!

[Guest Ken Blake, MVP]

Re: Chkdisk Question...

 

On Sun, 11 May 2008 18:14:00 -0700, John

<John@discussions.microsoft.com> wrote:

> How often, if at all, should chkdisk be run on a computer running Windows XP?

 

 

 

It should be run in response to a disk problem or suspected problem.

Otherwise not at all.

 

--

Ken Blake, Microsoft MVP - Windows Desktop Experience

Please Reply to the Newsgroup

[Guest Bill in Co.]

Re: Chkdisk Question...

 

Ken Blake, MVP wrote:

> On Sun, 11 May 2008 18:14:00 -0700, John

> <John@discussions.microsoft.com> wrote:

>

>> How often, if at all, should chkdisk be run on a computer running Windows

>> XP?

>

>

> It should be run in response to a disk problem or suspected problem.

> Otherwise not at all.

 

OR, I'd say: just run occasionally, to make sure there isn't any problem

that we're unaware of (which has happened, on occasion).

[Guest John John (MVP)]

Re: Chkdisk Question...

 

Bill in Co. wrote:

> Ken Blake, MVP wrote:

>

>>On Sun, 11 May 2008 18:14:00 -0700, John

>><John@discussions.microsoft.com> wrote:

>>

>>

>>>How often, if at all, should chkdisk be run on a computer running Windows

>>>XP?

>>

>>

>>It should be run in response to a disk problem or suspected problem.

>>Otherwise not at all.

>

>

> OR, I'd say: just run occasionally, to make sure there isn't any problem

> that we're unaware of (which has happened, on occasion).

 

That is like getting "preemptive surgery" for no reason at all. If the

disk isn't "dirty" it has no errors to fix and running chkdsk is

completely unnecessary.

 

John

[Guest Bill in Co.]

Re: Chkdisk Question...

 

John John (MVP) wrote:

> Bill in Co. wrote:

>> Ken Blake, MVP wrote:

>>

>>> On Sun, 11 May 2008 18:14:00 -0700, John

>>> <John@discussions.microsoft.com> wrote:

>>>

>>>

>>>> How often, if at all, should chkdisk be run on a computer running

>>>> Windows

>>>> XP?

>>>

>>>

>>> It should be run in response to a disk problem or suspected problem.

>>> Otherwise not at all.

>>

>>

>> OR, I'd say: just run occasionally, to make sure there isn't any problem

>> that we're unaware of (which has happened, on occasion).

>

> That is like getting "preemptive surgery" for no reason at all. If the

> disk isn't "dirty" it has no errors to fix and running chkdsk is

> completely unnecessary.

>

> John

 

Trouble is, I've, on occasion, run it (without any switches, which is even

safer), and found there were a few errors, which it has reported resolving.

So I'd say it's more like going in for a checkup.

[Guest Colin Barnhorst]

Re: Chkdisk Question...

 

Occaisonally? As in "just for the heck of it"?

 

"Bill in Co." <not_really_here@earthlink.net> wrote in message

news:eqtp7EGtIHA.4076@TK2MSFTNGP06.phx.gbl...

> Ken Blake, MVP wrote:

>> On Sun, 11 May 2008 18:14:00 -0700, John

>> <John@discussions.microsoft.com> wrote:

>>

>>> How often, if at all, should chkdisk be run on a computer running

>>> Windows XP?

>>

>>

>> It should be run in response to a disk problem or suspected problem.

>> Otherwise not at all.

>

> OR, I'd say: just run occasionally, to make sure there isn't any problem

> that we're unaware of (which has happened, on occasion).

>

[Guest Bill in Co.]

Re: Chkdisk Question...

 

If it's been awhile, and I remember, I do it. I wouldn't say "just for

the heck of it".

As I said before, it's kinda like going in for a checkup. And I'd rather

know about it first before making a TI image backup (again, running it w/o

the switches, which is safer)

 

Colin Barnhorst wrote:

> Occasionally? As in "just for the heck of it"?

>

> "Bill in Co." <not_really_here@earthlink.net> wrote in message

> news:eqtp7EGtIHA.4076@TK2MSFTNGP06.phx.gbl...

>> Ken Blake, MVP wrote:

>>> On Sun, 11 May 2008 18:14:00 -0700, John

>>> <John@discussions.microsoft.com> wrote:

>>>

>>>> How often, if at all, should chkdisk be run on a computer running

>>>> Windows XP?

>>>

>>>

>>> It should be run in response to a disk problem or suspected problem.

>>> Otherwise not at all.

>>

>> OR, I'd say: just run occasionally, to make sure there isn't any problem

>> that we're unaware of (which has happened, on occasion).

[Guest Malke]

Re: Chkdisk Question...

 

Colin Barnhorst wrote:

> Ed Bott, in his Windows XP Inside and Out, second edition, pages 1240 ff,

> does advise running chkdsk proactively to catch file system errors before

> trouble breaks out.

 

So I've heard. Then I guess I have to disagree with Ed Bott. As far as I'm

concerned, Chkdsk is for when things go sour and not to be used lightly.

 

Best regards,

 

Malke

--

MS-MVP

Elephant Boy Computers

http://www.elephantboycomputers.com

Don't Panic!

[Guest R. McCarty]

Re: Chkdisk Question...

 

Just open a Command Prompt Window & type

FSUtil Dirty Query C:

to determine a volume's health

*Substitute C: with whatever drive you wish to check

 

"Colin Barnhorst" <c.barnhorst@comcast.net> wrote in message

news:99DEC975-2348-454B-BFA7-81FBE788590D@microsoft.com...

> Occaisonally? As in "just for the heck of it"?

>

> "Bill in Co." <not_really_here@earthlink.net> wrote in message

> news:eqtp7EGtIHA.4076@TK2MSFTNGP06.phx.gbl...

>> Ken Blake, MVP wrote:

>>> On Sun, 11 May 2008 18:14:00 -0700, John

>>> <John@discussions.microsoft.com> wrote:

>>>

>>>> How often, if at all, should chkdisk be run on a computer running

>>>> Windows XP?

>>>

>>>

>>> It should be run in response to a disk problem or suspected problem.

>>> Otherwise not at all.

>>

>> OR, I'd say: just run occasionally, to make sure there isn't any problem

>> that we're unaware of (which has happened, on occasion).

>>

>

[Guest Colin Barnhorst]

Re: Chkdisk Question...

 

You can simply run chkntfs x: or use R McCarty's suggested FSUtil command to

see if the dirty bit is set. Why keep the drive churning through a lengthy

chkdsk run?

 

"Bill in Co." <not_really_here@earthlink.net> wrote in message

news:%23ffXdCHtIHA.4716@TK2MSFTNGP06.phx.gbl...

> If it's been awhile, and I remember, I do it. I wouldn't say "just for

> the heck of it".

> As I said before, it's kinda like going in for a checkup. And I'd rather

> know about it first before making a TI image backup (again, running it w/o

> the switches, which is safer)

>

> Colin Barnhorst wrote:

>> Occasionally? As in "just for the heck of it"?

>>

>> "Bill in Co." <not_really_here@earthlink.net> wrote in message

>> news:eqtp7EGtIHA.4076@TK2MSFTNGP06.phx.gbl...

>>> Ken Blake, MVP wrote:

>>>> On Sun, 11 May 2008 18:14:00 -0700, John

>>>> <John@discussions.microsoft.com> wrote:

>>>>

>>>>> How often, if at all, should chkdisk be run on a computer running

>>>>> Windows XP?

>>>>

>>>>

>>>> It should be run in response to a disk problem or suspected problem.

>>>> Otherwise not at all.

>>>

>>> OR, I'd say: just run occasionally, to make sure there isn't any

>>> problem

>>> that we're unaware of (which has happened, on occasion).

>

>

[Guest Bruce Chambers]

Re: Chkdisk Question...

 

John wrote:

> How often, if at all, should chkdisk be run on a computer running Windows XP?

>

> John

 

 

Only when an error is detected by the OS.

 

--

 

Bruce Chambers

 

Help us help you:

http://www.catb.org/~esr/faqs/smart-questions.html

 

http://support.microsoft.com/default.aspx/kb/555375

 

They that can give up essential liberty to obtain a little temporary

safety deserve neither liberty nor safety. ~Benjamin Franklin

 

Many people would rather die than think; in fact, most do. ~Bertrand Russell

 

The philosopher has never killed any priests, whereas the priest has

killed a great many philosophers.

~ Denis Diderot

[Guest Bruce Chambers]

Re: Chkdisk Question...

 

ju.c wrote:

> Run chkdsk:

>

> 1. After moving or copying many files.

 

Why? Please provide a technical reason.

> 2. After uninstalling a large program like Nero or Photoshop.

 

Why? Please provide a technical reason.

> 3. Before installing a large program like Nero or Photoshop.

 

Why? Please provide a technical reason.

> 4. Always run chkdsk before you run a full defrag.

 

Why? Please provide a technical reason.

> 5. You cannot run it too often.

 

Utter nonsense, unless one's sole goal is to create utterly unnecessary

wear and tear on the hard drive.

> 6. Unless otherwise noted, always select to fix found errors.

>

 

No. The correct answer would be "*ONLY* to seek/fix errors reported by

the OS."

 

>

> See:

>

> Seven Golden Rules for Disk Maintenance

> http://www.windowsnetworking.com/articles_tutorials/Troubleshooting-File-System-Problems.html

>

>

 

 

Er.... That link is about Windows Server 2003, *NOT* WinXP. They're

completely different operating systems, you know. (And even then I'd

call it bad advice.)

 

 

 

--

 

Bruce Chambers

 

Help us help you:

http://www.catb.org/~esr/faqs/smart-questions.html

 

http://support.microsoft.com/default.aspx/kb/555375

 

They that can give up essential liberty to obtain a little temporary

safety deserve neither liberty nor safety. ~Benjamin Franklin

 

Many people would rather die than think; in fact, most do. ~Bertrand Russell

 

The philosopher has never killed any priests, whereas the priest has

killed a great many philosophers.

~ Denis Diderot