-
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.
PA2010 and Unicode
-
The graphical interface part of PA2020 still doesn’t support unicode completely. I initially raised this issue here. I am particularly concerned about displaying unicode file names and inputting unicode characters in the 7z and rar format.
PA2010 simply still can’t display unicode names inside 7z and rar files. Also, for 7z files, PA allows you to rename files inside them. You can’t input unicode characters here either.
As far as unicode handling is concerned, the original 7-Zip file manager is the best. Of course, it can’t edit (e.g. rename files inside) rar files, but it can display unicode names inside rar files fine. WinRAR file manager is far behind 7-zip. It can display unicode names inside rar files (of course :)), but it can’t display unicode names inside 7z files correctly (and doesn’t accept unicode paths in, for example, the “Extract to…” window). Now, PA is tied with (or somewhat worse than) WinRAR. This is really unsatisfactory :(
-
i cant reproduce the issue, it works fine here. Can you please attach an example archive here so we can check it out.
-
OK, there are three text files whose names are in Chinese, Japanese, and Russian.
I am using PA 2010 11.50.48 RC1.
attachment_p_18679_0_test.7z
attachment_p_18679_1_test.rar -
works fine here - what OS are you using? maybe it is more specific… Also, can you go to options and reset defaults? it might be due to some option being on.
thanks,
-
I am using Vista. I don’t think there are any option settings that affect unicode handling. The fact is that they work fine in the 7-Zip file manager and they don’t in PA2010 on my end. Could you change the regional setting/system locale for Windows from Control Panel and see if they still work. Also, can you input (copy and paste), for example, Chinenese characters in any input windows of PA2010 (e.g. rename)?
-
there is no chance for language setting to make chinese and arabic work together. Mine is set to English in any case.
Can you please reset your settings to default and check then? Your PA settings of course.
I can rename files inside 7z too, copy and paste cyrilic name inside arabic one….
-
you could also go to your registry, export your HKCU\Software\PowerArchiver setting and zip it, and send it to support at conexware . com
and we can try with your settings, thats even better.
-
Can you please reset your settings to default and check then?
OK, resetting worked ;) (The nag screen is back!)
So, the culprit is Configuration > Miscllaneous > allow all lower case file name.
I looked up this setting in the help file, thinking what is wrong with allowing lower case file names. I don’t think this setting should affect unicode handling. For one thing, how it’s worded is confusing. But for languages that don’t have any distinction of lower and upper case (e.g. Chinese), this setting shouldn’t affect the availability of file names in those languages.
-
OK, resetting worked ;) (The nag screen is back!)
So, the culprit is Configuration > Miscllaneous > allow all lower case file name.
I looked up this setting in the help file, thinking what is wrong with allowing lower case file names. I don’t think this setting should affect unicode handling. For one thing, how it’s worded is confusing. But for languages that don’t have any distinction of lower and upper case (e.g. Chinese), this setting shouldn’t affect the availability of file names in those languages.
there you go :).
that function is probably not unicode compatible and it breaks support for it… i dont remember why exactly would someone use it anymore :).
-
that function is probably not unicode compatible and it breaks support for it… i dont remember why exactly would someone use it anymore :).
So I think we have an option that can be removed :p
I don’t think there is any need for PA to check case as nowadays windows doesn’t care whether name is upper, lower or mixed case :confused: -
i dont remember why exactly would someone use it anymore :).
I suspect it’s there from the days that zip file contents were often or always DOS-style filenames that were all caps. This would make listings more readable.
I’d agree with TBGBe that there’s probably no reason for this option anymore (especially if it causes problems sometimes…).
-
i should go on on hunt for options we dont need anymore :)
-
This issue has been fixed in following pre-release:
http://www.powerarchiver.com/test/alpha115/powarc1150rc3.exePlease let me know if it works fine now. Thanks!