-
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.
-
-
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.
Extract archive to subfolder - multiple archives to one folder
-
Several versions now I’m seeing this problem…
I have the ‘Extract archive to subfolder’ context menu action enabled under the shell extension settings. In all past versions, selecting multiple archives and then dragging-and-dropping them to a destination folder and extracting them with this option caused all archives to be extracted to their own folder - named after each archive. Since the last few versions, only a single folder gets created (named after the FIRST selected archive) with all of the archives contents being extracted to the single folder…
Is this “known” and expected to be fixed soon? Having to select and individually extract each archive is a real pain…
-
Hi steje,
The Option you’re looking for is Extract to filename/
It’s not enabled by default and you have to add it manually, here’s a screenshot showing where it is. Single click it and click Add or Add to Submenu
-
Once you do add it, the right click option will look like the highlighted below.
It shows up when multiple archives are selected and right clicked and it will extract all archives into separate folders;
-
Thanks as always Mili… this was a self-inflicted problem. I must have messed around with my shell extension settings for some reason at some point and didn’t realize I had reset them to use the wrong subfolder action. Thanks for correcting me… all good now.
-
maybe we could set this as default option for 2015?
-
Thanks as always Mili… this was a self-inflicted problem. I must have messed around with my shell extension settings for some reason at some point and didn’t realize I had reset them to use the wrong subfolder action. Thanks for correcting me… all good now.
You’re very welcome steje!
As spwolf points out, it probably wouldn’t be a bad idea to make this a default option in PA 2015. As it’s probably the most logical way to handle extracting multiple archives into subfolders. -
So - ironically, since updating to 15.00.38 - this seems to have BECOME a legitimate issue :-)!
I’ve got 3 zip files in the same folder:
Autoruns.zip
SysinternalsSuite.zip
Sysmon.zipI select all three and drag them with right mouse button and then release. I pick what seems to be the ‘multiple archives into separate folders’ item from the drop menu. But only one folder is created, with the contents of all three zip files mixed into the one folder (named after the first selected zip file). Same behavior as if you’re using the ~wrong shell extension option like I had unknowingly been doing before == the regular ‘Extract archive to subfolder’ item.
So, I went into Configuration, and edited the Shell Extensions/Extraction page to remove ALL menu items (except for the sub-menu that you never let us remove ;-) ). I was surprised that after doing this, I still had both the ‘Extract Here’ and ‘Extract archive to subfolder’ menu items appear on the drop menu…?
But I then go back into Configuration and re-add the ‘Extract to filename/ (multiple archives into separate folders)’ item, and when testing again - it still DISPLAYS in the context menu as if it’s the right item (by virtue of showing \filename\ at the end of the Extract To text shown in the context menu text, instead of the actual name of only the first of multiple filenames selected which is indicative of the regular ‘Extract archive to subfolder’ menu item). But again, the behavior is as if the regular item is selected.
Weird… did you perhaps in fact make a change in v15 like the one described here about making the ‘multiple archives into separate folders’ the default behavior, but it somehow went terribly wrong - lol?
-
yep, we added by default for both options to work… it seems that drag and drop one has the issue you experienced, while “normal” right click works fine? Please check it out.
thanks!
-
Hi wolf… yes, confirmed. The right click context menu Extract to /filename/ works as expected as you said. It’s only the drop menu thats broken…
-
okie dokie, new version should be out soon.
-
Hi folks, just wondering if there is a fix for this intended for release some time soon? I submitted a ‘Support Form’ last week but it seems maybe the support form might be a bit deprecated? At least, the version drop down only goes as high as PA2013, and I didn’t get a response… so I’m mentioning again here now because several updates have been released so far without a fix.
-
hey Steje, this was logged into the system but we’re now adding it to the list for the next update. thanks very much for the reminder!
-
At least, the version drop down only goes as high as PA2013, and I didn’t get a response… so I’m mentioning again here now because several updates have been released so far without a fix.
did you get ticket number automatically?
-
Thanks Mili!
Hi spwolf… I don’t recall seeing anything other than a web page that acknowledged me submitting the report. I didn’t get an email or anything like that (I checked SPAM, etc).
I just submitted a new report for another issue I’ve been having - and I see that PA2015 is now an option in the drop down - thanks. But again - I just get a “Your report has been sent, and will be replied to as soon as possible!” page come up - and no email ack that a report has been filed, etc.
-
weird, still nothing and nothing in the logs of the support software… what support page are you sending it from?
You can just send email to support at conexware dot com… it will automatically accept your report and send you ticket number… lets try that!
-
Please check this release for right click, several files extract to filename\ extraction:
http://www.powerarchiver.com/test/release15/powarc150202.exethanks!
-
Hi wolf… yeah, I installed the 15.02.02 build and the drop menu action now works correctly for multiple archives.
Thanks for the fix!
-
Hi wolf… yeah, I installed the 15.02.02 build and the drop menu action now works correctly for multiple archives.
Thanks for the fix!
thanks for reporting it!
-
Actually - sorry - but something else is broken now ;-).
I went straight to testing extraction of multiple archives, which now works like it used to. Separate folders are created correctly for each archive… However, when extracting just a SINGLE archive - it behaves as if you just used the ‘Extract Here’ drop action. I.e. the contents of the archive are extracted to the current folder - no new folder gets created.
Shall I send an email with the problem report - or is reporting here good enough to get it fixed?
-
Actually - sorry - but something else is broken now ;-).
I went straight to testing extraction of multiple archives, which now works like it used to. Separate folders are created correctly for each archive… However, when extracting just a SINGLE archive - it behaves as if you just used the ‘Extract Here’ drop action. I.e. the contents of the archive are extracted to the current folder - no new folder gets created.
Shall I send an email with the problem report - or is reporting here good enough to get it fixed?
no need to send email, i wrote it in here… argh! thanks!
-
Actually - sorry - but something else is broken now ;-).
I went straight to testing extraction of multiple archives, which now works like it used to. Separate folders are created correctly for each archive… However, when extracting just a SINGLE archive - it behaves as if you just used the ‘Extract Here’ drop action. I.e. the contents of the archive are extracted to the current folder - no new folder gets created.
Shall I send an email with the problem report - or is reporting here good enough to get it fixed?
Still not fixed in 15.02.04.
-
@Brian:
Still not fixed in 15.02.04.
this was reported day after 15.02.04 was released, unfortunately.
-
this was reported day after 15.02.04 was released, unfortunately.
Are you able to give a rough estimate of when a fix will be released?
-
@Brian:
Are you able to give a rough estimate of when a fix will be released?
Monday if it passes testing?!
-
You can help us test it here:
http://www.powerarchiver.com/test/release15/powarc150301.exeWe still did not have time to test it properly, so it would be helpful… thanks!
-
in initial testing it seems to be working fine, looking forward to your confirmation :)
-
You can help us test it here:
http://www.powerarchiver.com/test/release15/powarc150301.exeWe still did not have time to test it properly, so it would be helpful… thanks!
Yes, seems fine to me. :)
Thank you.