-
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.
-
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. -
I installed powarc-macos20001.dmg and I am attempting to create a password protected zip file. When I create the zip in the UI it doesn’t write the file to the destination folder. No error message is displayed. The PA app has full folder permission. I’m new to Mac, but have been running PA on Windows for a long time.
Will there be a new version of the Mac version soon?
-
Hi! I came across an issue when I tried to uninstall PowerArch 2013. I got an error “The specified account already exists” which broke the process. I got the same error when I tried to install the current version, without uninstalling the previous one.
So I can’t uninstall and I can’t install PowerArchiver. Any suggestions? OS Windows 8.1 x64.Dariusz
-
Where are various settings store . . . e.g. ftp, etc.
-
d40b03ac-1a7a-4358-8d6c-0ec7f455de04-image.png
should the image have a white background?
-
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).
-
Powerarchiver 2022
Right-click and select Encrypt on a folder does not work.
Although it says it encrypts, there is no encrypted file in the destination folder. -
The online update feature within the program suggests there is a later version than the ‘.17’ available on the web site. But clicking either download or update just reinstalls version .17.
Either there isn’t an update OR
the “download” and 'update" links should be repaired. -
Hi Dear,
Cannot login and request resend license code for my fd
-
Hi,
When you click on the Buy Now link, you come across four tabs - Home or Work, Enterprise Unlimited, Educational Discount, & Gift Discount.
What is the difference between a licence purchased via Gift Discount and a Home/Work licence?
Also, how can I renew the PowerArchiver Select plan a year after the purchase? Will it remind me automatically?
Best,
-
I’m running PA 21.00.17 64-bit on a 64-bit i7 desktop with W10 Pro, latest version. This 32gb of installed RAM.
As I use the PA pbs system for a number of scheduled archiving operations throughout the day, PA Starter is set to load and run at system startup.
In the course of trying to identify some causes of slowness and bottlenecks in other processes, I notice that PA Starter (PAS) always runs at between 11% and 15% of CPU (see screenshot), usually at about 12-13%. This is by far the highest demanding process on the system, as shown by Task Manager. In Performance Monitor, PAS Average CPU is 8.32, with every other process at less that 1 i.e. in decimal places only.
Task Manager also shows PAS Power Usage as “Very High”, and is the only process shown thus.
I have looked again at the information about PAS at https://wiki.powerarchiver.com/en:help:details:powerarchiver_starter, which was last modified in 2016. The article states a low memory usage for PAS of 784k, which is fair enough, but it is the large CPU overhead which is of concern.
It is of course possible to change the PAS priority, but this has no effect on CPU overhead.
However, is it possible to change PAS, which is required only at intervals to initiate PA scheduled tasks, from consuming so much system resource for every moment of the day?
PA Starter.jpg
-
I’m experiencing very slow extraction speed of multipart RAR files. For the first part the extraction is super fast but when PA reaches the part2.rar the extraction from there on gets super slow. PA needed for a 6,3 GB multipart archive 30 minutes to extract. I tested then with another program and it just took 70 seconds. I had this slow extraction speed with PA for quite a long time and I always thought that is maybe because of a high compression rate that the extraction would take longer. But it seems that only PA gets that slow.
I have lots of multipart archives that are 10+ GB and with PA it would be really time consuming. Is there any solution to this?
Bug in 7z archives properties
-
when you create a 7z archive and then check its properties via PA, sometimes PA will fail to tell its compression, stating 0% when it’s not true…
For example, download this 7z archive:
[http://greg79.altervista.org/sw/debian jigdo-win-0.7.1a.7z](http://greg79.altervista.org/sw/debian jigdo-win-0.7.1a.7z) (right click and save)Then open it with PA (I’m using 9.11.01), and see that it states it has a 0% compression, while it hasn’t obviously.
Open it with WinRAR, for example, and it’ll correctly say
Uncompressed size: 2.515.893
Compressed size: 781.091
Compression ratio: 31%If it worked, PA would say 69% (to 100).
Can anyone of you confirm that, and check with some 7z files of your own?
Thanks! -
I can confirm this!
I have downloaded your archive and I have tha same problem (0%)
Also I created my own 7z archives… the same problem…Thanks,
-
any news about this, spwolf? :rolleyes:
-
any news about this, spwolf? :rolleyes:
Hi,
As mentioned in another thread, current PA does not display this info for 7zip files (under filelist either). Once we implement new 7zip code, you will be able to see this info, where available (unless it is solid archive I assume). We will have to redesign the properties window in any case, as mentioned on the wishlist.
thanks,
-
Hi,
As mentioned in another thread, current PA does not display this info for 7zip files (under filelist either).
this is not true…
in fact, I have that issue only with some 7z files, not with all of them!!look!
with the above file, all works perfectly…and it’s a 7zip file!
so,I think this is a bug, not a missing feature…
by the way…both files, are files I compressed to 7zip with PowerArchiver…and my settings for compressing include the “solid archive” option…so both files are solid archives.
what do you think?
-
Well, you are correct - 7zip saves original file size anyway.
Upon checking it a bit more - it is because of using Explorer view. It works just fine under Classic view. It seems that for 7zip, PA displays current archive path compression size info, while for other formats it shows overall info (size) at all times.
So reason % doesnt work in this case is because its compressed size is bigger than original file size and it really does not know what to do then.
thanks,
-
It seems that for 7zip, PA displays current archive path compression size info, while for other formats it shows overall info (size) at all times.
So reason % doesnt work in this case is because its compressed size is bigger than original file size and it really does not know what to do then.
I can’t understand…
what is bigger than original file size? the 7z archive’s uncompressed size is 2.515.893, its compressed size is 781.091…
what do you mean by “current archive path compression size”?
anyway, you’re right…under classic style view compression properties are correctly shown.
but, eventually, don’t you think this is a bug? I sure do.
-
If you check at the status bar, you will see that it shows current uncompressed data for FILES in the PATH that you are currently in. This means when calculating % in the properties, it comes out to negative since uncompressed size is less than compressed size. If you check at the status bar, you will see what I mean. When you go throught paths, you will notice how the values change and they should not for this purpose.
I think it is actually useful since you can now see current path info however it really should work as in Classic mode and that way compression % would be correct as well. It will be our priority to fix this BUG for next version.
thanks,
-
If you check at the status bar, you will see that it shows current uncompressed data for FILES in the PATH that you are currently in. This means when calculating % in the properties, it comes out to negative since uncompressed size is less than compressed size. If you check at the status bar, you will see what I mean. When you go throught paths, you will notice how the values change and they should not for this purpose.
ooh, ok, now I understand!
I think it is actually useful since you can now see current path info however it really should work as in Classic mode and that way compression % would be correct as well.
right! :)
It will be our priority to fix this BUG for next version.
thanks
thank you!
-
at least, for the file in my first post!
I’ll be checking with some other ones!in the meantime, very well done, guys!! :)
