W10 Pro 22H2 - 64 -bit
PA 22.00.06 (PA 2023)
It has been the case with previous versions of PowerArchiver, but I had hoped that the latest might behave differently. Not so, I’m afraid.
I have, for various obscure reasons, created a few .pa archives, mainly in the hope that they will save me some more space. From time to time, I use the “Test” option to check that important archives are OK and uncorrupted.
With every .pa archive I’ve tested, the process runs through OK but then reports that there are errors. This is always the number of files in the archive e.g. if 11 files, then 11 errors reported.
In the .pa, I can:-preview the files (usually PDF) extract some or all files and look at or use them convert the .pa to a .zip or .zipx archive, which then works fine and tests without errors
Is it the case that the Test routine isn’t designed for .pa archives, or is there another reason? Although the .pa seems to function properly, despite the test reporting errors, I would like to be sure that every .pa is OK and not “broken”.
Some of the .pas are quite old and produced with earlier PA versions (they are truly “archives”). If I extract all the files in the old .pa, create a new, fresh .pa and add back the files to that, then test the new, no errors (at least in the .pa I’ve tried this on) are reported. This would suggest a mismatch between old .pas and newer versions of PA itself.
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.
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.
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?
Crash at Exit with PA 10.2 Beta 2
PA 10.20.02 on XP x64
Open PA with an empty archive, close PA, boom
First-chance exception at 0x0049890f in POWERARC.EXE: 0xC0000005: Access violation reading location 0x1a000008.
according to VS 2005
I run windows XP Pro SP2 with the latest updates as of 2 weeks ago and installed the same PA Version but did not experience this issue??
Did you do an upgrade or a clean install??
try uninstalling the program, then delete the PowerArchiver Folder in Program Files. Reboot and re-install then to be safe restart again!
If it still happens then send an error report to PowerArchiver Support.
TBGBe last edited by
Open PA with an empty archive, close PA, boom
What is an empty archive ?
What archive format?
My mistake on the empty archive: it’s open PA without an archive loaded.
It was a clean install after a uninstallation of PA 10.2 Beta 1.
I already tried the reinstall/reboot Sir Richard suggested. Same problem.
If not already try this then (only if you know the registry)
1. Uninstall PowerArchiver 2006/07
2. Delete “Program Files/PowerArchiver” Folder
3. Delete Registry Link
then… if you have any registry cleaning software such as CCleaner or tune-up etc… do a full registry clean!
Restart then re-install…
If it still continues then it must be a fault with the program or something on your system is causing a conflict.
Tried the procedure but that did not help
However, I have more information:
the crash occurs only with the classic skin, not with the ribbon interface.
The Default blue skin works nicely.
I though it may have been Windowblinds causing the problem. I unloaded Windowblinds and run PA: with the Windows classic style, PA does not crash, with the Windows XP style, PA crashes.
That’s really odd.
TBGBe last edited by
Well, I have PowerArchiver :: Classic
Windows XP - Appearance XP Style / Color Silver
But no crash.
If you can reproduce it, provide/attach a DR Watson Log File (Zip).
Did I read the original post correct that you are using the 64bit version of XP or is it the 32?
I’m not able to reproduce, but I’m using the 32 bit, so maybe it is a 64 bit problem.
I think I reproduced the error… it ocured when I did the following
1. Open PA With Silver Default Ribbon
2. Change to Blue Default Ribbon
3. Change to silver default Ribbon
4. Change to classic
5. Change to Silver default
(I couldnt replicate it all the time only when I was clicking and changing skins like a mad man)
the errors are as follow’s (does it look familer?)
Yes, I am using XP x64. The errors reported by Sir Richard looks similar.
I will forward those results via your support page for you to look at!
Cheers crew, Vykranth Hopefully, this will support PA to amend the problem ready for the next release!
those are two different bugs - we are looking at 64bit one, already reported here while i will move sir richs to new thread…
p.s. devs on vacation until sunday, so expect new release in 6-7 days…thanks!
To be fair spywolf this is the 1st error I have personally experienced with PA in a long time!!
Looking forward to the next release, keep up the good work!
Please check with Beta 3 preview:
and let us know if it works properly now.
I don’t have the crash at exit I experienced intially.
I did have one crash when changing from the classic skin to the modern silver sking but I cannot reproduce it anymore.
I will try again later to see if I can reproduce it systematically.
Thank for the early preview. As Sir Richard said, it has been a very long time since I reported a problem in PA.
Keep up the good work