PA2023 Win10, (same problem with older releases but never reported)
PA Soft is installed on partition D. (exclusive for installed progs)
Then I created on my partition G: the folders as configured in PA Settings ‘Folders’.
0fcf1b09-1b91-4b74-b250-f8cf908a3348-Ashampoo_Snap_maandag 20 maart 2023_11h54m34s.png
Screenshot 2023-03-20 121152.png
The problem : Any activity on PA is saved in these folders…
PA ignores them and still use the default settings. Whats wrong ? Regards, Pirrbe
I am still using Powerarchiver 2022 and it does not show pdf markups in the preview. Is there a setting to get version 2022 to show pdf markups in the preview? If not, does this work in version 2023?
The question that I have about PA archives is what happens if say ConeXware, as a company, dies in the future? What happens to any PA files that are created today? Can these files be decompressed with a copy of a PowerArchiver that can no longer phone home to the mothership thus can’t be registered or activated?
I mean, I can understand that new PA files wouldn’t be able to be created if the program isn’t registered but what about an un-registered copy because well, the question that I posed above?
It’s questions like this that make me not want to store anything really valuable in PA files out of fear that I, at some point in the future, might lose access to said data inside those files. OK, 7ZIP might not be able to compress as heavily as PA but at least it’s open source and any 7ZIP files will still be able to be read and decompressed ten, twenty, or fifty years from now.
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.
Is this a known problem? Is there a fix coming? This is a primary reason I buy PA.
I’ve tried both methods I know to extract multiple zips at the same time. 1) Multi Extract feature in the GUI. 2) In Windows File Explorer, select multiple zips, right click, use PA context menu to Extract or Extract To…
Is there a setting I missed? Or maybe it really is processing in parallel, but I can’t detect it? Nothing tells me in the Processes in Task Manager that multiple PA extracts are running. And my CPU, memory and disk resources do not look like a lot of extracts are running.
I’m using PA 2022 Standard version 21.00.18 on Windows 11 Pro version 10.0.22621 Build 22621.
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
Hi there, been a user since 13 years now and in past whenever I had a problem or question I could email, however since 3 weeks it seems like everybody is dead?
Anyway, as kind of a last resort, I post this email a 4th time but in this forum instead now, in the hope for help:
"This is the 3rd time I am emailing you guys as I am missing a working code for the preview of Power Archiver 2023
Can you please help me? I am a 13 years lasting customer of yours, and I am shocked thatr for whatever reason my support tickets are ignored now, why?
thanks in advance!
All the best!
Re: Explorer.exe Crash on right click
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).
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.
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:
Brian Gregory Alpha Testers last edited by
@godlydevils said in PowerArchiver Queue made worse:
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.
godlydevils last edited by godlydevils
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.