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.
HELP! Shell integration completely broken.
-
Ok, first, the windows zipfldrs is completely broken, which is in no way the fault or even the responsibility of powerarchiver.
But I really NEED shell integration to unzip multiple ZIP files, doing them one at a time is not an option and neither is interacting with a GUI. I’m certainly capable of making the correct associations. However since the zipfldr method which powerarchiver attaches to is completely fscked, is it possible to use command line args instead? If so, what are the args? I have in mind something like the following(in the registry)….
powerarc.exe /x “%1”
The arg is obviously not “/x” since I tried it and it failed. What I want to achieve is the equivalent functionality of “Extract here” … which means unzip the files & close without any nags (as PA would do if zipfldrs worked correctly).
Please do not suggest fixing zipfldrs, it’s not possible without a complete OS re-installation (2 days work, many many apps), which this fix would help me avoid.
-
Welcome to PowerArchiver forum, Sigh!
first, PowerArchiver does not use Windows’ Zip Folders. PA creates it’s own association. you can repair it in Configuration > File Formats > Associate now.
Also you don’t need to reinstall windows to fix zip folders association. just right click any file > Send to >Compresses zipped folder… Then windows will ask you if you want to associate files. click Yes.
-
also, please make sure that you have enabled Shell extensions in Configuration > Shell extensions.
-
BTW: to extract multiple archives you can use the Multi Extract tool in PowerArchiver…
-
@NTFS:
also, please make sure that you have enabled Shell extensions in Configuration > Shell extensions.
Just to re-enforce this suggestion - if you choose the “Add as Submenu” option, then this should be available even when Zip files are NOT associated with PowerArchiver.
-
@NTFS:
Welcome to PowerArchiver forum, Sigh!
first, PowerArchiver does not use Windows’ Zip Folders. PA creates it’s own association. you can repair it in Configuration > File Formats > Associate now.
Also you don’t need to reinstall windows to fix zip folders association. just right click any file > Send to >Compresses zipped folder… Then windows will ask you if you want to associate files. click Yes.
1st, yes powerarcher uses the zipfldr REGISTRY ALIAISING LINK, not the zipfldr.dll.
2, I’m really fcuking pissed that you dumbed down my real problem with some simpleminded filetype association newbee moron idiocy.
The REGISTRY for the entire shell extension integration is FCUKED! I’m NOT asking you for help on that. It’s beyond you, waaaaaaaaaay beyond you.
What I want is the command line arguments for powerarc.exe …what are the command line switches? That’s all I want to know. NOTHING ELSE!!!
-
This post is deleted! -
@NTFS:
also, please make sure that you have enabled Shell extensions in Configuration > Shell extensions.
Yeah, IT’S FCUKING BROKEN IN THE FCUKING REGISTRY. Maybe you could suggest some magic “registry heal thyself” button.
I’ve run “regsvr32 zipfldr.dll” also run direct .reg scripts to restore all zipfldr functionality to its original condition, but to no avail, there is no shell integration on zipfldrs. When I install powerarchiver, it does all the right things, all the registry settings seem to be 100% correct, but guess what, STILL NO FCUKING SHELL INTEGRATION MENU. If it doesn’t work with zipfldr, just how the fcuk do you think it will work with powerachiver, which uses the same registry attachment technique as zipfldr.
If powerarchiver used actual command line arguments, then I could restore shell integration, but becuase powerarchiver attaches thru a registry key, {d03d3e68-0c44-3d45-b15f-bcfd8a8b4c7e} to be specific, shell itegration will not work.
So what are the command line args to powerarc.exe?
That’s all I want to know, nothing more, nothing less.
-
Just to re-enforce this suggestion - if you choose the “Add as Submenu” option, then this should be available even when Zip files are NOT associated with PowerArchiver.
Duuuuhhhh, NO FCUKING censoredcensoredcensoredcensored. But it does NOT.
That whole registry mechanism is totally fcuked. It’s beyond hope, totally not even a consideration at this point. I don’t want help with it, I don’t even want to mention it again.
All I want to know is the powerarc.exe command line switches. If I had those the rest would be a frickin cakewalk.
-
For command line use please try PowerArchiver Command Line:
http://www.powerarchiver.com/pacl/
It is free to registered PowerArchiver users.It contains all the documentation you need.
-
but here is what you want:
ShellExt Command line args for powerarc.exe:
Extract to…: -et
Extract here: -e
Add to archive…: -aZIP
Add to FileName.zip: -aZ -
Duuuuhhhh, NO FCUKING censoredcensoredcensoredcensored. But it does NOT.
That whole registry mechanism is totally fcuked. It’s beyond hope, totally not even a consideration at this point. I don’t want help with it, I don’t even want to mention it again.
All I want to know is the powerarc.exe command line switches. If I had those the rest would be a frickin cakewalk.
you should be a lot nicer to people trying to help you deal with your issue. NTFS has correctly answered to your issue (-e).