-
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.
Bug: Non-english char filenames
-
Archive filenames with non-english characters seem to be refused to open in the latest version of P.A. Earlier versions worked fine with foreign language filenames.
I’m using Windows XP if this is in dispute elsewhere (PA 9.02.01)
- Joel
-
Hello!
Can you give us more information.
-
Which is the archive format you are having problems with? Can you please try renaming some other format (if it is ZIP, then to e.g. CAB or 7-ZIP) to same archive filename, and then try opening.
-
Does this happned from main PA or from shell extensions? Try both of them.
-
What is your country? Does this filename contains only local country letters or UNICODE letters?
-
Can you create 7-ZIP file and add some smallest archive with this filename to it and then send it to us so we can check. 7-ZIP will save filename even if it is UNICODE so we can check it on our machines.
-
-
My locale is Australia and default language is English. The characters in filenames that are causing problems are Hebrew characters on a FAT32 system, although the same problem occurs in NTFS. I presume this is a strange problem, considering that you provide a Malaysian version, etc.
From what I have tested:
a) The characters show as ? even in a right-click popup menu.
b) Note that below problems are independent of whether I open from explorer or by File->Open in PA. Archives that open ordinarily with only roman letters in the filename do the following:
- ZIP, 7Z, BH, LZH: open showing an empty archive
- RAR: PA cannot open message
- TGZ: “Error in TAR/GZIP file structure” -> PA cannot open message
- PAE (Rijndale): “‘4294967295’ is not a valid integer value.” -> empty archive
With your question: from main PA or shell extensions did you mean what I answered in (a)?
I previously used PA 2001 which my University introduced me to and I don’t remember these problems, but I may have not been using such filenames; now when I reinstall PA 2001, I get the same problems, but I don’t know if there would have been common DLL’s that reinstalling 2001 would have kept from the newer version so I don’t know if the test was fair.
Note that PA similarly doesn’t let me make archives with these unicode characters, simply because it doesn’t recognise it as a valid file, but it also doesn’t do anything logical to stop it, it just gives messages of confusion. Adding files with foreign characters sometimes works and sometimes doesn’t… I haven’t yet worked out the context.
To illustrate, attached is an archive test.7z, containing a aש.7z which contains a שדכחך.txt, although this is not shown when the archive aש.7z is opened.
I hope this helps (since it took time to experiment!)
-
Hello!
The archive filename contains UNICODE character. PowerArchiver doesn’t support archives with UNICODE characters right now - planned for 9.5. This limitation was also in ALL previous versions.
But, adding “those” files with UNICODE filenames is POSSIBLE. You can use 7-ZIP to add/extract archives with those filenames INSIDE, but only from main PA window (not shell extensions). Also extracting RAR archives with those filenames inside works fine.
Other formats (ZIP, CAB, …) DO NOT support adding/extracting UNICODE filenames. This is general ZIP specification problem - no program can do it right now.
So, please make sure all archive filenames are without UNICODE chars, but if need to compress those files, use 7-ZIP format which supports UNICODE filenames.
-
Hi, sorry, I hadn’t realised this was known to be unsupported. I mostly receive non-English filenames, so I just have to rename them, or not use PowerArchiver for now…
Other formats (ZIP, CAB, …) DO NOT support adding/extracting UNICODE filenames. This is general ZIP specification problem - no program can do it right now.
I’ve actually managed to extract RAR and maybe ZIP files with PowerArchiver that contained Unicode files, and it worked perfectly. I can’t test right now as I’m not in windows…
- Joel
-
No, you just have to use 7-ZIP format and non-unicode name for archive and you CAN add/extract/open/delete all the unicode files inside.
There is no ZIP utility that supports unicode filenames. There are just few archive utilities that support unicode filenames, but PowerArchiver supports in INSIDE 7-ZIP archives (not ZIP or CAB) completely.
-
You might be confused by seeing the Hebrew letters and thinking they were written in Unicode - Unicode is “just” an encoding standard for letters. You could have those same letters in several different encoding codesets and yet it wouldnt be the Unicode.
Due to limitations of old zip format, unicode is not supported so when you had support for Hebrew characters in zip, it was probably some other codeset and not unicode.
Only modern formats like 7zip and RAR support unicode because they were newer and they had built in unicode support. So basically, please use 7zip when you have to compress something with Unicode letters.
thanks!
-
There still seems to be a problem though.
Using PA to open the test.7z file that moo provided,I cannot read Hebrew, so I apologise but:-
Open test.7z
PA shows that there is another 7z file inside:- a{HebrewChar}.7z
Trying to open this (with double click inside PA window), nothing is shown - the file appears empty!However, using 7-zip File Manager (beta 4.09) I can see that
a{HebrewChar}.7z contains another single file {Hebrew}.txtSo it seems PA does not open the 7z file with these Unicode(?) characters in the Filename :confused:
-
-
Yes but Spwolf said:
Only modern formats like 7zip and RAR support unicode because they were newer and they had built in unicode support. So basically, please use 7zip when you have to compress something with Unicode letters.
I was saying that PA support for 7zip format doesn’t support Unicode {yet}.
So I think the current situation is that the filenames (to be archived) may use Unicode characters BUT the actual Archive filenames can not - is that right ?
P.S. Does PA support for RAR work with Unicode characters in Archive filenames ?
-
Terry - PA does not support archive filename in Unicode - this is PA-wide limitation.
Inside of archive, you can have Unicode filenames in formats that support them (7zip and RAR). -
Terry - PA does not support archive filename in Unicode - this is PA-wide limitation.
OK thanks - got it now - ;)