FYI the same thing happens with Windows Explorer and the same workaround fixes the problem: Add rustic.exe to the list of excluded processes.
I still find it very strange that whatever restic is doing causes the virus scanners to think files on the disk might have changed. Other programs can read every file in a directory without causing the virus scanner to run.
As I understand it, restic should be reading the directory entries and then calling the moral equivalent of fstat() on each entry. (1) This shouldn’t be interpreted as changing files by the virus scanner so it is strange.
- Calling fstat() on every scanned file is a known outstanding performance bug in the scanning code, but lower priority than the issues with restore or prune.