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?
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.
Here is the email…
On Tue, Jun 7, 2022 at 1:20 PM Rich DiBenedetto email@example.com wrote:
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,
On Wed, Dec 9, 2020 at 6:35 AM ConeXware, Inc. firstname.lastname@example.org 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.
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.
Can 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.
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
PowerArchiver Toolbox Edition Personal English
Disabling PowerArchiver context menu using Autoruns: on the Explorer tab, uncheck PowerArchiver64 under HKLM\Software\Classes\Folders\ShellEx\ContextMenuHandlers and the crash does not happen.
when clciking on powerarchiver update from within powerarchiver we get a windows for the update but it nows sayes script errors. I think it could be due to windows update in windows 10 can you look into it. By pressing cancel it seems to be ok. It seems that the page being displayed as erros on it.
From within PA on the extract popup, buttons are hidden, I must resize the window to get access to the OK/Cancel buttons. Tried on the default notebook screen (Macbook M1 Max 14") as well as on my external monitor (4k).Screenshot_2022-05-12_10-02-10.jpg
Ho già contattato il supporto con il modulo presente qui https://www.powerarchiver.com/it/contact/ da settimane ma non ho ricevuto riscontro e ora che ho aggiornato alla versione 21.00.15 ho notato che il problema persiste.
Quando clicco PDF Encrypt & Sign nel tab Crittografia appare la schemata riportata sotto come se mancassero le funzionalità.
I’ve already contacted support with the form here https://www.powerarchiver.com/it/contact/ weeks ago but I haven’t received any feedback and now that I’ve updated to version 21.00.15 I’ve noticed that the problem persists.
When I click on PDF Encrypt & Sign in the Encryption tab the schematic below appears as if the functionality is missing.
I have tried to burn a DVD with PowerArchiver 2022 Final, but it didn’t work because PA didn’t found the external DVD-Burner.
I have tried several burners from Sony, LG, Dell.
I have connected the burners with several USB-Ports but unfortunately without any success.
With other burning software, e. g. Nero, all burner worked perfect on each USB-Port.
The same problem occured with PA2018 and it was solved with an update, but I don’t remember the detailed software version.
Could you check the possibility of an bug, please?
Thank you for your support in advance!
UNSOLVED PGP Keys
I’ve had this issue for awhile now (ever since they added PGP support) but the key info some how gets truncated so it doesn’t have the full name when imported. It’s the only PGP “program” that I have used that doesn’t correctly import the keys. It still has not been resolved even in the latest build and I was just wondering what the status of the fix is.
We recently bumped the bug report for the dev team to do their best to implement the improvement as soon as possible.
I have confirmed that your previous reports through support are attached to the bug report in the dev stream and we will let you know once the fix is implemented and we’ll send you a version to test out and confirm. I’ve also added this thread to it.
Apologies for the delay, plenty of stuff being worked on and PGP should come up soon.
Thanks for letting us know.
Thanks, I appreciate that