-
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 errorsIs 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.
-
PA 21.00.18 running on Windows 7 64 bit.
I made a big .PA file and thought I’d check it was made correctly with Menu / Actions / Test.
Discovered:
a) PA always issues a UAC prompt to do this!
b) PA always says there are many errors in PA files. -
Clipboard02.jpg
See the, supposedly, blank space where the green box is? It’s like that in Modern Light theme too. I can toggle it, but it’s missing text or shouldn’t be there I guess?
Thanks :)
-
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.Features implemented:
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.
thank you!
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
76e97ab9-8d75-4175-9ce8-446500031f38-image.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.
Power Archiver not including files when creating zip.
-
I recently installed Power Archiver 9.11 on a fresh install of XP SP2 to try it out. I really like the program, but don’t seem to be able to trust it.
For some reason, when I select a group of folders to compress (each containing a few small files), Power Archiver creates a zip file containing the folders in question, but none of them contain the actual files. The first time it happened I thought I’d just made some sort of error, but now I have a group of folders on which I can constistently duplicate the problem. Yet any other groups of folders I try to compress seems to work fine.
I’ve tried moving the particular folder group to the root of the drive and compressing them from there, but it didn’t seem to make any difference. I have found that if I right click on the root folder (the one containing all the sub folders), then Power Archiver compresses everything fine. However if I navigate into the root folder, select all the sub folders, then right click to create a zip file, Power Archiver creates a zip file containing the folders but none of the files they contain. There’s about 65 folders that I’m trying to compress, but they all contain pretty small files. I’ve even tried just selecting a few of them but the problem still exists. What I’m finding really hard to understand is that I can consistently reproduce the problem on this one group of folders, yet for the moment everything else I try to compress seems to work fine.Hopefully I explained all that well.
Has anyone else experiences this behaviour?Thanks,
Darren -
Okay, just as I was hitting the submit button on the above post I developed a theory. I’ve tested it and now seem to think I’ve found the bug, but if someone else could test it out too that would be great.
The group of folders I was trying to compress were all named after the version of the files they contained. So each folder was called something like “Program.1.3.5”. I can only assume that the “.” in the file name is causing Power Archiver to treat the folders as files, and it therefore doesn’t look inside them. To confirm this theory I renamed a few of them, removing the version number so there were no "."s in the name. I then recompressed the group of folders and sure enough, all the ones I’d renamed contained files but none of the rest did.
So for now I know not to use Power Archiver, and I’ll have to walk away from the computer for a while so I can come back to it in a less distressed state, when hopefully I’ll be in a better frame of mind to sort out all the files I’ve lost since installing it. :-( -
the best thing you can do is share those folders with us, uploading them on the web, so that we may download them and look about the problem.
-
the best thing you can do is share those folders with us, uploading them on the web, so that we may download them and look about the problem.
There shouldn’t be a need for that. It’s a pretty simple bug to reproduce.
Just create a couple of folders. Call one “test.01” and the other “test.02”
Stick a couple of files in each folder. Now select both folders and compress them from the right click menu. The resulting zip file will contain the folders, but the folders won’t contain any files. Now rename the folders to “test” and “testing”. Compress them again and everything will be fine.I’ve uninstalled 9.11 and installed 9.1
Run the tests again and the bug is no longer present.Although……
I was testing the folders on the root of my C drive. When compressing them with the older version (9.1), it insisted in trying to include the hyberfil.sys file in the archive, even though it wasn’t selected. But that’s another story… -
There shouldn’t be a need for that. It’s a pretty simple bug to reproduce.
Just create a couple of folders. Call one “test.01” and the other “test.02”
Stick a couple of files in each folder. Now select both folders and compress them from the right click menu. The resulting zip file will contain the folders, but the folders won’t contain any files. Now rename the folders to “test” and “testing”. Compress them again and everything will be fine.YOU ARE RIGHT! :eek:
I could reproduce the bug.So, PA fails to include any files in folders named with a point in their name, but just when compressing to ZIP.
I tried to compress to other types like CAB, 7Z, BH and all worked fine.Using 9.11.01
-
Cheers,
Thanks for confirming it!
I didn’t actually check any of the other formats. I was using version 9.11.01 myself. It seems that’s the only version with the problem.Thanks,
Darren -
thanks - we will check it out!
