-
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.
PASHLEXT.DLL is blamed by Raymond
-
Blamed for slow right click.
http://www.raymond.cc/blog/archives/2010/01/04/fix-for-very-slow-or-hang-when-right-click-on-a-file-or-folder/ -
probably interferance with antivirus or something, without proper report nothing we can do… PA does not scan .zip files when right click, so there is no chance for it to cause slowness.
-
without proper report nothing we can do…
Yeah, but it’s not good for publicity. Isn’t it worth at least sending email to the author?
-
Yeah, but it’s not good for publicity. Isn’t it worth at least sending email to the author?
you are right of course… lets see if we can get to the bottom of that.
-
p.s. not for publicity, but i dont like that there might be an issue with PA that I am not aware of ;-). It will be curious to see what was the culprit.
-
I had the very same problem, investigating with Sysinternals’ Porcess monitor I noticed my problem occurred when it read the keys HKCU\Software\PowerArchiver\Files\Active_File*W one by one and tried to “queryBasicInformationFile” on files on network resources that were no longer available, such as \MyRemoteMachine\MySharedFolder\myfile.zip
I simply removed the offending HKCU\Software\PowerArchiver\Files\Active_File4W key from the registry and right click slow down was gone -
I had the very same problem, investigating with Sysinternals’ Porcess monitor I noticed my problem occurred when it read the keys HKCU\Software\PowerArchiver\Files\Active_File*W one by one and tried to “queryBasicInformationFile” on files on network resources that were no longer available, such as \MyRemoteMachine\MySharedFolder\myfile.zip
I simply removed the offending HKCU\Software\PowerArchiver\Files\Active_File4W key from the registry and right click slow down was goneeven if network resource is not gone, it might take a while to respond… i have already set that for investigation because it seems that it reads it first time and then removes them (meaning you get slowdown once at least). They should not be read at all.
thanks for the info…
-
Please check if following pre-release fixes the issue:
http://www.powerarchiver.com/test/release10/powarc116202.exeand let us know… thank you!
-
This post is deleted! -
Unfortunately the pre-release v11.62.02 does not fix the right-clicking delay issue. I’m running Windows 7 Professional 64-bit and KIS 2010. I don’t think the problem is network related. I have noticed that it happens sporadically (not every time you right-click). My feeling is that it is related to AV software or it affects only the 64-bit PA shell extension or the combo 64-bit and AV software. This is really an annoying problem and I’m praying every night for a solution to became available quickly.
Sorry for my premature post. I was so excited with a possible solution to this annoying problem that I forgot to log off or reboot my machine before testing the pre-release version and after rebooting… it works!!! The delay is gone.
-
Unfortunately the pre-release v11.62.02 does not fix the right-clicking delay issue. I’m running Windows 7 Professional 64-bit and KIS 2010. I don’t think the problem is network related. I have noticed that it happens sporadically (not every time you right-click). My feeling is that it is related to AV software or it affects only the 64-bit PA shell extension or the combo 64-bit and AV software. This is really an annoying problem and I’m praying every night for a solution to became available quickly.
praying to the PA gods? :-).
can you check the date on the pashell dll and see if it is 2/1/2010… dev team might not have updated it for 64bit for pre-release as well but lets see if your dll is updated first of all.
you can go to hkcu>software>powerarchiver, delete that key completly and then see if you still have the slowdown (that will let you know if it is MRU issue).
Tricky thing about it is that it depends on your network… if windows has recent cache it will not query your network at all, and you will not notice the slowdown for instance… until it needs to query it again or computer is simply missing.
-
p.s. you should have posted sooner in this thread that you have issue with it…
-
Sorry for my premature post. I was so excited with a possible solution to this annoying problem that I forgot to log off or reboot my machine before testing the pre-release version and after rebooting… it works!!! The delay is gone.
greeat then ;-)
-
in the future please report your issues even if they have been reported before, it lets us know how serious something is… thank you!
-
praying to the PA gods? :-).
no doubt!
can you check the date on the pashell dll and see if it is 2/1/2010… dev team might not have updated it for 64bit for pre-release as well but lets see if your dll is updated first of all.
that’s the weird part… it worked but…
PASHLEXT.DLL
version: 11, 6, 1, 1
date: 02/12/2009 19:21:48
size: 238.456This is after a full uninstall, reboot and then install pre-release. So dll not updated for 64-bit? But no update required in order to correct the issue? I’m confused here.
-
no doubt!
that’s the weird part… it worked but…
PASHLEXT.DLL
version: 11, 6, 1, 1
date: 02/12/2009 19:21:48
size: 238.456This is after a full uninstall, reboot and then install pre-release. So dll not updated for 64-bit? But no update required in order to correct the issue? I’m confused here.
probably due to the fact that dll actually just calls PA to do the work, and this has been fixed on PA side…