Date modified for folders not showing correctly

[harryray2]

The date modified and date accessed for folders aren't showing correctly...the files though, do seem to show the correct dates.

It doesn't appear to be a problem on all folders, just some. I'm not over sure, but it look like sub folders are correct but not some parent folders.

[therube]

Do the dates differ from what Windows Explorer shows?

[harryray2]

Yes they do...some by a few months and some by several years.

[therube]

Some examples of particular directories & their differences?
And these are on NTFS or?
Windows 10?

And there are specific (regedit) changes a user can make, like disabling 8.3, might you have made changes in that respect.

Might your .db be out of wack (in need of a Rebuild)?
(But, if you were to do that... So maybe back up the existing .db first, that way you can reference it again, if needed...)

[horst.epp]

How do you look up the dates of the parent folder ?
If you mean the .. entries that is a known difference.
Also date accessed should be disabled as default for NTFS.

[NotNull]

Are those directory junctions? (Like C:\Documnts and Settings)?

Check in CMD: DIR /AD; they will be shown as <JUNCTION> :

2021-10-07 17_42_06-cmd.exe - Shortcut.png (33.52 KiB) Viewed 9742 times

[harryray2]

Therube...windows 7 and NTFS Everything 1.5.

c:\Programdata (folder modified and accessed incorrect)>abelhadigital.com (folder modified and accessed incorrect)>hostsman (folder modified and accessed correct) files within correct and I created a folder called test within the same folder as the files, this is also correct.

I've tried rebuilding the database, also deleting the database.

8.3 is set in the registry as 2, which appears to be "Sets 8dot3 name creation on a per volume basis"

[harryray2]

Notnull, I have a junction showing up as application data [c:\programdata]

The programdata folder is showing incorrect dates.

It does appear that folders within programdata are showing up incorrectly until one drills down.

[harryray2]

Possibly something to do with junctions?

[void]

It might have something to do with junctions..

Could you please send a screenshot of Everything showing the incorrect dates. (please search for: c:\programdata\* )

Could you please send a screenshot of following options page: Everything -> Tools -> Indexes

Could you please send a screenshot of a command prompt after running the following commands:
cd /d c:\programdata
dir /ad

Times from dir /ad are wrong (doesn't adjust for day light savings)

Could you please send a screenshot of c:\programdata in Windows Explorer.

[harryray2]

Thanks, yes, I'll do that.

Some of the folders within programdata are correct whilst some are wildly inaccurate.

I don't think it's only folders within programdata that are affected, it seems to be on some other directories as well but it will take me a while to plogh through and find them.

I'm not really too clear about junctions, I just know they're a form of shortcut...

[void]

Some of the folders within programdata are correct whilst some are wildly inaccurate.

Are the dates out by days? months? years?


Are you using the correct Date Modified property in Everything? (please make sure you are not using Date Recent Changed or Date Changed)
Everything doesn't track Date Accessed changes. (a force rebuild is required to pick up the new date accessed)

It sounds like a force rebuild isn't helping either, so there is most likely something wrong with Everything..

What are you using to compare dates with? (eg: Windows Explorer)

[harryray2]

I'm comparing date with windows explorer, but there are folders that I know have been modified or accessed in the last day, or few days that are showing dates that are years out.
I haven't yet looked to see if date created is affected.

Dates accessed are also affected, folders that I know have been accessed recently are way out.

In general the dates seem to be out by years with some by a few months.

I'm using DM: DC: and DA: I'm not using date changed or recently changed although I have date changed in properties on my main everything but not enabled on instance.

I've tried a rebuild and also tried deleting the database and restarting Everything.

I've just come across the fast rescan command..I haven't enabled or tried it yet but presumably this problem would also affect the rescan if and when I do try it out?

[void]

It sounds like you are using folder indexing.
Maybe there is an issue with folder indexing.

What type of index are you using ? (eg: Tools -> Options -> NTFS or Tools -> Options -> Folder)



Are you indexing Date Modified under Tools -> Options -> Indexes?



Fast rescan will only work for NTFS folders.
If it is enabled for other incompatible file systems, Everything will miss changes during rescanning.
-Is the folder index an NTFS folder? or a FAT folder?

[harryray2]

I'm using NTFS with 1.5

with options>NTFS>
On instance, the two offline disk's are disabled (Include in database unchecked)
On the main Everything, all four entries are enabled (Include in database checked)
See screenshot.

With options>properties
On instance, properties are disabled
On the main Everything, all the properties in the box are enabled, some of which include files and folders are enabled and some with only include files enabled.
All with entries in exclude folder entries and some with exclude files as well.
See screenshot

I'm having the same problem with both instances.
Would it be useful if I included the ini file from both instances?

Something I've just noticed in the instance, although I have properties disabled, the main body is greyed out although the entries aren't. I'm still able to add the columns and see results.

I ask about fast rescan as I'm wondering if the current problem of folders not showing the correct DM: dates will affect fast rescan?

[therube]

there are folders that I know have been modified or accessed in the last day, or few days that are showing dates that are years out.

I'm not sure of the circumstances, but there can be times where one would expected an updated date to happen - but Windows doesn't.

You have the Mozilla directory dated 9-21-21, yet the most recent (immediate child) file/dir within is dated 7-9-21.
(Maybe some temporary file was written, then erased on 9-21-21, but I'm thinking not too likely?)
(Oh, that's actually for Firefox - which I generally ignore, so maybe not such a great example.)

Code: Select all

programdata:
drw-rw-rw-   3 RUBEN7 0 4096 2021-09-21 12:17 Mozilla

programdata/Mozilla:
total 4
-rw-rw-rw-  1 RUBEN7 0 156 2021-07-09 11:16 profile_count_72BA74B3052734C0.json
-rw-rw-rw-  1 RUBEN7 0   0 2021-06-17 14:10 UpdateLock-72BA74B3052734C0
drw-rw-rw-  4 RUBEN7 0   0 2021-06-17 14:10 updates

programdata/Mozilla/updates:
total 8
drw-rw-rw-  3 RUBEN7 0 4096 2021-10-07 12:12 72BA74B3052734C0
drw-rw-rw-  3 RUBEN7 0 4096 2021-09-27 13:31 A0D9F245A5B00C5D

programdata/Mozilla/updates/72BA74B3052734C0:
total 16
-rw-rw-rw-  1 RUBEN7 0  103 2021-08-26 11:19 update-config.json
drw-rw-rw-  4 RUBEN7 0 4096 2021-10-06 11:30 updates
-rw-rw-rw-  1 RUBEN7 0 7153 2021-10-06 11:30 updates.xml

programdata/Mozilla/updates/72BA74B3052734C0/updates:
total 12
drw-rw-rw-  2 RUBEN7 0    0 2021-10-06 11:30 0
-rw-rw-rw-  1 RUBEN7 0 4595 2021-10-06 11:24 backup-update.log
drw-rw-rw-  2 RUBEN7 0    0 2021-10-06 11:24 downloading
-rw-rw-rw-  1 RUBEN7 0  915 2021-10-06 11:30 last-update.log

programdata/Mozilla/updates/72BA74B3052734C0/updates/0:
total 0

programdata/Mozilla/updates/72BA74B3052734C0/updates/downloading:
total 0

programdata/Mozilla/updates/A0D9F245A5B00C5D:
total 12
-rw-rw-rw-  1 RUBEN7 0   25 2021-03-12 11:13 update-config.json
drw-rw-rw-  3 RUBEN7 0    0 2021-08-18 12:02 updates
-rw-rw-rw-  1 RUBEN7 0 8147 2021-08-18 12:02 updates.xml

programdata/Mozilla/updates/A0D9F245A5B00C5D/updates:
total 8
drw-rw-rw-  2 RUBEN7 0    0 2021-08-18 12:02 0
-rw-rw-rw-  1 RUBEN7 0 3938 2021-08-10 11:22 backup-update.log
-rw-rw-rw-  1 RUBEN7 0  906 2021-08-18 12:02 last-update.log

programdata/Mozilla/updates/A0D9F245A5B00C5D/updates/0:
total 0

[therube]

If you were to set up a separate instance - and do not add any Properties, but do set the same Index settings, do the dates then coincide?

[harryray2]

I already have two instance's, one with file and folder exclusions, properties etc and a 'clean' instance without.

Same problem with both of them.

Windows does have a somewhat weird dating system...

[void]

I'm unable to produce the issue on Windows 7 or Windows 10.

Please try creating a file directly in a folder with the wrong time.

Does Everything and Windows Explorer update the folder date to the same time?

Would it be useful if I included the ini file from both instances?

Not at this stage.

I ask about fast rescan as I'm wondering if the current problem of folders not showing the correct DM: dates will affect fast rescan?

Fast rescan is only for folder/FAT/network drive indexes.
It looks like you are using NTFS indexes.
What is shown under Tools -> Options -> Folders, FAT and network drives?