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 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.
Possible bug in creating password protected zip files in v11.03.04
I can’t find any setting to prevent an issue caused by the following task:
1. Right click on a folder and choose “Compress to Zip + Options”
2. Choose any encryption from the dropdown box.
3. Press Add and type in a password when prompted twice.
…the result is a password protected file which always includes a copy of the folder structure (which is empty) along with the files.
Can’t reproduce this. Please check if you don’t have the “Save full folder info” option checked.
Maybe give us more details of folder structure that is being saved?
No, I don’t have the “Save full folder info” option checked.
Since there are so many settings and everyone uses different ones, here’s the easiest way to reproduce the issue:
Perform a clean install and make this single change:
uncheck - “Use normal relative path”
(I don’t like having this option turned on since it creates an unnecessary root folder in an archive if a single folder is zipped)
Create a folder on your desktop called “test” and place two text files in it.
Right-click on the folder and choose “Compress with Options” and click “Add”
At this point you end up with an archive which contains the two text files along with an unnecessary and empty folder structure.
If you were to choose “Compress to “test.zip”” instead, a proper archive is built.
The reason I felt it had to do with password protected files is that I would choose “Compress with Options” to include a password and “Compress to…” otherwise.
Having researched this further, I’ve discovered that when you simply choose “Compress with Options”, you get that issue regardless of whether or not you password protect it as shown in the steps above.
The empty folder stucture being saved using the steps in my last message is (in my case):
Documents and Settings
thanks, we will check it out…
I have the same problem.
It’s a bug.
And it happens whenever you select:
Compress to Zip + Options (password protected or not)
- Right click on a folder that contains 3 files located at D:\Desktop\Sample Folder
- Select “Compress to Zip + Options”
- Uncheck all checkboxes and use default options
- Click on Add
The zip file is created called: Sample Folder.zip It contains the 3 files, plus an empty folder: Desktop\Sample Folder
What does “miiiliiiiiiiiiiii” mean? :confused:
What does “miiiliiiiiiiiiiii” mean? :confused:
calling Mili to write the bug down into our bug list :P
oh “Mili” the person. Sorry, I’m new to this forum. Our friend Mili. :) Gotcha…
Have no fear, Mili is here!! :)
Had tested this earlier but could not reproduce. Finally reproduced it.
Reported to dev team. Thanks mj0hnson!!!
Glad it’s being fixed :)
please check with official beta 1, and let us know if this has been fixed… thank you!
It’s been fixed - Thanks!