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.
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.
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.
CRC errors when working with WinRar ZIP files
Hi. I am using two PCs - one at work with old version of PA (named 2009, I can check the exact version number on monday if that helps you) and no way for upgrades (corporate policy, will be explained later) and another one at home with latest version of PA.
Few weeks ago we were informed at work that PA is getting replaced with WR which is recommended to be used, while we may keep the old version of PA installed. And this is where the problem started. At work I am creating large backup ZIP archive (around 15 GB compressed) using Win Rar 5.00 x32 running under Windows XP Pro x32. Next I am copying it onto external USB HDD and getting home. I am copying it then from external HDD to my personal HDD. As always just to be sure everything went fine I run Test operation on this archive using PA 13.x. I got thousands of CRC errors. My first thought was that this file was corrupted while moving between HDDs. But that was not the case. I got my home HDD hooked to work PC and the Test procedure went fine using WR 5.00 and PA 2009 that I got there installed. So knowing the file is not damaged I’m back with my personal HDD to home. It seems PA 13.x is wrong claiming there are CRC errors. Just to be sure I have installed at my home PC trial version of WR 5.00 (x64, running under Windows 7 x64) and the Test procedure is completed just fine. I can extract every file from this archive and they are working fine after that. So I did upgrade from PA 13.x to PA 14.01.06 - still same situation, thousands of CRC errors while running Test procedure.
Looking closely into that case I was able to isolate the problem. PA 13/14 claims there is a CRC error only on files inside this ZIP archive that have unusual characters in their filenames. By unusual I mean common Polish national characters that can be found in Windows-1250 charset (e.g. Unicode #017A character). All other files can be extracted and working file when using PA 14.
Any fix for this? It’s weird that old version of PA 2009 doesn’t have this bug, but it could be related to new multicore ZIP engine that was introuduced somewhere between those versions…
can you send us one example archive but with single file or something like that? I cant tell you whats wrong before checking it out.
WR has pretty wonky ZIP support, it is better to use RAR which you can open with PA. They have multicore support for RAR, I dont think they do for ZIP, so it will be faster that way.
We always have to add workarounds for various different archivers that dont implement perfect support for zip specification.
you can send archive to support at conexware dot com… much appreciated!
Hello, I attempted to reproduce this by including the Unicode #017A character in a filename and creating an backup archive via WinRar 5.00
Tested in latest PowerArchiver and it worked fine.
If you can, please do send over a sample archive to support at conexware dot com and we will take a closer look