-
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?
-
Hi. The “Move” Action seems to be Not Working when used in the Tool – Batch Archive.
Using the Options – Configuration – Compression Profiles ---- I created a Profile with the Action of Move. Also set were Zip, and Method Deflate.
When I use the Tool - Batch Archive – It appears to me that the Action Move does not Move the compressed files (basically add to zip, and delete the added file from original location on the same disk). Zip file(s) are created and look ok.
Typically I on the Batch Archive process – I have selected options to use a Profile with the Move Action.
File’s Current Folder Group files from same folder into same archive Add subfolders to separate archivesMy PowerArchiver version is 21.00.17 .
Can you reproduce ? – Or do you need additional details or information?
-
Hello,
PowerArchiver Command Line 7 support file greater than 2 Go ?
Thanks
-
i just registered my own copy and i need some help to set it…
if i set the ‘configuration>shell extension>open folder after extracting’ checkbox, after decompress an archive is opened the file manager on that folder but… if somebody is using a different file manager how to open XYplorer or Directory Opus for example and NOT the MS file manager?
consider this as a feature request also if not available within the 2022 version
-
I am looking for a way to stop the UAC elevation prompt when running Powerarchiver. In an old post about PA 2019, someone asked this and got a response to uncheck “all users” at the prompt but I am not seeing where one can do this. It definitely seems like the way to go though as if I click on “More Details” at the prompt I see that it is trying to run “_pautil.exe /paassociate /allusers /my(long binary string)”. Can you let me know? Thanks.
PS I tried renaming _pautil.exe and this worked, but I don’t know what the consequence of doing this may be so I would like to do this properly, thanks.
-
Just a question is Ashampoo zip pro 4 built by Powerrachiver as it is very similar and uses the pae encryption.
-
Hi,
Is it possible to transfer one of my existing PC Licenses to my MacBook? -
Re: Transfer PC License to MacBook iOS
Here is the email…
On Tue, Jun 7, 2022 at 1:20 PM Rich DiBenedetto rmdibened@gmail.com wrote:
Greetings,
Could you assist me with this?
Can I use my current licenses with MacOS?
If not, can I transfer a license to MacOS?Cheers and Have a Great Day,
RichOn Wed, Dec 9, 2020 at 6:35 AM ConeXware, Inc. ordering@conexware.com wrote:
Dear Richard DiBenedetto,Thank you for supporting PowerArchiver! Please find your activation and registration codes below.
*** Online Activation ***
PowerArchiver Select for PowerArchiver Toolbox English - LIFETIME
is valid until - not limited.E-Mail: RMDibened@gmail.com
Activation Code: *** -
There would be many of us with Intel Processors.
and they have their own optimized zlib algorithm, which can result in more efficiency if used combined with their hardware processor.
Reference:
https://www.intel.com/content/dam/www/public/us/en/documents/white-papers/zlib-compression-whitepaper-copy.pdfCan we get the same Functionality Under Hardware Acceleration Feature?
Zlib is not the only feature that intel has included with their processor, there’s many, which if combined can result in efficient and better compression ratios.
-
a686fe8c-93a1-4830-9d01-0b9a4edd9449-image.png
Right buttons are not visible
-
Greetings, new customer searching for help and/or refund…
-
With PowerArchiver context menu enabled, it is crashing Windows 10 File Explorer when right-clicking on the Default User junction in C:\Users. Had 2021 installed, updated to today’s 2022, still getting same crash. Must have Hidden files and folders set to Show, and Hide protected operating system files cleared in File Explorer Options|View.
Windows 10 Enterprise Version 21H2 (OS Build 19044.1708) (64-bit)
PowerArchiver 2022 Version: 21.00.15 (03/2022) 64-bit
Licensed:
PowerArchiver Toolbox Edition Personal EnglishDisabling PowerArchiver context menu using Autoruns: on the Explorer tab, uncheck PowerArchiver64 under HKLM\Software\Classes\Folders\ShellEx\ContextMenuHandlers and the crash does not happen.
Could not upgrade to PA 9.6 beta 1 (9.6.0.8)
-
I upgraded from my previously 9.51
rebooted, and that’s what happens when I call the program (I’m Italian, so errors are in my language):
and then
I’m now going to uninstall it then reinstall the last beta, to see what happens.
I’m writing here because it’s really the 1st time I’ve experienced a problem when upgrading PA :(
-
I saw the second error (interface not registered) after updating a PA 9.51 to PA 9.60b1 - but I had not rebooted.
After rebooting, PA 9.60b1 is working fine.
-
I saw the second error (interface not registered) after updating a PA 9.51 to PA 9.60b1 - but I had not rebooted.
After rebooting, PA 9.60b1 is working fine.
That seems to be a problem with the dll which implements the Explorer (shell) options - it is replaced and a reboot is needed.
Not sure about “manuangi’s” first problem. Was the previous version (9.51) using a different skin (non-default) perhaps?
As a “general rule” I would not advise << upgrading >> to a ‘beta’ version of any software. I always do a clean install (uninstall previous/reboot/install ‘beta’).
Still feedback that there was a problem is useful.
-
definetly an old skin. We have to be able to handle that better.
thanks!
-
I saw the second error (interface not registered) after updating a PA 9.51 to PA 9.60b1 - but I had not rebooted.
After rebooting, PA 9.60b1 is working fine.
what OS are you using?
-
definetly an old skin. We have to be able to handle that better.
thanks!
yea, I was using the “bunnies” skin that I love so much :)
so, spwolf, what’s your advice about how to proceed?
thank you
-
try deleting the skin that you were using? If not, you can uninstall it and install it again, which will delete the registry keys…
thanks!
p.s. what OS?
-
try deleting the skin that you were using? If not, you can uninstall it and install it again, which will delete the registry keys…
thanks!
ok…but I really loved the bunny-skin :(
p.s. what OS?
WinXP SP1
-
I think restart is the most important step here, so please restart your computer when installation tells you so!
thanks,
-
I always did, if you read my previous posts.
anyway, uninstalling/reinstalling PA did the trick
can I apply my bunny skin again, or you think there could be problems?
-
skinning engine is completly new, only toolbars will work (complete skin wont)…
-
what OS are you using?
WinXP SP2.
Note that I did not consider the error message I saw to be a bug - the update told me that I had to reboot, but I generally ignore those messages unless I run into problems because reboots are often not really necessary for many products - the install process is just being overly conservative.
However, if you can workaround the need to reboot, obviously that would be a plus!
-
WinXP SP2.
Note that I did not consider the error message I saw to be a bug - the update told me that I had to reboot, but I generally ignore those messages unless I run into problems because reboots are often not really necessary for many products - the install process is just being overly conservative.
However, if you can workaround the need to reboot, obviously that would be a plus!
Did you install PA in same folder as before or in new folder? Did you keep old version installed?
I noticed one case where installer would not register skin dlls until reboot, but in that case PA would have tell you that you cant install until reboot and you would have to delete your registry key for pending renames, which is probably not what you did?
thanks,
-
Did you install PA in same folder as before or in new folder? Did you keep old version installed?
I noticed one case where installer would not register skin dlls until reboot, but in that case PA would have tell you that you cant install until reboot and you would have to delete your registry key for pending renames, which is probably not what you did?
thanks,
I just installed the beta over the existing install (I’m wreckless sometimes). No problems - it told me to reboot, but I didn’t (wreckless…) and it gave the interface registration error when I tried to start PA. After a reboot I tried again, and everything is working fine.
-
… can I apply my bunny skin again, or you think there could be problems?
Not sure what “bunny skin” is.
If you mean “Rabbit XP” then that is a toolbar and not a skin, so…
@spwolf:skinning engine is completly new, only toolbars will work (complete skin wont)…
Maybe? {Can’t try it myself at moment sorry… }
-
Not sure what “bunny skin” is.
If you mean “Rabbit XP” then that is a toolbar and not a skin, so…skinning engine is completly new, only toolbars will work (complete skin wont)…
Nope.
Doesn’t work - or at least I cannot see how to apply the “old” toolbar button “skins”. :confused: -
Config> Skins & Toolbar :-).
-
Config> Skins & Toolbar :-).
:o I was trying via
Options - Skins …
Skins(right click) …
Select Buttons …Missed the Config settings :o
OK it does work.
