"Error running more C:\....

[ArnieR]

Running Windows 11, on both 12.28 and 12.38, I get the following error message when executing exiftool(-k):
Error running more C:\Users\ARnotAdmin\AppData\Local\Temp\par-41526e6f7441646d696e\cache-exiftool-12.38/exiftool_12.38_doc.txt

If in a Windows Command window, I type: >more C:\Users\ARnotAdmin\AppData\Local\Temp\par-41526e6f7441646d696e\cache-exiftool-12.38/exiftool_12.38_doc.txt
I get an error message:  Invalid parameter - /exiftool_12.38_doc.txt
However, if I change the last forward slash to a back-slash:
>more C:\Users\ARnotAdmin\AppData\Local\Temp\par-41526e6f7441646d696e\cache-exiftool-12.38\exiftool_12.38_doc.txt
Then the correct file opens in a text file.

Somewhere, somehow, the path to the exiftool_ver_.txt  is not being created correctly within the tool, me thinks.  The slash before the text filename should be a backslash, not a forward slash.

I don't think it has anything to with permissions of the file or path as I have seen in other posts.
Not sure what to try next to get around this problem.

[Phil Harvey]

Interesting.  I don't know why this hasn't been reported before since ExifTool has been doing it like this for well over 10 years.

But I'll look into using backslashes.

- Phil

[Phil Harvey]

I'll add a patch to ExifTool 12.39 which should fix this issue.

- Phil

[obetz]

I don't think it has anything to with permissions of the file or path as I have seen in other posts.

IMO you demonstrated that this is no permission problem.

Not sure what to try next to get around this problem.

it would be interesting whether this is caused by Windows 11 or by a specific setting of your system.

Forward slashes in the middle of a path are allowed at least up to Windows 10 and I didn't read anywhere that Win 11 behaves differently.