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 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.
Access Violation on Install
I tried to install 9.63.02 on a new laptop and I get the following error when the application starts. I have tried uninstalling and reinstalling with a reboot in between.
Registration has no effect on this behavior.
Access violation at address 007ACD33 in module ‘POWERARC.EXE’. Read of address FFFFFFFF.
When I hit OK the application loads but none of the buttons show.
On a side note I could not figure out how (help anyone?) to get the images I loaded as attachments to show up inline with this post, hence the links.
What OS are you using?
guido last edited by
It looks like 98
Windows XP SP2.
The only thing odd about the systems is that there are some tightened security controls enabled in various places. I am not sure of all the details of the hardening that was done to the system.
For example parts of the registry or file system could have non-standard (i.e. default install) security controls in place.
I do have administrative privileges on the system.
The only change I made the debug output was to change the computer name and user name to obfuscate the identity.
date/time : 2007-02-10, 08:24:04, 197ms
computer name : mysystem
user name : pa-user
operating system : Windows XP Service Pack 2 build 2600
system language : English
system up time : 49 minutes 4 seconds
program up time : 3 seconds
processor : Intel® Pentium® M processor 1.73GHz
physical memory : 408/1015 MB (free/total)
free disk space : (C:) 53.38 GB
display mode : 1024x768, 32 bit
process id : $514
allocated memory : 6.28 MB
executable : powerarc.exe
exec. date/time : 2006-12-10 10:28
version : 184.108.40.206
madExcept version : 2.7g
exception class : EAccessViolation
exception message : Access violation at address 007DB20F in module ‘powerarc.exe’. Read of address FFFFFFFF.
main thread ($794):
00400000 powerarc.exe 220.127.116.11 C:\Program Files\PowerArchiver
01b70000 unrar3.dll 18.104.22.168 C:\Program Files\PowerArchiver
020b0000 cabinet.dll 1.0.603.0 C:\Program Files\PowerArchiver
10000000 PAISO.DLL 22.214.171.124 C:\Program Files\PowerArchiver
20000000 DZIPS32.DLL 126.96.36.199 C:\Program Files\PowerArchiver
30000000 DUNZIPS32.DLL 188.8.131.52 C:\Program Files\PowerArchiver
5ad70000 uxtheme.dll 6.0.2900.2180 C:\WINDOWS\system32
5edd0000 olepro32.dll 5.1.2600.2180 C:\WINDOWS\system32
63000000 WBOCX.OCX 184.108.40.206 C:\WINDOWS\system32
71aa0000 WS2HELP.dll 5.1.2600.2180 C:\WINDOWS\system32
71ab0000 WS2_32.dll 5.1.2600.2180 C:\WINDOWS\system32
71ad0000 wsock32.dll 5.1.2600.2180 C:\WINDOWS\system32
73000000 winspool.drv 5.1.2600.2180 C:\WINDOWS\system32
73b30000 mscms.dll 5.1.2600.2709 C:\WINDOWS\system32
73dd0000 MFC42.DLL 6.2.4131.0 C:\WINDOWS\system32
755c0000 msctfime.ime 5.1.2600.2180 C:\WINDOWS\system32
76380000 msimg32.dll 5.1.2600.2180 C:\WINDOWS\system32
76390000 imm32.dll 5.1.2600.2180 C:\WINDOWS\system32
763b0000 comdlg32.dll 6.0.2900.2180 C:\WINDOWS\system32
76600000 CSCDLL.dll 5.1.2600.2180 C:\WINDOWS\System32
76b40000 winmm.dll 5.1.2600.2180 C:\WINDOWS\system32
76fd0000 CLBCATQ.DLL 2001.12.4414.308 C:\WINDOWS\system32
77050000 COMRes.dll 2001.12.4414.258 C:\WINDOWS\system32
77120000 oleaut32.dll 5.1.2600.2180 C:\WINDOWS\system32
773d0000 comctl32.dll 6.0.2900.2982 C:\WINDOWS\WinSxS\x86_Microsoft.Windows.Common-Controls_6595b64144ccf1df_6.0.2600.2982_x-ww_ac3f9c03
774e0000 ole32.dll 5.1.2600.2726 C:\WINDOWS\system32
77920000 SETUPAPI.dll 5.1.2600.2180 C:\WINDOWS\system32
77a20000 cscui.dll 5.1.2600.2180 C:\WINDOWS\System32
77a80000 crypt32.dll 5.131.2600.2180 C:\WINDOWS\system32
77b20000 MSASN1.dll 5.1.2600.2180 C:\WINDOWS\system32
77b40000 appHelp.dll 5.1.2600.2180 C:\WINDOWS\system32
77c00000 version.dll 5.1.2600.2180 C:\WINDOWS\system32
77c10000 msvcrt.dll 7.0.2600.2180 C:\WINDOWS\system32
77d40000 user32.dll 5.1.2600.2622 C:\WINDOWS\system32
77dd0000 advapi32.dll 5.1.2600.2180 C:\WINDOWS\system32
77e70000 RPCRT4.dll 5.1.2600.2794 C:\WINDOWS\system32
77f10000 GDI32.dll 5.1.2600.2818 C:\WINDOWS\system32
77f60000 SHLWAPI.dll 6.0.2900.2995 C:\WINDOWS\system32
77fe0000 Secur32.dll 5.1.2600.2180 C:\WINDOWS\system32
7c800000 kernel32.dll 5.1.2600.2945 C:\WINDOWS\system32
7c900000 ntdll.dll 5.1.2600.2180 C:\WINDOWS\system32
7c9c0000 shell32.dll 6.0.2900.2951 C:\WINDOWS\system32
7e1e0000 hhctrl.ocx 5.2.3790.2744 C:\WINDOWS\system32
007db20f sub_7db20f: ; function entry point
007db20f > cmp byte ptr [edx+eax-1], $5c
007db214 jz loc_7db223
007db216 lea eax, [ebp-$20]
007db219 mov edx, $7dce9c
007db21e call -$3d5d63 ($4054c0)