-
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.
Rar file extracting ISO at 100% ISO
-
When extracting a ISO normaly you see the iso file while it is extracting and at the end just click it but mine just disappears after extraction no warning.
-
Sorry, but I have no idea what your problem is.
Can you give a “step by step” description of what you are doing - trying to do?A link to the rar/iso file would also help.
Also, which version of PA and which OS would be useful.
-
Windows Xp SP1 the problem is simple really when it extracts from the rar file the ISO disappears at 100% so i get no extracted file i have used current BETA’s and old versions the same thing.
-
Does it happen on all rar files or just one?
-
Does it happen on all rar files or just one?
All files over 1gb which is strange because i have 20gb free.
-
Over 1GB is a strange size limitation - and not easy to find for doing quick tests.
(2GB would make more sense - e.g. 16 bit limitations).Do you mean that you have a single rar archive (not split) which is over 1GB containing a single ISO file?
Or is the ISO file itself over 1GB ?Is the problem only with ISO files inside RAR…
or any RAR archive which is over 1GB…
or only when RAR archive contains a file which is over 1GB?Do you know how the RAR was created (which version of RAR)?
Exactly how are you trying to extract it in PA 9.5 beta 7?
-
Confirmed. I created a file FILE.ZIP using b7 and it was 1.2Gb, and then I try to extract it using b7, it extracted the content to… nowhere humm. The extacted folder and content is not to be found :)
-
@yop:
Confirmed. I created a file FILE.ZIP using b7 and it was 1.2Gb, and then I try to extract it using b7, it extracted the content to… nowhere humm. The extacted folder and content is not to be found :)
Sorry, NOT confirmed here. :confused:
I tried with a Zip of a DVD - zip filesize 4.04 GB (4,345,357,872 bytes)
Then tried a zip containing two movie files - zip filesize 1.66 GB (1,784,405,346 bytes)
Then tried a ZIP file of 980MB.All extracted with no problems in PA 9.5 beta 7.
Note: there was a “known” problem with PA not showing error message on insufficient disk space when using ZIP format, but this was fixed in PA 9.5 beta 7.
However, Atonement said he has 20 GB free (and is using RAR anyway) :confused: -
I created a zip file (1.5GB-named test.zip) using Beta 7. I was able to unzip without any problems. I also tested the archive and it tested fine. I created 758MB (330files) archive and it also checked out fine.
-
All files over 1gb which is strange because i have 20gb free.
I do not have a 1GB iso file. However I do have one 340MB iso.
So I made copies.4 iso files -> RAR 1.29 GB (1,386,471,671 bytes)
“Extract to folder” via shell (using PA 9.5 beta 7)
No problems encountered.My drive C: only has 1.5 GB free but my “working” drive D: has 20GB free - (Note: I activated PA “use current folder as temp” to avoid possible free disk space problem on Drive C:).
-
The problem was extracted it was 4gb and i was on my fat32 formated drive so i just converted back to NTSF( something like that)
-
OK
Thanks for coming back and telling us. -
Explains why we couldn’t reproduce it. :)
-
But there’s still a bug here - an error message should be displayed.
-
But there’s still a bug here - an error message should be displayed.
Yes, but the problem is that Windows cannot handle files of this size.
So the error message should be from Windows - not PowerArchiver. -
I’m not 100% sure, but I believe that what happens is that when a program tries to write past the 4GB file limit on a FAT32 partition the API returns an ERROR_DISK_FULL result to the calling program.
This often leads to a confusing error message (since there can be more than 4GB available on the partition), so PA may want to present it as “The disk is full or the file is too large for the destination file system.” Or something.
But in any case, it should not fail silently.
(edited)
-
We will check it out later on, thanks for clarification, although in reality move to NTFS people!!!
:-)
