-
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.
Real slow UX / PA 2017
-
I am using latest version 17.00.83
OS : Windows 10 Pro Creators Update x64
Security App : Emsisoft Internet security.
On a laptop with decent specs with 12 GB RAM and i7 processor with SSD drive. Photoshop works faster than PA.Please watch the screen recording : https://puu.sh/wFqlj/1d69c0450a.mp4
The UI opens and closes too slow. Shell extraction is slower than winrar.
Switching between tools is real slow. Opening and closing configuration window is slow too. -
I would recommend opening up task manager (right click on task bar, select task manager) so we can see what’s going on while opening/selecting different tabs. Also, after opening task manager do the following;
Options - Always on top
View - Update speed highSo before opening PA2017, open the tm first and select the process tab. Than look at the CPU% and disk% to see what’s going on.
-
@delixyr i can confirm that closing part is due to emsisoft scanning our registry save at close. We will try to work around this in the future. Same goes for config when you click on OK, it saves info to the registry and it seems emsisoft is scanning all the changes first.
as to the changing interface tabs, this should not be so slow, I dont see why should AV influence this but I can get slow times with emsisoft too there… I have to time it to see before/after emsisoft to make sure it is the part of the problem.
Your video is very helpful, thank you for making it. We apologize for any inconvenience you are experiencing.
I will update the thread when I time it on my own laptop here.
-
@delixyr Quick tests:
Emsisosft ON
- Start PA 2.40s
- Go to FTP 6.27s
- Go to Archive 7.60s
- Open Config 1.40s
- Close Config 10.59s
- Close PA 4.20s
- Extract shell 0.95s
Emsisosft – whitelisted – no changes
Emsisosft - uninstalled
- Start PA 2.40s
- Go to FTP 1.44s
- Go to Archive around 0.5s or faster
- Open Config 1.30s
- Close Config 2s
- Close PA 0.5s or faster
- Extract shell 0.95s
So when it comes to closing config, closing PA and changing between FTP and Archive modes, there are massive differences between Emsisoft being ON or OF. I could not see any difference in shell extract and with AV on, my laptop cpu is likely at full speed before PA starts so it starts a bit faster.
edit: here is video with windows defender on (not emsisoft):
http://snap.ashampoo.com/qQRqreSq -
@delixyr to see if shell extract speed can be faster, can you go to HKCU\Software\PowerArchiverInt - export it first and then delete complete PowerArchiverInt key from registry.
Then try starting PA and see how fast is it, and after that see extract here and if there is any difference?
after that you can restore your settings of course by doubleclicking on saved .reg file. Thanks!
-
@spwolf I have disabled all components of EIS and saw no noticeable changes. And PA is the only app that is slow. I tried after reboot too. I dont have much apps or services running in background. 75% of my RAM was free and only 10% of CPU has been used. I will try the other solutions mentioned and report my observations later today.
-
@delixyr yes, disabling does not work, it keeps working in the bg, but thats the same for all AVs. Only uninstall will clean it properly. Obviously we dont expect you to uninstall AV you paid for.
We will write them an email, Kaspersky or NOD used to do this 3-4 years ago, but we got them to whitelist PowerArchiver main exe so it works properly. This is for closing issue where PA writes many entries to registry. No other AV ever slowed down file listings.
-
@spwolf As far as I know EIS used BitDefender engine.
-
@delixyr we got pretty fast response from Emsisoft. They are looking into fixing it permanently, but in the meantime you can disable PA folder monitoring and it will work properly:
Good company, fast support, kudos for them. Lets hope they can fix it for other users fast too.
-
Yeah now it has gotten way faster :) . And yeah their customer support is very responsive and supportive. And great security app. Hope to have PA a really swift utility app. … precisely the context menu / shell extraction.
