Extracting full pathnames from logs

[garrwill]

We are using the v10.6 donor version of FreeFileSync and we have a process to analyze the logs after they are generated in order to keep track of possible anomalies.

We are usually able to reconstruct exact pathnames for any questionable files with the help of "Synchronizing folder pair" log entries.

However, some types of anomalies, such as "files have the same date but a different size", often (if not always) precede any root-relative folder references and themselves contain only partial pathnames.

Other than testing for the existence of such pathnames as produced by concatenating FolderPairs from the *.ffs_gui file with the partial path (with potentially ambiguous results), is there a more certain method of determining full pathnames of files referenced in the logs?

[Zenju]

I've aggregated the conflict items in groups by base folders and prepended the base folder pair like:

The following items have unresolved conflicts and will not be synchronized:

Folder pair: C:\Source <-> E:\
subfolder\file1.txt: Both sides have changed since last synchronization.
subfolder\file2.txt: Both sides have changed since last synchronization.
subfolder\file3.txt: Both sides have changed since last synchronization.

Folder pair: D:\Source <-> F:\
subfolder\file1.txt: Both sides have changed since last synchronization.
subfolder\file3.txt: Both sides have changed since last synchronization.

You can check out these changes in the latest beta:
https://www.mediafire.com/file/ej8e4bm9hcbhejy/FreeFileSync_10.7_%5BBeta%5D_Windows_Setup.exe