-
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.
Multiple steps to get better compression
-
I’m using the latest build of PowerArchiver 2016 16.00.69
I have gone through the Compression Profiles settings and set it up just the way I want it, regarding 7-zip format, but others also.
I now right click and select “Compress to xxxxx.7z” for it to compress with all options I have already set up for 7-zip, I assume.
However, the file size I get using the above method is ALWAYS bigger (i.e.: compression isn’t as good), as if I right click and select “Compress to 7-Zip + Options” and then just click Add.
PS: The settings on the “Compress to 7-Zip + Options” are the same as I have already set up in the Compression Profiles pages.
So why do I have to perform this multiple click process to get the best compression, when just right clicking and selecting straight to 7-Zip compression should get me the same compression as the multiple click process?
-
hello,
what compression method is selected in the created 7z profile?
-
hello,
what compression method is selected in the created 7z profile?
Generally, its LZMA2, but whichever it is, its the same as the test I perform using the multiple step process.
So I am testing like for like here, not two different compression methods.
-
Hello,
What kind of a file are you compressing where you notice the difference?
Also, please export your settings by going to Options>Save Settings to file" then compress them into a 7z or a Cab file and send them over to support at conexware dot comWe will then try it out with your exact settings on a similar file as you and and see what we come up with.
thanks!
-
I just got the same issue right now with RAR files this time.
The file I’m compressing is called Ricochet Xtreme.exe and its 7,336KB in size.I set up the RAR Command Profile to have Maximum Compression and Default RAR5 Method with Solid Archive enabled.
I compress the file by right clicking and selecting “Compress to xxx.rar”. The file size is 7,306KB.
I now right-click and select Rar + Options and select Maximum Compression and Default RAR5 Method with Solid Archive enabled. I click add, and the file size is 7,304KB.
Not much difference I know, but there should be NO difference at all, since its just the same compression just done a different way.
Tried it more than 5 times each way, and the same results each time.
-
I just got the same issue right now with RAR files this time.
The file I’m compressing is called Ricochet Xtreme.exe and its 7,336KB in size.I set up the RAR Command Profile to have Maximum Compression and Default RAR5 Method with Solid Archive enabled.
I compress the file by right clicking and selecting “Compress to xxx.rar”. The file size is 7,306KB.
I now right-click and select Rar + Options and select Maximum Compression and Default RAR5 Method with Solid Archive enabled. I click add, and the file size is 7,304KB.
Not much difference I know, but there should be NO difference at all, since its just the same compression just done a different way.
Tried it more than 5 times each way, and the same results each time.
you can set RAR command line options as you wish in Config…. there are a lot of switches that can be used.
-
you can set RAR command line options as you wish in Config…. there are a lot of switches that can be used.
Well, its set as the defaults in ALL cases.
I haven’t changed that in either case.I’ve run a lot of other tests, and the same result is happening all the time.
-
Thanks for the info. I have tested a similar scenario compressing a RAR with compression profile options and then compressing into a RAR using the same options but in Compress w Options. The file sizes did turn out to be different so I’m logging this in so we can check it out.
thanks!
-
Great.
Its good to be believed that a problem did exist.The same issue also happens with 7zip also.
-
picture tutorial :-)
-
picture tutorial :-)
And?
What does that mean?I already know about those settings…and surely they affect ALL RAR compression, no matter the method.
-
And?
What does that mean?I already know about those settings…and surely they affect ALL RAR compression, no matter the method.
change your setting to indicated above and try compression test again. Thank you.
-
change your setting to indicated above and try compression test again. Thank you.
Just did. And as I suspected, the results are exactly the same as before….the file sizes are indeed different each time…
Issue STILL exists…
-
Just checked mine and my RAR Maximum is different -> -m5 -mdg -mc10:128t
-
Just checked mine and my RAR Maximum is different -> -m5 -mdg -mc10:128t
That’s what I had also.
But I changed it to just -m5 as suggested and ran the tests again, and that’s what I was talking about.
-
Just checked mine and my RAR Maximum is different -> -m5 -mdg -mc10:128t
there were 2 problems, first setting was not compatible with later WR versions… so it was fixed. And then compress to .rar always used default one (compress with options used config setting as it should). Now both of these should work fine, check it out:
http://dl.powerarchiver.com/2016/powarc160204.exe -
I just got the same issue right now with RAR files this time.
The file I’m compressing is called Ricochet Xtreme.exe and its 7,336KB in size.I set up the RAR Command Profile to have Maximum Compression and Default RAR5 Method with Solid Archive enabled.
I compress the file by right clicking and selecting “Compress to xxx.rar”. The file size is 7,306KB.
I now right-click and select Rar + Options and select Maximum Compression and Default RAR5 Method with Solid Archive enabled. I click add, and the file size is 7,304KB.
Not much difference I know, but there should be NO difference at all, since its just the same compression just done a different way.
Tried it more than 5 times each way, and the same results each time.
this a file that is so small and if we compress small file so it change alittle bit
like if you change a picture with 793KB after compress it would be 792KB or 792.5 KB because the picture size is so less and if we compress a file with 1.3GB after compress it would be 1.2GB or 1.1GB which reduce up to 100MB size
so file compressing belong to file size
and the file you want to compress is so small ( about 7MB) so if you compress this file it would be about 6.8MB
hope to find the answer -
Do did the problem with 7z files mentioned in #1 exist or not?
If so is it fixed or not? -
Hi Brian,
We’ve just tested two files, a 170mb file and a 1GB file, via Compress to 7z and Compress w options>7z
Compression profile changed to LZMA2 Ultra.
Also tried with LZMA Ultra.In both cases, both files resulted in same file size of the compressed 7z file.
Seems fixed.If you happen to come across a specific situation where the issue seems present, please let us know and we’ll test immediately.
Thanks!
