Powerarchiver is dead no updates to fix bugs no new features, no communication and errors in program update system with scripting errors. Duplicate context menus windows 11 no fixes no updates
I declare that this is the last version.
From google search
AI Overview
Yes, that’s correct. UltimateZip was indeed a product of the same company that developed PowerArchiver, and it was essentially a rebranded version of PowerArchiver. It was discontinued and replaced by PowerArchiver.
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).
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
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?
Not handling multi-part .rar archives properly
-
v10.10.09
If you have a multi-part .rar archive which is using the ‘old style volume names’ i.e.:
my_archive.r00
my_archive.r01
my_archive.r02
my_archive.r03
my_archive.r04
my_archive.r05
my_archive.r06
my_archive.r07
my_archive.r08
my_archive.r09
my_archive.r10
my_archive.r11
my_archive.r12
my_archive.rar…and you right-click my_archive.r00 or my_archive.r01 (both file extensions are associated with PA) and choose to ‘Extract Here’ - PA just bombs out.
However, if you right-click my_archive.rar and choose to ‘Extract Here’ - PA handles that file extension fine and will extract the archive contents to the current directory.
Can you allow PA to do the same for *.r00 and *.r01 files?
-
it worked before… so we will check it out
-
v10.10.09
If you have a multi-part .rar archive which is using the ‘old style volume names’ i.e.:
my_archive.r00
my_archive.r01
my_archive.r02
my_archive.r03
my_archive.r04
my_archive.r05
my_archive.r06
my_archive.r07
my_archive.r08
my_archive.r09
my_archive.r10
my_archive.r11
my_archive.r12
my_archive.rar…and you right-click my_archive.r00 or my_archive.r01 (both file extensions are associated with PA) and choose to ‘Extract Here’ - PA just bombs out.
However, if you right-click my_archive.rar and choose to ‘Extract Here’ - PA handles that file extension fine and will extract the archive contents to the current directory.
Can you allow PA to do the same for *.r00 and *.r01 files?
hmm…v10.10.09???
-
10.10.09 is a test version of beta 2.
So it is not available via Update (at least not yet).
Check other threads if you must try it. -
10.10.09 is a test version of beta 2.
So it is not available via Update (at least not yet).
Check other threads if you must try it.I find out links…
It alpha version…
Why so complicated author do? -
I find out links…
It alpha version…
Why so complicated author do?alphas are not posted as betas until they become betas… so no, you wont see that version up on the site until we think it is ready.
-
Some more info to report about this:
If you have a 2-piece multi-part archive e.g.:
my_archive.r00
my_archive.rar…and you right-click my_archive.r00 and select Power Archiver 2007 > Extract Here, you’ll get an error message stating that there was a CRC error, continue?
If you do this with the my_archive.rar file it extracts the archive contents to the current directory, as expected.
If you have a larger multi-part archive and try to extract from the *.r00 or *.r01 file then PA just crashes without giving the CRC error popup.
It seems to not be loading all parts of a multi-part archive during extraction unless you begin with the *.rar file.
-
This should be fixed in latest version:
http://www.powerarchiver.com/test/release10/powarc1010.exePlease let us know…
thanks!
-
I tested extracting from both the *.r00 and *.r01 file from a couple different multi-part archives and it worked ok. Before this was reproducible every time so this seems to be fixed. I’ll advise if I notice it again and give details. Nice job on the fix btw.
