This appears to be happening again with the Power Archiver 2022 shell extensions.
When I have Use Explorer Shell Extensions enabled in Power Archiver Configuration and right-click on c:\Users\username\Start Menu, (hidden Junction file), File Explorer crashes.
I have version 21.00.15 (03/2022) 64-bit installed in Windows 10 Version 21H2 (Build 19044.1826).
In the latest version of PA, on W11 (latest build/SP) when you try to use the first level context menu - NOTHING HAPPENS (particularly when you do this from Downloads or Documents folders) - however I noticed that it DOES WORK when you use the context menu from the Desktop. Going to the second level context menu does work however.
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
Apparent glitch with some encryption via shell
I say “apparent,” 'cause perhaps I missed something. But I tried it three times . . . and had the same problem every time.
I have created a Profile called “ZIPX + PAE” – all with optimal settings. (I have a similar one for 7ZIP + PAE). The problem happens when I am tying to create a new PAE file using the former profile – in one cases.
Here’s what I found – all within the shell (highlight the files, then select PA and Compress To).
- the 7 zip/pae profile worked just fine – even if I renamed the file.
- the zipx worked fine if I did not rename the file.
- But if I tried to rename the file, it would not create the archive to be encrypted – it went straight to the encryption window . . . without having first created the archive.
I may just be missing something. But, as I said, I tried it thrice with the same result.
I did go back and recheck the definition of the profile. Everything looks to be in order.
hmmm, lets give it a check
Thanks. I am really not 100% sure. I may be overlooking something obvious. But it kept happening when it wasn’t happening with the parallel 7Z profile.
I appreciate it.
It happened ONLY when I renamed the file. I thought it might be a problem with the name (had a dash). But the 7Z profile worked.
Could you email me the .reg settings please?
Also, you’re changing the name in the full path field in the compress options menu or?
Also#2, is a PAE file created at the end or there’s no PAE file at all?
I tried it again. Every worked fine with the 7zip + PAE profile. But this time, I couldn’t even get the encryption window to open with the ZIPX +PAE profile. But these were different files, including different files types. That may have made a difference.
I attached a pic of the zipx profile in case I am missing something simple.
I am changing the name in the add window, which standardly opens first, and then - after the archive is created - the encryption windows (normally) opens. But not now with ZIPX +.
No PAE2 is created.
great, we’ll replicate and post the results. thanks!
I deleted the profile. Create a new one – exactly like the old.
It worked just fine.
So somehow that profile must have been corrupted, although the settings looked fine.
But maybe if you peek, you can figure out what.
Or prudence may demand ignoring it.
Attached is a comparison of the two:
The “new one” has “Use current folder as temp” (which is what I usually have set).
Could this have made the difference?
hmmm, i’ve tried using both ways and both work fine for me. But when I use your .reg settings, I get the issue you referred to.
I’ll be logging it in and do some further investigating to see what the culprit might be.
thanks very much for the details!
So a culprit lurking in the reg settings. The mystery deepens.
I went fishing in my config settings.
I discovered the cause of my problem reported a month ago (that you could not duplicate). Perhaps it is source of this problem as well.
Burning support was set to “autodetect.”
I changed it to SPTD, and the .iso window open exactly as it was supposed to – no 38 sec delay!
Maybe it is also causing this problem?
I have no idea how the setting got switched . . . it has always been SPTD. Maybe it was with one of the updates?
Actually, glad to know that I was not nuts claiming there was a 38 second delay in having the iso windows open!