When the function for testing archives is invoked via the shell context menu (PowerArchiver > Test) then all the files in the archive get extracted to the current folder.
The test dialog reports as many errors as there are files in the archive but it fails to give any hint as to which files are supposed to be erroneous or what the nature of the problem might be. Comparing the extracted files to the originals shows no differences at all.
The .7z in question was produced with maximised compression settings in 7zip (taking forever but resulting in smaller archives than .7z produced by PowerArchiver with maximised settings). Therefore I wanted to see whether PowerArchiver can at least test .7z that it produced itself. Hence I had PowerArchiver convert a .pa with the same contents to .7z. There weren’t any errors reported but the resulting .7z contained fewer than half of the files contained in the .pa (137 of 366), so I scratched that test.
Performance is abysmal when testing via the context menu (e.g. almost 2 minutes for testing a .7z that 7zip tests in 4 seconds), but that is most likely due to the fact that the extracted files are written to disk. Testing the same .7z in the PowerArchiver GUI takes only 8 seconds but causes the mysterious appearance of a UAC dialog, as reported elsewhere.
The testing function is vital because PowerArchiver has a history of producing archives that it cannot unpack without errors or that do not conform to the respective file format standards (e.g. ZIP) so that other programs report them as erroneous.
The point of creating archives is that the files in them will most likely have to be extracted at some point. If the extraction cannot be guaranteed to produce correct results then the whole program is absolutely pointless. Actually, worse than pointless - it causes data loss and hence damage.
In PowerArchiver 2023 22.00.06 configuration, the option labelled “Start PowerArchiver 2023 Starter when my computer starts” seems to be redundant.
I am only allowed to change this option when PA Starter is disabled, and then it seems to be ignored.
When I enable PA Starter this option is forced to the enabled state.
I think it’d be good to remove “Start PowerArchiver 2023 Starter when my computer starts” completely. I’ve always found it confusing having both options.
Added later: However i don’t particularly want to use queue but I do like having the PAStarter icon in my tray area.
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.
PA 9.11.01 can't unzip pkzip files
I just upgraded to the new version and I can no longer unzip files created on my old dos laptop with PKZIP 5.0.
I can’t be sure this problem is new with the latest version since I haven’t used those files much for a few months but I’m sure whatever version I was using 6 months ago was working fine and I think I’ve probably unzipped a few things since then.
I’ve had to copy PKUNZIP to my XP computer to unzip them there.
Is this a bug or a new “feature” or is it something I’m overlooking?
manuangi last edited by
the latest version, though beta, is the 9.20.04, available through the update feature.
PA supports only pkzip 2.04g and higher specs. Long time ago, PkZip used implode method which is not supported by PA, nor I think it ever was.
I think you might still be able to create implode zip archives with some pkzip utilities but I am not sure.
sorry and thanks,
I just checked the pkzip version I used and it was 2.04g. I have 5.0 but somehow that laptop has the older version on it.
A few small archives will unzip. The rest start to and unzip a file or two or even several and then stop saying there was an unexpected end of the zip and that it was probably just the first part of a spanned archive. But it isnt spanned and PKUNZIP 2.04g unzips it just fine.
This isn’t a problem I can’t live with. I do have PKUNZIP. But it sure is going to be a hassle and I am sure I’ve never had this problem before and I’ve been using PA to unzip stuff from this laptop since I registered it a few years ago.
I went back to some of my backups and tried them. One in particular that I keep handy because it has some stuff I refer to now and then and I’m sure PA has unzipped it before but now it doesn’t do it. I’m not sure how long it’s been since I’ve done it.
For what it’s worth, PA is the only archiver I’ve had on either my XP or my Win98 machines for a few years so I’m really very sure it’s unzipped this file before with no problems.
You can send us an example (smaller) so we can test it out: supportREMOEVE@conexware.com. That way I will be able to tell you better what might be wrong. Actual zip support has not been changed noticably for a while.
Did you try repairing the file via repair tool?
Did you try repairing the file via repair tool?
No I didn’t since I know the archives are good when used with PKUNZIP. However I will and I’ll send one to you as well. I’ll try to do that tomorrow.
Check it out with this release: