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
Grouping of PowerArchiver windows doesn't work
Hi, first I want to thank the programmers of PowerArchiver, who made this powerful update to PowerArchiver, especially the 7-zip support is great.
I noticed that now I use Windows XP Professional SP-1 i cannot group powerarchiver windows. This is not a big problem. I discovered also that when you hold the CTRL + select taskbar windows you can’t set powerarchiver next to other windows. I would like to have this feature added, so you can handle multiple windows faster.
grouping works on mine, but it took me 9 instances of PA to group. seems a bit high… i thought this was a global option or something for windows? perhaps PA is not obeying this the way it should?
also, once they are grouped doing a right click -> close group doesn’t work either. it only closes the top instance.
edit: the ‘tips’ being open is what causes close group not being able to work.
Hm, I never used this Windows feature so first I must see how it works, and is there any way to “tell” Windows about group. I also don’t know is this features only for Microsoft applications or all other applications and how it should work when you click on “Close group”. I will check it.
Isnt grouping automatic when you have too many taskbars? In that case, it works fine with PowerArchiver…
Is there any other way for Windows to use grouping that we dont know of?
I totally forgot I had post here. Sorry for my late response.
However the error still exists in PowerArchiver 9.2. I ment like behaviour when using Internet Explorer or whatever program when holding Control button and then selecting multiple windows from the taskbar in Windows XP. Right-click after that on the taskbar and you get choice to handle the windows trapswise, next to eachother, above and under eachother or close the group. It would be fantastic if you could set a PowerArchiver window next to an explorer window and drag and drop files more easily.
Since this issue is still not solved here a screenshot of what a mean:
BTW, I use Dutch version of Windows XP
Hold CTRL and select powerarchiver window and another window (like explorer). THan right-click on the selected taskbar-button. Not working!!!
BTW, this is one of this new Windows XP feautures. Why not use them anyway?
You mean hold ctrl and click on 2 different application taskbar buttons and then right click on one of them? What is the option that you are looking for?
It seems to work here, but I am using internal version. However, no specific changes were made to accomodate this, it is an Windows feature that should work with any Windows program automatically.
Doesn’t work here with PA 9.21 on XP Home SP2. For example, I selected four taskbar icons (2 PA and 2 others) and then chose Tile Horizontally. The operation was only performed on the two other windows, not on the two PA windows (they stayed the same as before the operation).
PM me with a link to the new internal version and I will try it out to see if it works.