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).
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.
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?
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’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 archives
My PowerArchiver version is 21.00.17 .
Can you reproduce ? – Or do you need additional details or information?
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 firstname.lastname@example.org 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. email@example.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.
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.
Lately I’ve been experiencing application crashes with with PABACKUP.EXE. Here is the Event information offered by the Windows Application Log (let me know if you need more details):
Faulting application name: PABACKUP.EXE, version: 22.214.171.124, time stamp: 0x2a425e19
Faulting module name: PABACKUP.EXE, version: 126.96.36.199, time stamp: 0x2a425e19
Exception code: 0xc0000005
Fault offset: 0x000041da
Faulting process id: 0xcd4
Faulting application start time: 0x01cc5fb1ffa1369e
Faulting application path: C:\Program Files (x86)\PowerArchiver\PABACKUP.EXE
Faulting module path: C:\Program Files (x86)\PowerArchiver\PABACKUP.EXE
Report Id: 3d59a85f-cba5-11e0-bbed-7071bce3eb99
This started happening under version 11.71 and continued after I upgraded to version 12. I have even uninstalled version 12 and re-installed from scratch.
I’m running Windows 7 64-bit and I launch my PA backup jobs using Splinterware’s System Scheduler 4.17.
In System Scheduler I use the Sequence of Events scheduling type in order to launch multiple backup jobs sequentially (I switched to this method when the PA Queue feature proved too problematic with frequent failures).
Thanks in advance for any help with this.
You will most likely be asked by the devs if you have the same problem if you don’t use “Splinterware’s System Scheduler 4.17” So it would probably help them to know that.
I’ve installed splinterware system scheduler and scheduled a pbs script there to be run.
Once the selected time came up, the script ran and created my backup with no issues.
Does this error occur for you with all pbs scripts or just one?
If you can, please send us a sample script which does not work for you along with a screenshot of the settings for that scheduled event/script in Splinterware System Scheduler.
You can send it to support at conexware dot com
Thanks for your reply and thanks for your help.
This issue is becoming a real brain teaser as I am pouring over the Windows event log to find anything that could cause this crash.
Just like you, I can’t duplicate the crash at will. System Scheduler is not the culprit here, as it does exactly what it is supposed to do. As a matter of fact, it ran successfully at 2:30am this morning - no crash this time.
I am currently looking at the possibility of some sort of conflict with VSS. The VSS service stops due to idle timeout and perhaps that causes a problem when PABACKUP.EXE starts.
I was hoping the crash information provided through the event log might help you pinpoint some sort of problem area. If that is not the case then there is not much else you can do at this juncture.
I will keep plugging away at this and will provide updates here.
If you have any thoughts on the VSS angle please let me know.
VSS was not used with PA 2010 though, so it should be not influencing factor with the issue.
Did you try using different compression? What are other PBS settings, for instance are always new files created, or is old backup file updated?
is there another process running in the background when pa backup is used.
does differnt backup scrips work ok?
when did you create the backup script i mean what version of pa was the backup script made in.
I’m closing this thread. Thank you to all for your replies. :)
As it turns out the System Scheduler utility has failed to properly execute an automatic Windows login, so when PABACKUP is scheduled no user is logged in, causing PABACKUP to crash (perhaps not very elegant programming!).
Before I run all of my backup scripts, I schedule a series of housekeeping activities (closing applications, running CCleaner) followed by a system restart. System scheduler has a setting to automatically initiate a Windows auto logon and this works well in Windows XP, but has stopped working in Windows 7.
I’ve had to find a different way to initiate a forced Windows auto login (I’m not relying on System Scheduler for this any more). Problem solved.
Thanks again. :)