Files become "recently changed" just opening them

General discussion related to "Everything".
Post Reply
maxfactor
Posts: 27
Joined: Tue Nov 08, 2016 4:31 pm

Files become "recently changed" just opening them

Post by maxfactor » Thu Nov 10, 2016 2:50 pm

Hi all,

I have had a long mail exchange with @void and finally he has found the reason for files becoming "rc:" just opening them (STREAM_CHANGE).

EDIT: in my case, it seems it is something related with the Dropbox usage.

Has anyone the same behavior?

@void : can we disable STREAM_CHANGE check in any way?

Thanks
Last edited by maxfactor on Fri Nov 11, 2016 11:00 am, edited 1 time in total.

void
Site Admin
Posts: 4876
Joined: Fri Oct 16, 2009 11:31 pm

Re: Files become "recently changed" just opening them

Post by void » Fri Nov 11, 2016 9:07 am

I've added the Everything.ini option: usn_record_filter to Everything 1.4.1.800b

Please try enabling this filter to ignore STREAM_CHANGE:
  • Completely exit Everything (right click your Everything system tray icon and click Exit)
  • Open your %APPDATA%\Everything\Everything.ini
  • Add the following line to the end of your Everything.ini:
    usn_record_filter=0xFFDFFFFF
  • Save changes and restart Everything.
Note: Changing the usn record filter may cause Everything to miss changes to your file system. It can also cause file information such as size and date modified to not update in Everything.
Note: I highly recommend leaving this usn_record_filter set to 0xffffffff and preventing the STREAM_CHANGE in the first place, as technically the file was modified and should show in the recent change list.

A list of all USN record filter flags:

Code: Select all

USN_REASON_DATA_OVERWRITE        0x00000001
USN_REASON_DATA_EXTEND           0x00000002
USN_REASON_DATA_TRUNCATION       0x00000004
USN_REASON_NAMED_DATA_OVERWRITE  0x00000010
USN_REASON_NAMED_DATA_EXTEND     0x00000020
USN_REASON_NAMED_DATA_TRUNCATION 0x00000040
USN_REASON_FILE_CREATE           0x00000100
USN_REASON_FILE_DELETE           0x00000200
USN_REASON_EA_CHANGE             0x00000400
USN_REASON_SECURITY_CHANGE       0x00000800
USN_REASON_RENAME_OLD_NAME       0x00001000
USN_REASON_RENAME_NEW_NAME       0x00002000
USN_REASON_INDEXABLE_CHANGE      0x00004000
USN_REASON_BASIC_INFO_CHANGE     0x00008000
USN_REASON_HARD_LINK_CHANGE      0x00010000
USN_REASON_COMPRESSION_CHANGE    0x00020000
USN_REASON_ENCRYPTION_CHANGE     0x00040000
USN_REASON_OBJECT_ID_CHANGE      0x00080000
USN_REASON_REPARSE_POINT_CHANGE  0x00100000
USN_REASON_STREAM_CHANGE         0x00200000
USN_REASON_CLOSE                 0x80000000
The USN record filter is ANDed with each USN record reason. Combine these flags to enable or disable Everything processing them.

maxfactor
Posts: 27
Joined: Tue Nov 08, 2016 4:31 pm

Re: Files become "recently changed" just opening them

Post by maxfactor » Fri Nov 11, 2016 11:36 am

Thank you David.

Last time the debug was showing a STREAM_CHANGE as the cause of the rc status. Now that I can get rid of them thanks to the filter that you have implemented, I have found this

USN_RECORD 18721849632, FLAGS 00002020, PARENT FRN 00010000000003a8, FRN 21aa000000000761, reason OBJECT_ID_CHANGE (00080000), filename 2016-10-22 ALL.txt

and so after opening the file has become a "recently changed" again.
Maybe that the STREAM_CHANGE involves a physiological OBJECT_ID_CHANGE?

It is very frustrating to not understand why my "recently changed" list is forced to show also just-opened files... (I know it is not an Everything-related trouble). I really don't know if I will succed in achieving my goal, maybe some background software is doing the ...

Anyway I know ho to use the debug and verbose feature, and I know (and thank you for) the great availability you have had till now, so I think that I really will not bore you anymore with this problem. It was just a chance to share and see if someone else has a similar problem.

Thanks a lot
Kind regards

void
Site Admin
Posts: 4876
Joined: Fri Oct 16, 2009 11:31 pm

Re: Files become "recently changed" just opening them

Post by void » Fri Nov 11, 2016 11:44 am

Filter out USN_REASON_STREAM_CHANGE and OBJECT_ID_CHANGE:
usn_record_filter=0xFFD7FFFF

maxfactor
Posts: 27
Joined: Tue Nov 08, 2016 4:31 pm

Re: Files become "recently changed" just opening them

Post by maxfactor » Fri Nov 11, 2016 12:03 pm

Great!

It seems it is really the way to go! I was losing hope of having the recent-change feature working as I would expect.

Thank you so much!

Post Reply