-
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.
Slow startup under Windows 7
-
I am experiencing a very slow PowerArchiver (latest version) startup, under Windows 7 64-bit. The issue is sporadic. It seems that once PowerArchiver loads (after a several second delay), then I no longer have the problem (at least for a while).
This isn’t a normal slow-program startup. My system is running super fast and I don’t have this issue with any other programs. I’m running ESET Antivirus, but I don’t think this is the cause since, as I say, after the first PowerArchiver load, it loads new ZIP files very quickly.
The startup speed doesn’t seem to be related to the size of the ZIP files. It appears to be PowerArchiver itself which is slow to start for the first time.
Any ideas?
Thanks!
-
Hi Logidelic,
Your 100% correct that doesnt sound rite. I sometimes have a slow start up on the 1st fresh boot but after that everything runs smoothly.
Can you share your system specs?
This is something i would do;
1. Uninstall PowerArchiver including Patchbeam and the Virtual Driver.
2. If you have any system cleaning products on your computer such as ccleaner do a full clean including registry, then reboot your system.
3. Then download the latest version and install again.
Dont forget to backup your current configuration for PA , But on install “dont” import them untill you have tested the speed on a fresh install.
See if you notice a difference on a complete fresh install without any personal configurations.
After than then configure your product, personally i would do this from scratch.
I know this sounds like a pain in the backside, but it will help us establish multiple area’s such as is it an upgrade issue, background tasking, registry issues, computer resource etc
Thanks.
-
First impression after uninstalling and re-installing is that it solved the problem! Seems weird to me, since the system was very clean and there was no reason for a dirty install, but there you have it.
This is just after two tries, so will followup further if I notice anything new.
Thank you!
-
maybe some setting? If it happens again, try saving config via Options and see if setting defaults help.
-
First impression after uninstalling and re-installing is that it solved the problem! Seems weird to me, since the system was very clean and there was no reason for a dirty install, but there you have it.
This is just after two tries, so will followup further if I notice anything new.
Thank you!
Your welcome! It has happened from time to time , but you can almost resolve every PA issue with a clean install.
Like Spwolf suggested, if this happens again send the guys at support the specs, and a copy of your config. This can aid them further.
-
Just an update: Unfortunately I spoke too soon. Seems like it didn’t really change anything afterall. I will send my config to support as suggested, but just a few more clues:
- After a slow startup, PowerArchiver will start very quickly at subsequent starts, BUT….
- This only lasts for an unexplained amount of time. For example the next day (no reboot!) I’ll have the exact same problem again.
- When the startup is slow, it’s close to 15 seconds before PowerArchiver shows up. This happens no matter how I bring up the UI (ex. right-click on a file and choose Extract Here… 15 seconds before it starts)
-
it looks like some antivirus thing - can you Please try uninstalling Antivirus you use, and then reboot computer and try extract here for instance… shell should always be instantly started (or close to it).
thank you and I am sorry for the issue you are experiencing…
-
problem is that you cant just disable any AV, it still works, so only way to test for sure is to remove and try without it….
-
since someone has reported something similar now with Avast, please let us know if disabling ESET works or uninstalling (you can install later)… that way we can report it to ESET.
there might be some virus that had start of file signature similar to pa.exe and hence now they auto check pa.exe due to bad flag setting. This happens every 3-4 years and we report it to them and they fix that flag so it doesnt happen.
-
gonna try this out with these 2 anti virus programs and see if can get the same slow startup time
-
Tried this with Eset Antivirus version 6.0.314.0
Virus definitions: 8164Worked fine, starts as usual.
I noticed that the startup time was very slow when Eset was doing it’s Quick Scan.
Is it possible that a quick scan or any scan was being performed at the time of your attempted start of PowerArchiver?Go ahead and send over your reg settings (zipped) to support and I can take a look while I still have Eset installed.
And try to reproduce with your exact settings.Thanks!
