[Bug?] Copy/unpack to Windows dir using env vars?

[Helix751]

I tried to use env vars to copy a lib to the System32 folder, but TC doesn't parse/expand the variable name and thus complains that the path is incorrect.

Example:

Copy/Unpack to: %windir%\system32

TC shows the message:

The target directory:

current_path\%windir%\system32\%windir%
is not valid!

Is there a way to use these vars this way (with any file command)?

Also:

There isn't a reference for the env vars defined by Total Commander anywhere in the help file, except for a mention in the "What's new" section. Are there more variables than %COMMANDER_PATH% and the new v6.50 pseudo vars?

Thanks in advance.

[Lefteous]

2Villampiro
I can confirm this behavior - it seems to be a bug.

[ghisler(Author)]

Environment variables aren't resolved by most system functions - I have to add that manually to each function. Therefore not all functions will support them, sorry.

[Helix751]

Thanks for the info. Anyway, it would be nice to have these implemented at least for the copy/move/unpack/create dir functions.

This has been added to my [Req] list (here)