sorry to bother all you intellectual people, but doing disk cleanup. is it
safe to delete old chkdsk files?

"Sky" <Sky@discussions.microsoft.com> wrote
> sorry to bother all you intellectual people, but doing disk cleanup. is
> it
> safe to delete old chkdsk files?

Have you looked at them? They are usually not good for anything. If there
is nothing worthwhile in them then delete them.

--
Rock [MS-MVP User/Shell]

Where are you finding the old Chkdsk files?

Most people have trouble finding out what the results are whenever they run
Chkdsk, because they don't realize they need to look for Winlogon in the
Event Viewer IMMEDIATELY after they do run Chkdsk.

Alan

"Rock" <Rock@nospam.net> wrote in message
news:OsA7KPSjHHA.4516@TK2MSFTNGP03.phx.gbl...
> "Sky" <Sky@discussions.microsoft.com> wrote
>> sorry to bother all you intellectual people, but doing disk cleanup. is
>> it
>> safe to delete old chkdsk files?
>
> Have you looked at them? They are usually not good for anything. If
> there is nothing worthwhile in them then delete them.
>
> --
> Rock [MS-MVP User/Shell]

"Alan" <inthegalaxy@solarsystem.huh> wrote:

>Where are you finding the old Chkdsk files?

Ummm... disk cleanup finds them.

DUH.

It's a good thing that disk cleanup CAN find them. Most users don't have a
clue how to see what chkdsk did..

Microsoft should publish a KB article to advise users how to find the chkdsk
logs using disk cleanup.

Alan

"Uncle Grumpy" <unclegrumpy@ameritech.net> wrote in message
news:omli33t7ul0u19rhvkdmksdu2512e3su79@4ax.com...
> "Alan" <inthegalaxy@solarsystem.huh> wrote:
>
>>Where are you finding the old Chkdsk files?
>
> Ummm... disk cleanup finds them.
>
> DUH.

I don't think he is talking about log files. He's asking about .chk files.

John

Alan wrote:

> It's a good thing that disk cleanup CAN find them. Most users don't have a
> clue how to see what chkdsk did..
>
> Microsoft should publish a KB article to advise users how to find the chkdsk
> logs using disk cleanup.
>
> Alan
>
> "Uncle Grumpy" <unclegrumpy@ameritech.net> wrote in message
> news:omli33t7ul0u19rhvkdmksdu2512e3su79@4ax.com...
>
>>"Alan" <inthegalaxy@solarsystem.huh> wrote:
>>
>>
>>>Where are you finding the old Chkdsk files?
>>
>>Ummm... disk cleanup finds them.
>>
>>DUH.
>
>
>

Thanks for the clarification, John. I thought I had been missing an easier
way to see the results of running chkdsk, other than by going into Event
Viewer and looking at the very intuitive labeled 'Winlogon.' :>

Alan

"John John" <audetweld@nbnet.nb.ca> wrote in message
news:O3WgOMXjHHA.5012@TK2MSFTNGP04.phx.gbl...
>I don't think he is talking about log files. He's asking about .chk files.
>
> John
>
> Alan wrote:
>
>> It's a good thing that disk cleanup CAN find them. Most users don't have
>> a clue how to see what chkdsk did..
>>
>> Microsoft should publish a KB article to advise users how to find the
>> chkdsk logs using disk cleanup.
>>
>> Alan
>>
>> "Uncle Grumpy" <unclegrumpy@ameritech.net> wrote in message
>> news:omli33t7ul0u19rhvkdmksdu2512e3su79@4ax.com...
>>
>>>"Alan" <inthegalaxy@solarsystem.huh> wrote:
>>>
>>>
>>>>Where are you finding the old Chkdsk files?
>>>
>>>Ummm... disk cleanup finds them.
>>>
>>>DUH.
>>
>>
>>
>

Well, you see the summary and results of the chkdsk in the Event Log but
if chkdsk found bad files it couldn't fix it will put the bad files and
bits in a found.nnn folder as .chk files. Sometimes the files can be
recovered or rebuilt from the .chk files but often the .chk files are
next to useless. These old .chk files are safe to delete, unless you
plan to study the files and attempt to recover data from them they serve
no purposes.

John

Alan wrote:

> Thanks for the clarification, John. I thought I had been missing an easier
> way to see the results of running chkdsk, other than by going into Event
> Viewer and looking at the very intuitive labeled 'Winlogon.' :>
>
> Alan
>
> "John John" <audetweld@nbnet.nb.ca> wrote in message
> news:O3WgOMXjHHA.5012@TK2MSFTNGP04.phx.gbl...
>
>>I don't think he is talking about log files. He's asking about .chk files.
>>
>>John
>>
>>Alan wrote:
>>
>>
>>>It's a good thing that disk cleanup CAN find them. Most users don't have
>>>a clue how to see what chkdsk did..
>>>
>>>Microsoft should publish a KB article to advise users how to find the
>>>chkdsk logs using disk cleanup.
>>>
>>> Alan
>>>
>>>"Uncle Grumpy" <unclegrumpy@ameritech.net> wrote in message
>>>news:omli33t7ul0u19rhvkdmksdu2512e3su79@4ax.com ...
>>>
>>>
>>>>"Alan" <inthegalaxy@solarsystem.huh> wrote:
>>>>
>>>>
>>>>
>>>>>Where are you finding the old Chkdsk files?
>>>>
>>>>Ummm... disk cleanup finds them.
>>>>
>>>>DUH.
>>>
>>>
>>>
>
>

Hi John,

That's true. I remember those *.chk files from MS-DOS -- and earlier
Windows -- times, when there were both Scandisk and Chkdsk in the Operating
System, and users were instructed to put a floppy in the drive before
attempting to do any fixes if there had been any disk errors found.

There were many times when I actually could recover corrupted files. Plus,
it was always nice to be able to see the results of the Scandisk/Chkdsk
operation by looking at the log which was generated and EASILY accessible.

Alan

"John John" <audetweld@nbnet.nb.ca> wrote in message
news:ePX74xXjHHA.4768@TK2MSFTNGP05.phx.gbl...
> Well, you see the summary and results of the chkdsk in the Event Log but
> if chkdsk found bad files it couldn't fix it will put the bad files and
> bits in a found.nnn folder as .chk files. Sometimes the files can be
> recovered or rebuilt from the .chk files but often the .chk files are next
> to useless. These old .chk files are safe to delete, unless you plan to
> study the files and attempt to recover data from them they serve no
> purposes.
>
> John
>
> Alan wrote:
>
>> Thanks for the clarification, John. I thought I had been missing an
>> easier way to see the results of running chkdsk, other than by going into
>> Event Viewer and looking at the very intuitive labeled 'Winlogon.' :>
>>
>> Alan
>>
>> "John John" <audetweld@nbnet.nb.ca> wrote in message
>> news:O3WgOMXjHHA.5012@TK2MSFTNGP04.phx.gbl...
>>
>>>I don't think he is talking about log files. He's asking about .chk
>>>files.
>>>
>>>John
>>>
>>>Alan wrote:
>>>
>>>
>>>>It's a good thing that disk cleanup CAN find them. Most users don't have
>>>>a clue how to see what chkdsk did..
>>>>
>>>>Microsoft should publish a KB article to advise users how to find the
>>>>chkdsk logs using disk cleanup.
>>>>
>>>> Alan
>>>>
>>>>"Uncle Grumpy" <unclegrumpy@ameritech.net> wrote in message
>>>>news:omli33t7ul0u19rhvkdmksdu2512e3su79@4ax.co m...
>>>>
>>>>
>>>>>"Alan" <inthegalaxy@solarsystem.huh> wrote:
>>>>>
>>>>>
>>>>>
>>>>>>Where are you finding the old Chkdsk files?
>>>>>
>>>>>Ummm... disk cleanup finds them.
>>>>>
>>>>>DUH.
>>>>
>>>>
>>>>
>>
>>
>

Sky wrote:
> sorry to bother all you intellectual people, but doing disk cleanup.
> is it safe to delete old chkdsk files?

Yes, they are safe to delete. They are not needed. They are recovered
"snippets" of files from past runs of chkdsk, so if you're not looking for
anything in them, blow them away.

Pop`

"Alan" <inthegalaxy@solarsystem.huh> wrote:

>Microsoft should publish a KB article to advise users how to find the chkdsk
>logs using disk cleanup.

Reading is a skill.

He wasn't talking about log files.

"Uncle Grumpy" is a very apt name for you.

Alan

"Uncle Grumpy" <unclegrumpy@ameritech.net> wrote in message
news:iink33pc8ibf0lc8jkl6j2u93sctffg6vn@4ax.com...
> "Alan" <inthegalaxy@solarsystem.huh> wrote:
>
>>Microsoft should publish a KB article to advise users how to find the
>>chkdsk
>>logs using disk cleanup.
>
> Reading is a skill.
>
> He wasn't talking about log files.

Uncle Grumpy wrote:
> "Alan" <inthegalaxy@solarsystem.huh> wrote:
>
>> Microsoft should publish a KB article to advise users how to find
>> the chkdsk logs using disk cleanup.
>
> Reading is a skill.
>
> He wasn't talking about log files.

Bored, huh? When you have nothing to say, that's exactly what you should
say: Nothing.

"Poprivet" <poprivet@devnull.spamcop.net> wrote:

>Uncle Grumpy wrote:
>> "Alan" <inthegalaxy@solarsystem.huh> wrote:
>>
>>> Microsoft should publish a KB article to advise users how to find
>>> the chkdsk logs using disk cleanup.
>>
>> Reading is a skill.
>>
>> He wasn't talking about log files.
>
>Bored, huh? When you have nothing to say, that's exactly what you should
>say: Nothing.

Bite me

chk files and the Found folders

On Fat formatted volumes.

Chkdsk saves each repaired file in the root folder as a File<nnnn>.chk file,
and each repaired folder in the root folder as a Found.<nnn> folder, where
<n> is a number.

Recovering Lost Clusters on FAT Volumes
http://www.microsoft.com/resources/d...d_tro_kbnn.asp

Link is no good anymore, below is from that old link.

<quote>
Because some repairs on FAT volumes, such as correcting lost clusters
(also known as allocation units) or cross-linked files, change the volume's
file allocation table and can cause data loss, Chkdsk first prompts you with
a confirmation message similar to the following:

10 lost allocation units found in 3 chains.
Convert lost chains to files? (Y/N)

If you press the N key, Windows XP Professional fixes the errors on the
volume but does not save the contents of the lost clusters.

If you press the Y key, Windows XP Professional attempts to identify the
folder to which they belong. If the folder is identified, the lost cluster
chains are saved as files.

If Windows XP Professional cannot identify the folder or if the folder does
not exist, it saves each chain of lost clusters in a folder called
Found.xxx, where xxx is a sequential number starting with 000. If no folder
Found.000 exists, one is created at the root. If one or more sequential
folders called Found.xxx (starting at 000) exist, a folder that uses the
next number in the sequence is created.

Windows XP Professional creates Found.xxx folders as hidden system folders.
To see a list of Found.xxx folders, at the root folder in the command
prompt, type dir /a. For information about viewing hidden system folders in
My Computer or Windows Explorer, see Windows XP Professional Help.

After the storage folder has been identified or created, one or more files
with a name in the format Filennnn.chk are saved. (The first saved file is
named File0000.chk, the second is named File0001.chk, and so on in
sequence.) When Chkdsk finishes, you can examine the contents of these files
with a text editor such as Notepad to see whether they contain any needed
data (if the converted chains came from corrupted binary files, they are of
no value). You can delete the .chk files after you save any useful data.

Caution
Because other programs might create and use files with the .chk extension,
you must be careful to delete only the .chk files that are in the Found.xxx
folders.
<quote>

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In news:OleAmxSjHHA.1900@TK2MSFTNGP04.phx.gbl,
Alan <inthegalaxy@solarsystem.huh> hunted and pecked:
> Where are you finding the old Chkdsk files?
>
> Most people have trouble finding out what the results are whenever they
> run Chkdsk, because they don't realize they need to look for Winlogon in
> the Event Viewer IMMEDIATELY after they do run Chkdsk.
>
> Alan
>
> "Rock" <Rock@nospam.net> wrote in message
> news:OsA7KPSjHHA.4516@TK2MSFTNGP03.phx.gbl...
>> "Sky" <Sky@discussions.microsoft.com> wrote
>>> sorry to bother all you intellectual people, but doing disk cleanup. is
>>> it
>>> safe to delete old chkdsk files?
>>
>> Have you looked at them? They are usually not good for anything. If
>> there is nothing worthwhile in them then delete them.
>>
>> --
>> Rock [MS-MVP User/Shell]