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.
Corrupted Run as…
I have a problem with PowerArchiver 2013, version 14.02.03 on Windows 7 64bit. When I want to run any desktop shortcut as different user or as an administrator nothing happens (there should be a pop-up window with enter credentials). UAC is on, all needed services are running. The same behaviour happens in start menu – recently opened programs (but only here). If I open \Start Menu\Programs\Accessories and run calculator as different user, pop-up window opens and I can enter credentials.I had previous version and i upgraded it yesterday.
Workaround is to uninstall PA but I dont want to do that.
- if I run as diff. user from Program files, it works
- I have another PC with Windows 8.1 Pro Eng and here it is also broken (if you right click the start menu a select control panel, task manager, file explorer…)
Thank you for your assistance.
Is it 14.02.03 or 05? 05 was yesterday?
It is version 14.02.05
let me add Run as different user to my computer and I will try it out
ok, so on desktop Win8.1 x64, right click run as different user (on any shortcut), seems to work.
I am assuming it is 64bit Windows?
If you could help us reproduce it, that would be great. I am not sure how can I run as a different user in Start menu, Win8.1… shift does not work?
in Windows 8.1 it is a different problem. Right click the start menu icon and click on control panel ( on this pc it does nothing). Also if i access the start menu and write cmd and right click it and select run as administrator, the cmd wont start. Problem in Win 8.1 has lower priority, lets focus on problem in windows 7, it has higher priority for me
can you save your PA settings, and send them to firstname.lastname@example.org. It might be related to some specific shell extension setting.
Also - these are x64?
Ok i send settings to support.
Yes both Windows are x64
thanks for sending your settings
testing this out today on our W7 x64 machine, will let you know the result
Thank you, I will wait for your answer
Can you please confirm the date of these files in your PA installation folder:
I verified the date of the required files:
POWERARC.EXE -Created: 12.March 2014 - 10:13:38
Modified: 12.March 2014 - 10:13:38
Size: 11 489 792 bytes
PASHLEXT64.DLL- Created: 6.January 2014 -16:22:06
Modified: 6.January 2014 -16:22:06
Size: 2 379 776 bytes
we were able to reproduce it on our W7 machines. it has been logged in our system andthe dev team will take a look.
thanks very much for your help and detailed report!
Thank you very much, I hope that the problem will be solved as soon as possible, since it strongly limits us
we have investigated this a bit - problem happens “only” when PA was never run on that user, so workaround right now would be to just run PA once.
We should be able to fix this for upcoming release. Thank you!
here is test release that should have a fix for this: