-
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.
SOLVED PA 19.00.51 / Access Violation
-
Hi,
I’m testing the new version.
My test system is a VM with Windows 10 1903 x86.
I’m trying to create an archive via context menu. ZIP is working fine, but with 7z and PA format, I get an access violation:
The archives seem to be created fine.
-
Hey @BigMike
How exactly are you attempting to create the 7z and PA archives when the error occurs?
We’ll attempt to reproduce using the same steps -
Hi,
it happens with any file on the desktop. I’m simply right clicking and then “Compress To 7z” or “Compress To pa”.
I noticed, that this won’t happen if the file is located in other folders (I tried a network share). I’m using German localization. -
@BigMike said in PA 19.00.51 / Access Violation:
Hi,
it happens with any file on the desktop. I’m simply right clicking and then “Compress To 7z” or “Compress To pa”.
I noticed, that this won’t happen if the file is located in other folders (I tried a network share). I’m using German localization.did you have the same issue with .50 or is it something new? Thank you!
-
Actually, I don’t think, I*ve tried this with version .50, so I can’t tell if it’s new or not.
-
@BigMike check with .57, not sure if anything changed but there were plenty of changes:
https://forums.powerarchiver.com/topic/6189/fast-ring-powerarchiver-2019-19-00-51-54-57 -
Still crashing here in my test VM, but if you can’t reproduce it and no other people report similar problems, maybe something is wrong with my VM!?
-
Hi BigMike,
If you can enable debug logging for your VM and provide the logs of the crash this would be useful.
However, these two Module error handlers refer towards .7z and .pa modules, and the fact that you are able to use the application to Zip without error points towards a conflict in the registry where the DLL’s are concerned.
As such, you are going to want to identify in the logs the DLL’s By name and location that are causing this 1st, and the logging will help with that.
But my feeling would be you try to de-register the following DLL’s , then reboot your VM and try. (The best way is to check the logs, find the actual dlls and de-register them) But we can try the good old fashioned “go by experience and hope for the best” way too :)
C:\Program Files\PowerArchiver
7z.dll
7z64.dll
pa.dll
pa64.dllKind Regards,
RJWaring -
Hi RJWaring,
regsrv32.exe /u 7z.dll raises an error, that the file couldn’t be unregistered.
Removing and reinstalling PowerArchiver (I guess, this would de-register them) doesn’t fix the problem. -
“regsrv32.exe /u 7z.dll raises an error, that the file couldn’t be unregistered.”
That might be your problem, what VM Application do you use? Do you have system admin rights?
I can do a bit more digging for you, but in experience 90% its the VM config causing you the problem.
Kind Regards,
RJWaring -
Hi, I’m using Oracle VirtualBox 6.0.12 for virtualization.
My account is an administrator with UAC protection, I ran the command from an elevated command prompt.I’m unsure, where to find the problem. The shell extension works perfectly fine in other folders. As I wrote above, the crash happens while compressing files on the desktop.
As I’m using the VM to test new software, the config might be broken and time to set up a new one.
I don’t know, if it’s worth to invest more time on the problem, as no one else seems to have the problem. -
Thanks BigMike,
I hate to say it , VM has a wide range of documentated cases like these the one’s i know of doing what i suggested helps, but not in all cases.
Then your talking more time to investigate, which is when the question is raised why not do a rebuild seeing that this isnt an issue being replicated on other VM’s.
But, it’s not a PowerArchiver problem as i’ve seen this across many other platforms and dll’s.
Sorry i couldnt help further buddy, if you do manage to figuire it out please share we would love to hear from you again.
Kind Regards,
RJWaring
