-
PA 2023 22.00.08
Long time no seeing. So I start up the new year with a first problem : the virtual driver cannot be installed. Reason : it is missing in the Fast Ring PatchBeam Update Service…
Virtual driver PA 2023-01-28 152607.png
It seems a standard problem with new releases :-)
Can I have a link or can it be fixed. Thank you. CU later -
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.
Recipients unable to unzip compressed folders
-
I am a registered user but was unable to send a message to support because I got an error message that said I had not entered sufficient information.
The last two times I sent zipped files to recipients (one e-mail the other a LogMeIn link to download from my computer), they were unable to extract the compressed files. I have been using one version or the other of Power Archiver for a long time and have never had this problem. The one that downloaded it from my computer downloaded it twice and had the same problem both times. The error message the recipient saw when trying to extract the files was:
<local path=“”>Unknown method in <compressed filename=“”>. This repeated for each compressed file.</compressed></local>
-
maybe the file was corrupted during sending? Also make sure that both of you are using same version of PowerArchiver.
-
This has happened with different recipients on the last two times I have e-mailed files and had people download files from my computer so I don’t think that they were corrupted (three different file exchanges – all the same result). When you asked if we were both using the same version of Power Archiver, that surprised me. Is the .zip format not universal? I doubt these other people are using any version of Power Archiver. Can’t a zipped Power Archiver file be reliably unzipped by Windows native unzip utility? It has been working in the past. Thanks for your help.
-
This has happened with different recipients on the last two times I have e-mailed files and had people download files from my computer so I don’t think that they were corrupted (three different file exchanges – all the same result). When you asked if we were both using the same version of Power Archiver, that surprised me. Is the .zip format not universal? I doubt these other people are using any version of Power Archiver. Can’t a zipped Power Archiver file be reliably unzipped by Windows native unzip utility? It has been working in the past. Thanks for your help.
ZIP format has many different versions. New PA 2010 introduced new zip methods which are compatible with zip format, but Windows native zip utility does not support them. They are supported by newer utilities such as PA 2010 or WinZip 12.
So to make sure all your recipients can read your zip files, either tell them to download PA 2010, or use deflate method for compression.
-
Is there a way to use PA 2010 to produce zip files that are readable by the native Windows utility? If not, can I downgrade to an older version that produced compatible files?
-
Is there a way to use PA 2010 to produce zip files that are readable by the native Windows utility? If not, can I downgrade to an older version that produced compatible files?
yes, as i said above, you need to use “deflate” as method… It is set by the default and you can select it manually in all of PA compression screens.
Thats why it says “Deflate (Compatible)”.
thanks,
-
Is there a way to use PA 2010 to produce zip files that are readable by the native Windows utility?
Just use the standard (not the new optimised) options
- method : deflate (or store)
- don’t use ultra compression
Edit: too slow :-p
-
Thanks for the help - but I need a little more. I looked under Options - Configurations and on the Tools menu but could not find where to set these parameters.
David
-
it is not that complicated - it is in add window that you use to select files to compress.
So compress those files again and you will have an option to select what method to use, pick Deflate.
-
Also (for shell) you can set the options under Configuration/Profiles/Zip
-
I had a similar issue with recipients not being able to open zip files. In my case it only occurred when I zipped up a folder by right clicking on the a folder and used the “Compress to <folder name=”“>.zip” explorer extension.
Opening up zip files created this way with the “Repair ZIP Archive” tool showed the folder as corrupted but all the folder contents fine. I have an open support request and confirmation that they were able to reproduce the error.The Repair ZIP Archive tool on the tools menu was able to remove the corrupted folder file and produce ZIP archives that could be opened by my recipients.</folder>
-
I had a similar issue with recipients not being able to open zip files. In my case it only occurred when I zipped up a folder by right clicking on the a folder and used the “Compress to <folder name=”“>.zip” explorer extension.
Opening up zip files created this way with the “Repair ZIP Archive” tool showed the folder as corrupted but all the folder contents fine. I have an open support request and confirmation that they were able to reproduce the error.The Repair ZIP Archive tool on the tools menu was able to remove the corrupted folder file and produce ZIP archives that could be opened by my recipients.</folder>
someone reported that issue and it was fixed in upcoming RC1
-
Winrar users faced the same problem with v11.03
-
i am closing this thread as original question as been answered - please open new threads for new problems, thanks!
