Reliabillity bug in Everything

[ericgl]

Hi David,

I'm using Everything 1.5.0.1391a on Windows 11 x64 24H2 en-US.
I keep copies of files on several drives.
However, I noticed that sometimes Everything will display the wrong size and modified-date for a certain file, even though its hash matches exactly with the files on the other drives.

This happens a lot with Excel files, for example.
In Windows Explorer the file size & date do match.
I also checked the files with another hash application, and they are exact copies.
All drives have an NTFS file system.
I tried several times to rebuild the database, but that doesn't fix the problem.

It's only in Everything that the wrong date and size are displayed, falsely leading me to believe that the backup files are not the same, when they actually are. I iterate - this does not happen with all files, mainly with Excel files (and maybe with other files - I can't remember).

Please fix as soon as you can - it is a very fundamental issue.

Please see attached screenshot:

image.png (82.72 KiB) Viewed 3190 times

[horst.epp]

What you describe as a Bug happens, for example with files which are still open in applications like Excel.
The correct date and size will be available after the files are closed.

[ericgl]

No, none of the files are open.

And besides - where is Everything getting those false date and file size from?
That particular file in the screenshot is updated weekly on all drives, yet Everything shows it was last modified on October 2024 (~5 months ago).
It looks like Everything is keeping something in the database and not updating it.

I see that sometimes it also happens with ZIP and TXT files as well.

What's crazy is that other files are showing up correctly from that drive.
Not sure if this would help, but the Q: drive you see in the screenshot is a Samsung T7 portable drive (formatted NTFS).

[win32]

And besides - where is Everything getting those false date and file size from?

CRC is calculated on display-time. Dates are gotten from the saved index.
My guess is that you have added your drive as a "Folder". Try adding it as NTFS index or check your options at Indexes/Folders

[ericgl]

No, I have not added any drive as a "Folder" (the Indexes > Folders is empty).
Could it be because I always start a new Everything window as Administrator?

[horst.epp]

No, I have not added any drive as a "Folder" (the Indexes > Folders is empty).
Could it be because I always start a new Everything window as Administrator?

The normal and suggested way is to install the Service and let start the client with the start-up.
Never start the client as Admin, that's not necessary and gives problems.

[win32]

Your problem is certainly caused by file being open by other programs and index data not being updated.
Try disabling ntfs_open_file_by_id from advanced settings.
Have a look at void's post here: viewtopic.php?p=63598#p63598

[ericgl]

Looks like running Everything as admin was the problem.
I'm now running the client without admin privilege.
I will test some more over the week ahead.

[Herkules97]

Looks like running Everything as admin was the problem.
I'm now running the client without admin privilege.
I will test some more over the week ahead.

Could be a bug specific to your system, I have this for open files like "C:\pagefile.sys".

I vaguely have a memory of it being the case where EBV said one slightly older time while Bulk Rename Utility and Windows Explorer reported the correct newer times and maybe they weren't open files. But it could also be that I was either using folder monitoring or some other factor I no longer remember.

[ericgl]

Well, after testing for while on a couple of computers, I think the problem is solved.
I UNCHECKED Run as Administrator, and since then I haven't had the problem anymore, on both PCs.
Everything is showing all files with the correct file size and date, on all my disks.

image.png (42.46 KiB) Viewed 2866 times

[therube]

as Administrator

Reading through, I would not have expected that to have been the cause, but if it works...


---


Outside of that, I would have said...

Verify the hashes of the 3 file - outside of Everything
(HashMyFiles or CHK Hash Tool or similar.)

Verify the dates

Verify "MS"
As in MS has been known to do real funky stuff with particular file types (like .xls, but seemingly not with .xlsx?).

If (Q: is a) NAS
Some NAS softwares may "change the date" of files copied to it - if those files are the same (content?) of an existing file it replaces.

If (Q: is a) cloud
No telling what the cloud may or may not do or show...

If file sizes are not equal, hashes cannot compare (theoretically, at least).
(KB is not always a good indicator of "size", as there is rounding going on. But in this case, seems sufficient.)


Otherwise, something going on causing Everything to not see or record particular changes (& again, I'd think the "as Admin" to be odd to behave in that manner?).