W10 Pro 22H2 - 64 -bit
PA 22.00.06 (PA 2023)
It has been the case with previous versions of PowerArchiver, but I had hoped that the latest might behave differently. Not so, I’m afraid.
I have, for various obscure reasons, created a few .pa archives, mainly in the hope that they will save me some more space. From time to time, I use the “Test” option to check that important archives are OK and uncorrupted.
With every .pa archive I’ve tested, the process runs through OK but then reports that there are errors. This is always the number of files in the archive e.g. if 11 files, then 11 errors reported.
In the .pa, I can:-preview the files (usually PDF) extract some or all files and look at or use them convert the .pa to a .zip or .zipx archive, which then works fine and tests without errors
Is it the case that the Test routine isn’t designed for .pa archives, or is there another reason? Although the .pa seems to function properly, despite the test reporting errors, I would like to be sure that every .pa is OK and not “broken”.
Some of the .pas are quite old and produced with earlier PA versions (they are truly “archives”). If I extract all the files in the old .pa, create a new, fresh .pa and add back the files to that, then test the new, no errors (at least in the .pa I’ve tried this on) are reported. This would suggest a mismatch between old .pas and newer versions of PA itself.
Dear @Alpha-Testers and all of our users,
time has come for testing of PowerArchiver and PACL for macOS.
Please let us know here if you have Mac and can test latest builds.
PowerArchiver 2020 - tabbing, opening, extracting, adding, testing, favorite folders, support for multiple languages, opening via Finder, explorer mode, installer.
PACL 10 - support for most formats and features in Windows version.
Upcoming: Tools such as archive converter, batch zip, multi-extract.
To start testing, please sign up here in this thread, and we will send you latest build.
Ashampoo_Snap_Wednesday, November 20, 2019_12h54m56s_008_.png Ashampoo_Snap_Wednesday, November 20, 2019_12h55m05s_009_.png Ashampoo_Snap_Wednesday, November 20, 2019_12h55m14s_010_.png Ashampoo_Snap_Wednesday, November 20, 2019_12h55m30s_011_.png Ashampoo_Snap_Wednesday, November 20, 2019_12h55m39s_012_.png Ashampoo_Snap_Wednesday, November 20, 2019_12h55m49s_013_.png Ashampoo_Snap_Wednesday, November 20, 2019_12h56m00s_014_.png Ashampoo_Snap_Wednesday, November 20, 2019_12h54m43s_007_.png
For some reason, the PowerArchiver functions in the Windows 11 context menu no longer work after the last Windows Update. Only the functions in the classic context menu function as they should.
I’ve tried uninstalling PowerArchiver and using RevoUninstaller to remove all bits and pieces that were left behind and did a clean install of PowerArchiver, it didn’t fix the issue. Other items in the Windows 11 context menu work.
I installed powarc-macos20001.dmg and I am attempting to create a password protected zip file. When I create the zip in the UI it doesn’t write the file to the destination folder. No error message is displayed. The PA app has full folder permission. I’m new to Mac, but have been running PA on Windows for a long time.
Will there be a new version of the Mac version soon?
Hi! I came across an issue when I tried to uninstall PowerArch 2013. I got an error “The specified account already exists” which broke the process. I got the same error when I tried to install the current version, without uninstalling the previous one.
So I can’t uninstall and I can’t install PowerArchiver. Any suggestions? OS Windows 8.1 x64.
This appears to be happening again with the Power Archiver 2022 shell extensions.
When I have Use Explorer Shell Extensions enabled in Power Archiver Configuration and right-click on c:\Users\username\Start Menu, (hidden Junction file), File Explorer crashes.
I have version 21.00.15 (03/2022) 64-bit installed in Windows 10 Version 21H2 (Build 19044.1826).
The online update feature within the program suggests there is a later version than the ‘.17’ available on the web site. But clicking either download or update just reinstalls version .17.
Either there isn’t an update OR
the “download” and 'update" links should be repaired.
9.02 bug, cannot extract .exe's anymore
Since 9.02, say if I download something like a display driver, I cannot extra the .exe anymore, however with WinRar I can.
TBGBe last edited by
In general, extracting from sfx (tried with Zip and 7z exe) files works for me.
Can you give more information :-
Does this problem occur with all sfx (exe) files?
When downloading, are you saving to disk first or trying to “open” immediately ?
What format has the exe been compressed with?
Can you provide a link so it can be tested?
Go and download the latest ATI drivers from www.ati.com on the front page. Save them to your HD, then right click and go extract here, it will give you a “invalid archive error”.
TBGBe last edited by
I downloaded WinXp version of “tv-capture-wdm-6-14-10-6246.exe”
This can be opened with 7zip and WinZip - but not PA :confused:
Thanks for confirming, this is a pretty bad and annoying bug. I hope it can get resolved soon.
It is not an bug, we removed the support for some SFX’s because new CAB sfx support had some issues, and we will not put it back in until they are solved. We reverted back to the pre-9.00 support, so all SFX’s that worked then, will work now as well.
thats a bad idea it might have some issues so do all file types nonme are perfect. if you don’t add this support back you will lose some people who require this support. You have 7zip support but 7zip is forever changing and you have winrar support but that is a little buggy due to winrars dll so why take the sfx support off for these type of files as it is stupidto do so i personally would of had a warning message wused when trying to access these file types instaed. personal choice.
Please read my post carefully - support was moved from certain CAB SFX’s not all of them, and basically what happened was it would make browsing CAB SFX’s show error msg’s all the time, and that happened for ALL CAB SFX’s - this also included WinXP SP2, which was reported on these forums month ago. You could not browse that file and now you can.
I will close this thread and will post when we update the CAB SFX support again.