The Windows 11 context menu for PowerArchiver on normal files (to be compressed, etc.) is now showing multiple tiers with two identical menus. See attached captures of the issue:
Screenshot 2025-01-08 082909.png
Screenshot 2025-01-08 082935.png
Screenshot 2025-01-08 082953.png
Edition Windows 11 Pro
Version 24H2
OS build 26100.2605
Hello!
I’ve just created SFX-Archives both from ZIP and 7z-Archives and none has an Icon as it seems.
I use the new version 22.00.11.
Zwischenablage_10-22-2024_01.jpg
Basically I used powerarchiver context menus to zip up a folder then i used windows 11 own built in zip extractor via the context menu to extract all and this is where it throw up a fault. , I’m using windows 11 .
The file that was a problem in the zip that windows 11 could not extract was iva “babe” cotton.jpg
I know it has non standard quotes in it.
However I had winrar on the computer and tried the exact same method with their context menu compress to zip and then I extracted the file with windows own extract all context menu and it had no problems. This indicates that powerarchiver is doing something different with iva “babe” cotton.jpg compressing to zip.
Then I changed iva “babe” cotton.jpg to iva babe cotton.jpg and compressed it with powerarchiver and then tried it with windows 11 extract all and had no problems. It looks like powerarchiver is doing something to that one file that has quotes in it.
Please note that powerarchiver extracted both zip files with no problems, only windows built in zip extraction had the fault. Reason I’m letting people know in case they send zip files with special characters in files names to people who do not have powerarchiver.
When will a fix be implemented?
On installing the program I am getting the error message:
"Unable to execute file c:\Program Files\PowerArchiver\pashutil.exe
CreateProcess failed: code 2
The system cannot find the file specified"
This can’t be right!
I am using the latest official build of Windows 11
Buttons are not properly aligned on About screen.
about window.png
Buttons not aligned on configuration window.
configbuttons.png
New version:
PowerArchiver 2023 - 22.00.10:
Download:
https://u.powerarchiver.com/pa2023/powarc220010.exe
New build for some bug fixes and issues - full list to come with new update. Please test and see if you have any issues.
Thanks everyone for your assistance!
New version:
PowerArchiver 2023 - 22.00.11:
Download:
https://u.powerarchiver.com/pa2023/powarc220011.exe
New build for some bug fixes and issues - full list to come with new update. Please test and see if you have any issues.
Thanks everyone for your assistance!
Just tried using the Modern (Windows 10) Icon set and seeing a few missing icons in both PowerArchiver Burner and PowerArchiver Encryption screens . They are all there in the Minimalistik icon set and the only difference I can see is the former is blue and the latter grey. In version 22.00.9
powerarc_2023-09-18_17-00-19.png
powerarc_2023-09-18_17-01-05.png
Hi everyone, some good news about PowerArchiver… I’ve managed to get in touch with the original developer of PowerArchiver, Ivan Petrovic, and he has confirmed that the product is not dead or abandoned, in fact it is still very much alive! There has been a hiatus over the past months for various reasons, but that we should expect to see stuff coming through in the coming months (hopefully the next 2 months).
I had a large .tar file (a backed up WSL) and I want to delete a few directories and their contents from it using PA2023.
PA just destroys the whole archive as soon as I try to delete a directory, leaving it in a state where PA2023 won’t even open it any more.
I tried several times and also tried compressing it to .tar.xz instead - same result.
This should either actually work, or it should say operation not supported and do nothing.
Hello!
The regular version of PA 2023 is out for over 6 months now, but there is still no sign of the portable release.
(When) will there be one?
Thanks!
Hello!
Is there currently no portable version of PA2023 available?
(When) do you plan to release one?
Thanks!
Win 11 64 bit
I have some archives which have been encrypted, using the encrypt option either in pbs or when interactively creating a zip. When I open these, and look at files, I am asked for passwords, which I know, and then can view items or decrypt the files in the archive (tools>decrypt files).
However, when I use the Actions>Remove Archive Encryption (whether using the same zip or asking to write another), the routine shows progress bar to the end, but then just hangs i.e. “OK” never activates. All process information shows this stalled/hanging.
What can I do to sort this out?
For example:
Download this ZIP file: http://dslstats.me.uk/files/dslstats32W-6.5.zip
Everything in the ZIP file is in a directory “dslstats32W-6.5”.
However when I extract using right click “Extract Here” the name of the directory created is “2W-6.5” !
I am running PA 22.00.09 on Windows 11. I have seen the same happen with some other kinds of archive too.
If I compress a folder to a .pa using right click, Compress to folder.pa and use the new Windows 11 menu then the Options, Configuration, Miscellaneous, Use normal relative path setting is always enabled.
But I like this option disabled so I have to use the old style menu in order to get PA to compress a folder in the way I wish.
Solved Open with... broken for filenames with spaces
-
Hi, long-time user of PowerArchiver here.
I noticed that some time ago the “Open with…” functionality broke for files with spaces in the name. Tested with latest PA2017 (64bit) on Win7.The issue is that the argument isn’t passed as a single string to tools, so for instance trying to file “My Text File.txt” using “Open with…” a tool located at C:\Program Files\Tool\My_Tool.exe will try to open the following files:
%TEMP%_PAnnn\My
%TEMP%_PAnnn\Text
%TEMP%_PAnnn\File.txtBasically, the file name needs to be enclosed in double quotes for this to not happen, so tools are called “%TOOL_LOCATION%” “FILE_LOCATION%”, e.g. “C:\Program Files\Tool\My_Tool.exe” “%TEMP%_PAnnn\My Text File.txt”
Thanks in advance,
Robert
-
Hi @FreakRob
Thanks for the details.
I’ve attempted the “Open With” function on file with spaces.txt and it opened properly in notepad.Which Tool are you using so that we may test with it and also, are you getting an error message when attempting to use the “open with” function on filenames with spaces and mentioned tool?
Also, which format are the archives in? I have tested with .zip and .pa
Let us know and we will look into it.
Thanks again!
-
Hi Mili,
Notepad is a bad test case, as it by default attempts to open multiple command line arguments as a single file.
I personally experience the problem with applications that allow multiple files to be put on command line. Notepad++ will actually guess, so not a good test case. I notice this with 010 Editor (a hex editor) when I examine zipped binaries that have spaces in their names.I tested .zip and .7z and both had the same issues. I doubt it’s related to the file format as this seems purely a PowerArchiver UI/logic issue.
For testing you can replicate the issue with the following batch file and zip file:
https://mega.nz/#F!4jA0nQjA!7ev5QS3gOsoH95_KG6W-xQI just noticed that the error does not occur when initially selecting “Open with…” --> “Choose Program…” – probably because Windows handles the arguments correctly. The error only occurs when using the shortcut that is generated afterwards directly in the “Open with…” menu.
Initially, “Open with…” --> “Choose Program…” will show the correct and expected result:
Using the generated shortcut it will show that the argument was not enclosed in double quotes:
This should illustrate the bug enough to reproduce and hopefully fit it.
-
many many thanks for the details @FreakRob
we have reproduced and have logged the issue in.we appreciate the assistance!
-
@FreakRob Thank you for your report. Please check latest release:
https://forums.powerarchiver.com/topic/5747/fast-ring-powerarchiver-2017-17-00-67-68-69-70-71-73It should work now. Please let us know. Thank you!
-
@spwolf I just tried it and it works. Many thanks!
-
@FreakRob thanks a lot. 2 more bugs and free license or extension, just a reminder!