-
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 2023Can 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!
Joerg" -
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.
Inconsistency with disabled tabs and multiple instances of PA allowed
-
If I the Configuration > View > Standard > Disable Tabs option is checked, when double clicking inside archives on files supported by the internal viewer (PDF, JPEG etc.) they are opened in associated application rather than on a new tab in PA internal viewer, which is expected behavior.
Next, if the Configuration > Miscellaneous > General > Reuse PA Windows is unchecked, when double clicking on archives associated with PA in Explorer they are opened in new PA instance when there is another one already running, which is expected behavior.
But when Configuration > View > Standard > Disable Tabs option is checked AND Configuration > Miscellaneous > General > Reuse PA Windows is unchecked, when double clicking inside archives on archive files they are opened in the same instance of PA with no way to get back to the parent archive. I would expect, that when the user doesn’t want to use tabs AND want to use multiple PA instances, that in such case double clicking on archive located inside another archive, the second one would open in a new PA window. -
Hey - welcome to PowerArchiver forums!
Thanks for this and for testing.
This is currently expected behavior - you can go back to previous archive (or the root archive) by closing the current one (ctrl+L or close archive).
Does that work for you?
-
No, it does not work like that.
Just to be clear: I have both options set as mentioned earlier and I’m opening archive file (let’s say ZIP) associated with PA by double clicking it in Explorer. Next I browse inside this archive and somewhere inside there is another archive file (let’s say RAR) so I open it by double clicking. It opens in the same PA window, next I browse inside it, but I want to back to the original (ZIP) archive. I could do that using tabs but I specifically disabled them. Using Ctrl+L or Close Archive option leaves me with empty PA window with no archive (neither ZIP nor RAR file) opened.
So it could be that the Close Archive command is not working as intended when Disable Tabs option is checked and Reuse Windows option is unchecked.
Personally I think in this case it would be most logical that trying to open archive located inside another archive would actually result in opening it in another PA instance. If this still seems unusual behaviour for you even with the mentioned two options specific combination, maybe you could add another configuration option like “force opening sub-archives in new window”, or something like that? -
thanks for reporting that - @Mili can test it and submit bug report.
It should definitely go back to the old archive, as that is how it worked before we had tabs support.would that work fine for you use?
-
While I would personally prefer to have option added that forces the behaviour described earlier by me, if asking for that is too much, fixing Close Archive option will be good enough.
-
thanks for the details @aionel_net
We have logged the issue in for fixing and have added the suggestion to open a new PA window upon double clicking an archive inside an archive, when tabs are disabled.
Lets see what the dev team says.thanks again!