-
Dear @Alpha-Testers and all of our users,
time has come for testing of PowerArchiver and PACL for macOS.
Please let us know here if you have Mac and can test latest builds.Features implemented:
PowerArchiver 2020 - tabbing, opening, extracting, adding, testing, favorite folders, support for multiple languages, opening via Finder, explorer mode, installer.
PACL 10 - support for most formats and features in Windows version.Upcoming: Tools such as archive converter, batch zip, multi-extract.
To start testing, please sign up here in this thread, and we will send you latest build.
thank you!
Ashampoo_Snap_Wednesday, November 20, 2019_12h54m56s_008_.png Ashampoo_Snap_Wednesday, November 20, 2019_12h55m05s_009_.png Ashampoo_Snap_Wednesday, November 20, 2019_12h55m14s_010_.png Ashampoo_Snap_Wednesday, November 20, 2019_12h55m30s_011_.png Ashampoo_Snap_Wednesday, November 20, 2019_12h55m39s_012_.png Ashampoo_Snap_Wednesday, November 20, 2019_12h55m49s_013_.png Ashampoo_Snap_Wednesday, November 20, 2019_12h56m00s_014_.png Ashampoo_Snap_Wednesday, November 20, 2019_12h54m43s_007_.png
76e97ab9-8d75-4175-9ce8-446500031f38-image.png
-
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.
-
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 errorsIs 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.
-
PA 21.00.18 running on Windows 7 64 bit.
I made a big .PA file and thought I’d check it was made correctly with Menu / Actions / Test.
Discovered:
a) PA always issues a UAC prompt to do this!
b) PA always says there are many errors in PA files. -
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.Dariusz
-
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,
Problems with PowerArchiver U3 2009 in Vista 32
-
Hi,
I just downloaded and installed PowerArchiver U3 2009 (V11.03.03) on my SanDisk U3 stick.
PowerArchiver itself is running fine from the stick. My problem starts when I try to eject the stick.
When I close PowerArchiver U3 the powerarc.exe and launcher.exe processes are stopped. Now, when I try to eject the stick with the Eject button from the U3 Launchpad, I got a warning message that PowerArchiver is still running and the Launcher.exe process is started again and is running with 50% CPU load (DualCore processor here). Each additional try to eject the stick results in starting another copy of the launcher.exe process.
The same happens when I eject the stick with the Windows function “Safely Remove Hardware”. Only in this case I get no warning message that PowerArchiver is still running but Launcher.exe is still started with 50% CPU load.
Any ideas ???
FreeBird
-
It looks like it’s working fine in Windows XP SP3.
So the problem occurs only in Windows Vista.Any ideas ?
FreeBird
-
Thanks FreeBird! Issue was reproduced and forwarded to the developers. We’ll see what they can do about it.
-
weird issue, do you use U3 for other software as well?
-
Hi spwolf,
yes, I’m running some other U3 programs (like UltraCompare UC3, UltraEdit UE3, TotalCommander, Putty, WinSCP, …) without any problems in Windows Vista. Only PowerArchiver gives me problems at the moment.
FreeBird
-
thanks, maybe our SDK is out of date or something, did you try PA 2007 previously on same computer?
-
thanks, maybe our SDK is out of date or something, did you try PA 2007 previously on same computer?
I’m sorry, no. But I could. If you give me a download link for the old version. Is the new license key compatible with the old version?
FreeBird
-
I will try to find it and send it over…
-
Any news about this issue ?
FreeBird
-
Bump!
Anyone home???
-
i need to find that 2007 versions… stay tuned.
-
Here you go:
http://www.powerarchiver.com/test/alpha100/pa_10.22.02.u3pcheck it out…
-
Sorry, can’t download from the above link. I’m coming back to the default download page.
FreeBird
-
Sorry, wrong one:
http://www.powerarchiver.com/test/release100/pa_10.22.02.u3pthanks!
-
Sorry, wrong one:
http://www.powerarchiver.com/test/release100/pa_10.22.02.u3pthanks!
Sorry, same problem.
FreeBird
-
probably then due to the older version of sdk we used for U3….
It will be fixed in 11.5 release.
-
Ooops, sorry,
what I meant is that the second link you posted is also not working.
But don’t worry, I will wait for V11.5.
Thanks anyway for your help
FreeBird
-
-
Hi spwolf,
just tested the version you provided (10.22.02). Exactly the same problem as in version 11.03.03.
Launcher.exe uses 50% CPU load on Vista Ultimate after removal of the U3 stick.
So I’m waiting patiently for version 11.5 :)
FreeBird
-
ok… i have logged it in our bug tracking system already, it is just waiting for more time…