By registering with us, you'll be able to discuss, share and private message with other members of our community.

SignUp Now!

NTFS descriptions?

I enabled NTFS descriptions and gave descriptions to two files in v:\ (w3*). Now, every file in v:\ has an oddball NTFS stream and those with a description have two. And one file (wmitest.btm) has a SummaryInformation stream but no description (according to @DESCRIPT). What's going on there?

2019-11-06  12:19           1,873  w32tmparams.btm
                              132    SummaryInformation:$DATA
                                0    {4c8cc155-6c1e-11d1-8e41-00c04fb9386d}:$DATA
2019-11-06  12:19           1,471  w32tmweights.btm
                              132    SummaryInformation:$DATA
                              775    .log:$DATA
                                0    {4c8cc155-6c1e-11d1-8e41-00c04fb9386d}:$DATA
2019-11-06  12:19             547  wmitest.btm
                               88    SummaryInformation:$DATA
                                0    {4c8cc155-6c1e-11d1-8e41-00c04fb9386d}:$DATA
Only the w3* SummaryInformation streams were created by TCC, The wmitest.btm one may be old, or may have been created by another app - TCC doesn't have exclusive ownership of SummaryInformation.

Start CMD, and do a "dir /r w*.btm" and see if it matches.
I already got rid of them. I assure you, they were not there previously; I look at the streams in that directory regularly. My history contains all I did involving descriptions (no smoking gun). Later I'll re-enable NTFS descriptions and try to reproduce it.

P.S., According to a doc I found, the {4c8cc155-6c1e-11d1-8e41-00c04fb9386d} stream is required if there is to be a SummaryInformation stream. And the actual name of the stream was (using TCC lingo) "%@CHAR[5]SummaryInformation". I did this to get rid of them.

do f in * ( del %f:%@char[5]SummaryInformation )
Doing this
describe timecheck.btm /=
and cancelling the dialog results in the creation of timecheck.btm:{4c8cc155-6c1e-11d1-8e41-00c04fb9386d} (and no SummaryInformation).

More to come.
Last edited:
@descript[] was the big the culprit. See below. Yesterday, I used "@descript[*]" buried in a PDIR. So all files got it.

Last edited:
4c8cc155-6c1e-11d1-8e41-00c04fb9386d is the control stream created by Windows (not TCC). It is required for files containing property sets (like SummaryInformation) stored in the streams.

If you delete it, bad things will happen to your streams.
Along with it I deleted the "\005SummaryInformation" streams. Apparently no harm done. It only affected the files in one directory, all created by me.

Similar threads