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?
Bug & more - Runtime error 217
-
Bug - random runtime error when extracting ZIP archives. Don’t know if it happens with other type of archives, but with zip files happens a lot.
More - PA can extract self-extraction zip archives but can’t explore them, only showing a file named “[NSIS].nsi”. Almost all free file archivers can do this.
-
Hello, please email support at support@conexware.com , so we can send you debug version… also send us an link to that SFX file as well so we can add better support.
We did not have any reports of this error before so debug version is necessary to catch the problem.
Thank you!
-
Please also send us your settings (Export option), make sure you .cab the .reg file so it can pass the filters… that will be very helpful! Thanks!
-
Reinstalled PA (repair) and the runtime error keeps appearing (random but with high rate).
Have been trying to replicate it in two virtual machines with Windows 8 and Windows XP (VirtualXPVHD from Windows XP Mode) but, so far, I couldn’t do it.
Maybe it’s related to my PC or OS setup (Windows XP SP3 32bits), but I don’t have any issue with other applications or file archivers. It only happens with PA.Update: It happens with all kinds of archives. I can replicate the error by doing the following steps:
1. Open any archive with PA. Drag and drop some of the archive files to an exctraction folder.
2. Do not close the PA window from step 1.
3. Select another archive using the Windows explorer or the PA explorer from step 1, and use the shell context menu option "extract to folder "
4. Loop 1-4Sometimes I don’t get the error in the first try and need to repeat the cycle. It happens almost every time in the second try. After getting the error, it will happen every time I repeat the cycle.
As I said before, it only happens in my system and I only have this issue with PA. Followed the same steps in the virtual machines, but I got nothing.
-
Here is the latest release:
http://www.powerarchiver.com/test/release15/powarc150106.exeemail us at support again to get debug exe which will tell us what is going on when error appears… thanks!
-
Runtime error persists with new version
Self-extraction zip explorer fixed–-Debug—
Replaced the PowerArc.exe with the debug version.
Every time I exit PA it ends with “runtime error 216” (ntdll.dll)
Replicating the original issue gives “runtime error 216” (ntdll.dll) instead of “runtime error 217” (kernel32.dll) -
send us a screenshot please… you dont get debugger? Are you sure you are using debug version? Thanks!
-
send us a screenshot please… you dont get debugger? Are you sure you are using debug version? Thanks!
The, on exit, runtime error 216 just happens since I replaced the original PA with the debug version (pa150105witheureka.7z). And yes, I don’t get the debugger log.
-
what happens when you click on click here in upper window?
-
what happens when you click on click here in upper window?
I get the following window (similar to the non debug version, when I get the runtime error 217):
