Explore here option bringing me to wrong location

[wave-form]

This is odd.
I'm syncing some sub folder picture sets in a root folder to the same root folder on another drive.
After doing a compare, when I was choosing the option to explore the image file in the source location, FFS pointed me to "My Documents" folder in my windows 7 user folder. There are no pictures stored there. However, what's even more odd is this only happened to a few of the sub folders, not all of them. Everything synced fine but it's odd why the explore option is bringing me somewhere totally different then where my images were stored.

I've been using FreeFileSync for over 5 years and this has never happened. Using v6.13

[Zenju]

Could be related to Windows Explorer's 260 Char limit for file paths which FFS does not have.

[wave-form]

That makes sense kind of, but if the path is too long, the file names usually get truncated.
The path actually was not that long, about 12 characters for the sub containing the images, the image file names are only 8 and all the image-sub folders were in a root folder that is directly on the root of the drive. It's not a Char length issue.

Like I said, everything seemed to copy over ok. It was just odd why it was happening on one folder and not another. I wonder if it's because there was a comma (,) in the file name. Is that an illegal char?

[Zenju]

By default, FFS executes

explorer /select, "%item_path%"

Maybe the file path contains some character that breaks this command line.