-
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.
-
Is the version Preview 2023 also considered to be tested by the testteam ? In the past we got messages in the forum for testing out version x.x, to be downloaded by fastring, or I missed the one for 2023. (I discovered 2023 on the official web…)
CU, Pirrbe.
-
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).
-
PA 21.00.18 running on Windows 7 64 bit.
I made a big .PA file and thought I’d check it was made correctly with Menu / Actions / Test.
Discovered:
a) PA always issues a UAC prompt to do this!
b) PA always says there are many errors in PA files. -
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.
No warning for wrong passwords?
-
I’m using the latest beta (11.50.30) and I found that when extracting password protected rar files if a wrong password is entered it will not give you any warning at all. Instead it seems to extract the file successfully but the destination folder will end up being empty.
I tried the same file with the 7zip program to make sure it wasn’t just a problem with the file, and it correctly gave a wrong password warning and quit rather than trying to extract the file anyway.
-
thanks, we will check it out…
-
Beta 2 is out, please check it out via web update or download page. Thanks!
-
problem still occurs in beta 2 with rar files.
strange thing is…winrar does exactly the same thing…
it will issue you with a warning but it still creates the empty folders as PA does. -
I get a “wrong password” warning but not second prompt to enter password.
reported
Anyone else?
-
ok here’s what I found after further testing…
if I’m trying to extract a rar file that hasn’t used the ‘encrypt file names’ option in winrar then I get a created empty folder as reported above.furthermore the only way to get a correct result is to open the file with PA and NOT use the shell extensions option to extract it…using the shell extensions always gives me an empty folder.
open the file with PA and then it seems to work correctly provided of course the rar file has used the encrypted file option.
phew! hope that makes sense…lol
-
how are you extracting through shell?
-
I’m just using the normal PA shell ‘extract to’ options
-
I updated to Beta 2 but I’m afraid the problem is not fixed. It still does not give any warning at all if a wrong password is entered for protected rar files. It appears to successfully extract the file, even though nothing is really extracted at all. This happens with both the shell extension and from running the program. I’m using XP by the way.
-
Please check beta 3 via web update or download page and let us know if this issue has been fixed… thank you!
-
I now get a warning that the password is incorrect in beta 3 but it still creates an empty folder with more empty folders in it but obviously no files…I don’t see the logic in it doing this to be honest.
if the password is incorrect it should just either close or give you another attempt at the password surely ?
-
it needs to extract files before it knows if password is wrong or not… when you say empty folder, what exactly do you mean?
thanks
-
it creates a folder based on the name of the zip file but there aren’t any files in it because of the incorrect password…wouldn’t it then be better if this was the case to then delete the empty folder?
if the zip file contains many folders then it creates them as well within the original folder but again without any files/content.
I just can’t see the logic in it leaving you with the empty folder…just my opinion anyway.
-
it is not that simple, it does not know if some files were extracted and some were not… it doesnt know if folder is empty.
-
well you guys are the experts…it’s something we’ll have to live with then…:)
-
Actually the situation is following. Folders and empty folders too are “stored” with no password protection. Hence, they are extracted same as other non-protected files would be extracted even if you enter wrong password after all those files are extracted.
-
can I assume it’s all to do with the ‘makeup’ of how winrar creates it’s encrypted files?
when I use the same encryption method in PA (PAE) it at least removes the ‘empty’ folder after an incorrect password has been used.
