My comment is: Why would one want to disable a function that helps the
system to run in a more reliable condition?
Guess I am a type of person who just doesn't get human nature.
As I have stated, oh so many times, in these newsgroups: The worst enemy of
any running computer is the person at the keyboard! Cause of errors = 99% of
all known problems
We ask people who have a multitude of problems - "What have you done to
alter your system?" They come back with, "I didn't do anything!"
--
Regards,
Richard Urban
Microsoft MVP Windows Shell/User
(For email, remove the obvious from my address)
Quote from George Ankner:
If you knew as much as you think you know,
You would realize that you don't know what you thought you knew!
"Jon" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
>I was looking through the new options available with the 'fsutil' command
>in Vista (as you do), and stumbled across this little chap.
>
> fsutil repair
>
> eg
>
> C:\Windows\system32>fsutil repair query c:
> Self healing is enabled for volume c: with flags 0x1.
> flags: 1 - enable general repair
> 8 - warn about potential data loss
>
>
> Is self-healing an indispensable option to keep enabled, or is there a
> performance impact involved? Would there any value in disabling it for a
> particular volume (and say replacing it with a traditional scheduled
> 'chkdsk' check)?
>
> I tried disabling it, and didn't notice any immediate catastrophic effect.
>
> Ran across this article which also provides some background.
>
> Self-Healing NTFS
> http://technet2.microsoft.com/window....mspx?mfr=true
>
>
> Thanks for any thoughts.
>
>
> --
> Jon
>
>