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.
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.
PowerArchiver Queue made worse
Just installed 2021 v20.00.63
Now, when I add to queue, with or without using always use queue.
The powerarc starter opens up in notification bar.
and that’s it, no matter how many files I add to queue, no compression will start.
I also cannot double click or right click the icon.
If i end task for this, and disable queuing, compression works fine, just that I have to manually start individual tasks.
it’s quite ironic that you guys took whole year to fix one issue, in this versions, which completely broke the queuing feature.
Did you guys test it before releasing?
tested, working fine in the tests here.
provide details, how are you adding them?
how many files?
Thank You for your Kind and prompt Response to my threat.
Please find Details Here:
It the video when you started PASTARTER you just saw the total CPU usage go up and assumed it was PASTARTER using the CPU. Why didn’t you check?
Also it looked like there was an operation in the queue already so when you started PASTARTER it would have immediately started the operation and therefore used CPU.
I have reported the inability to cancel at least twice before. They don’t do anything about it.
I think you did not notice properly, PAStarter was using 2444something KB of ram
no other Powerarchiver process was running.
and compression does not take only 20% of CPU, it takes 100% of CPU(I did not tick low priority compression)
No RAM was being used, actually, compression takes up all the ram that is available
No Temporary Files are created.
No Progress Dialog Box, if compression starts, there’s always a dialog box that shows progress and it comes on top
Also, it’s a bug which you did not refer on another post created by another user where PAStarter is using CPU for no reason.
For me it’s 20%, for this guy, maybe due to his old PC it’s 100%
And most of all, I want to right click on PAStarter icon and click on Show queue, why can’t I?
Also downloaded from:
but the file that got installed is 62, not 63
There are in numerous amount of bugs with the software that I can list, I already have, they just refuse to do anything about it.
AluminumHaste last edited by
It’s not that they refuse to do anything about it, if they cannot replicate the issue on their end, they cannot debug and fix the issue.
I have same problem with PAStarter:
- PAStarter takes 16~17% CPU usage when is running.
- Can’t click, right click or double click on PAStarter icon in systray.
- In Windows Explorer:
3.1. Try to compres a folder/file: i clicked with right mouse button on that folder/file and select PowerArchiver / Compress to “abc.zip” but nothing happened.
3.2. Try to extract file: i clicked with right mouse button on that file and select PowerArchiver / extract to “abc” folder. Folder abc is created, but no files extracted.
In Order to replicate the issue, you need to know how to use the product.
This lady here stated that she could not replicate the queue issue prior to this where some of the archives were unprocessed and ignored, how come they fixed it now?
it was common and happening with everyone, I even did clean install of OS and App directly from 2021 final, still was facing this issue.
And okay, Why can I still not save the exe, pdf PNG filter and dictionary size tickmark under advanced when using PA as format, in any profile?
Why can I not remove the default profile and make a new profile as default?
Why can I not use Advanced option for PA compression under multi archive compression?
It’s all in plain sight, there’s no difficulty in replicating the issue
I resolved the issue.
How to reproduce(it is my assumption):
Install the older version of PA 2021 than this, the one that came before x.x.62
run it once, then install the current version.
PA queue & PASTARTER will get bugged.
I got the issue resolved as I had to reinstall OS which has resolved the queue issue for me.
this is the same reason mili was not able to replicate the issue, because she runs a fresh environment for all testing.