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?
I think PA just blue screened my Vista x64 SP1 PC
-
Had been using default classic skin for a longtime so I decided to change it to the modern skin. Didn’t like the skin so I proceeded to go to the skins options and there were two others listed MyPA and Longhorn. Changed to Longhorn and PA suddenly crashed. Any attempt to reopen PA just caused an instant “This app stopped working” message from Vista. I then decided to go to the PA program directory and delete those two skins hoping that would cause PA to revert to default skin. As I was clicking through the directories, I noticed that my sound as screwed up as in static filled and the “click” sound effect was instead the “stop” or “crash” sound effect instead. Figured it was time for a reboot so I went to the start menu and selected to restart the PC. Within 20 seconds I got a blue screen. Powered down the PC and cold booted it and got a windows recovered from a serious error message. Immediately deleted those two skins and got PA to start again, but this was very troubling. This Vista install isn’t 3 months old and I had no issues up until this point. Using latest PA 2007 build, btw.
****** I tried to repro on an XP PC and although I didn’t get it to crash, there are definite problems with those two skins. If you switch back and forth between them, they will glitch up. It will for example show the MyPA skin even though it clearly shows Longhorn skin as being checked. Those skins should be removed from the installer if they’re not going to be updated. TBO, neither one of them are that great, especially LH.
-
Thanks Denzilla,
Im sure one of the developers will get back to you with regards to this issue. In the mean while can you provide a bit more information of your system specs of which this issue occured. ie, CPU, RAM, Vista Version ie Ultimate, Home etc… also if possible any programs that were runing as well.
Can any other users who own Vista try and replicate this and report it please? This will allow PA to gain an idea to the overall impact to other users.
-
I’m unable to reproduce this on vista x86.
Windows 11 Pro ENU x64
Intel Core I7
32 GB RAM -
Just tried it on Vista home premium 32 bit and could not reproduce.
What version of PA are you using ? as there was a problem with these skins in an earlier version as posted HERE
-
I could be a specific problem with Vista x64, SP1 or a combination of the two. My hardware:
Asus M2N-X motherboard
A64 X2 4400+
2GB Corsair VS DDR-667
Sapphire Radeon HD 3450 PCI-E
Seagate 250GB SATA II
Vista x64 w/SP1I had no other apps open at the time other than a few things in the systray (KAV7, APC powerchute, ATI control panel)
-
I could be a specific problem with Vista x64, SP1 or a combination of the two. My hardware:
Asus M2N-X motherboard
A64 X2 4400+
2GB Corsair VS DDR-667
Sapphire Radeon HD 3450 PCI-E
Seagate 250GB SATA II
Vista x64 w/SP1I had no other apps open at the time other than a few things in the systray (KAV7, APC powerchute, ATI control panel)
skins should not be used in x64… it is our error, it was supposed to be disabled when it detects x64.
so as an workaround, dont use skins in x64 :-).
-
skins should not be used in x64… it is our error, it was supposed to be disabled when it detects x64.
so as an workaround, dont use skins in x64 :-).
Just glad to hear there was an actual reason for the blue screen. Its actually the first blue screen I ever had. Seen them on other people’s systems, but never my own. Rather scary :p
