#699 Opening directory in Explorer opens tmp directory

[Dask]

When activating the option for automatically opening the extracted directory in the explorer after extraction, instead of opening the target I just get a tmp directory

[walter melow]

Same issue

[Giorgio Tani]

Does this happens extracting compressed tar files or in other specific cases?

In case of compressed tar files, e.g. a TAR.GZ file, the GZ compressed TAR archive is extracted in the temporary working directory (which can be set from options > settings), and then the TAR archive is opened for browsing.
Extracting the TAR content, the default output path - if not changed by the user - is inside temporary working directory, and will be opened after extraction if such option is flagged.

If this is not the case you are experiencing please feel free to add any other detail you find relevant to replicate the issue in the closest condition - e.g. what is the operating system in use, what is the path of the temp folder which is opened, what is the archive format being extracted, etc.

[Dask]

I'm mostly extracting .zip files, but with those it happens consistently.

The tmp directory opened has the following format:
C:\Users[USER]\AppData\Local\Temp\peazip-tmp

OS: Win10 21H1
PeaZip: 8.7.0

If you need any other info, let me know

[Giorgio Tani]

Thank you for the further information.

A couple of questions:

Does the extraction take place in the correct directory, regardless PeaZip opening a temp directory after extraction, or does the problem also affects the extraction stage?

Does disabling "Interactive extraction" option in Options > Settings > Archive manager (Extraction group) fixes or changes the issue?

Finally, as I was not able to replicate the issue on my Windows test machines, it would be useful to have the conf.txt file so I can test running your exact configuration.
If you want to sent it to my mail giorgio.tani.software@gmail.com you can find conf.txt file from Options > Settings > Advanced, which provides a link to PeaZip's configuration path.

[Dask]

Ahh, yes, disabling "Interactive extraction" actually did solve the issue!

[Giorgio Tani]

Thank you for the feedback, this narrows down the cases to test for the error.
With "Interactive extraction" option enabled, is the extraction performed to the correct path (so, the error only apply to opening the wrong output path after extraction), or is the extraction performed to the same wrong temporary path?

[Dask]

Sorry, the extraction always happened to the correct folder, even before. It was just the directory that was opened afterwards that was wrong.

[Melody Nelson]

I have this issue too, on 8.7.0 in Windows 11. It extracts to a correct folder, but instead of opening it, it opens the temp folder, which is empty by that moment. If I disable Interactive extraction, it works fine, I suppose because the temp folder isn't used then.

I mostly use default settings, except for open folder. I have this checked: Settings - Archive Manager - After archiving/extraction - Open output path when task completes.

Steps to reproduce:

1. Download some archive
2. Go to C:\Users\me\Downloads
3. Right click on archive - PeaZip - Extract here (smart new folder)
4. It extracts, but then opens C:\Users\me\AppData\Local\Temp\peazip-tmp which is empty.

[Giorgio Tani]

Hello, the issue is now fixed in 8.8.0 release.