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.
PowerArchiver crashes when decrypting Rijndael AES 256bit.
When descrypting two different encrypted files (with Rijndael AES 256bit), I get PowerArchiver crashing with the same message:
Access Violation at address 027C2E87 in module ‘PAISO.DLL’ read of address 00000000.
PowerAchiver version 9.63.02. My CPU is Core 2 Duo, and I am running Windows Home edition (32bit).
what are the contents of pae archive? (what kind of files). And what is the file size?
One file is ~ 85MB, another ~ 376MB. There is only one file in each encrypted archive. Encrypted files are binary, not text files.
rar. Does encryption algorithm care what format the encrypting file is?
rar. Does encryption algorithm care what format the encrypting file is?
depending on what options you are using, it might be automatically extracting archive as well.
I cant reporduce this issue easily. Can you please let me know how did you encrypt the archive (from where and what options) and how are you decrypting it?
I use shell extension both - to encrypt and decrypt. My moves:
1. Select a file to encrypt with right mouse button. choose Encrypt.
2. Change method to Rijndael AES 256 bit (default was Rijndael 128bit).
3. Check “Delete original file after encryption”.
4. Check “Hide filename”.
5. Leave “Create self extracting file” unchecked.
6. Enter password. My passwords are above 30 symbols in length. Yes, I know, I am too paranoid :)
Passwords for files I get PowerArchiver chrashed are similar. I have encrypted one more(third) file with self extracting option turned on - it decrypts correctly.
To decrypt I use:
1. Click right mouse button on encrypted archive. Select “Extract to c:<path to=”" default=“” directory=“” for=“” archive=“”>
2. Enter password.</path>
One strange thing. I just tried to encrypt ~135 MB file with the same password I used in one of those archives, which cannot be decrypted without crash. But when I click with the mouse right button on it - it says : “Decrypt to c:\blablabla”, not “Extract to c:\blablabla” as I see in those two archives I am not able to decrypt successfully. Is this significant?
I was able to successfully decrypt both files using this procedure:
1. Start powerarchiver.
2. Do “Open” and browse to encrypted file. Open it.
3. After the “enter password” dialog appears, close it (if I enter correct password, PowerArchiver starts decrypting it, and it fails. I can see that, because after some time the label “Decrypting file….” with the progress bar in the status bar disappears, and the list of files inside opened encrypted archive is empty).
4. Now I can see the file I need to decrypt in the PowerArchiver window. I select it, and click the “Extract” icon in the menu above, enter correct password, path to decrypt the file to, and voila - decryption successful.
thanks, we will look into it…