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.
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.
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.
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
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.
Drag and Drop Bug w/ Multiple Monitors
There’s a bug in 11.50.23. It’s existed for quite some time really, I just never bothered to report it before. I figure since you’re in a beta phase, now’s as good of a time as any. :)
I have a multiple monitor setup. If I have PowerArchiver on the secondary monitor (e.g. the one without the taskbar) and drag a file from an archive into an explorer window, the PowerArchiver window will disappear and reappear on the primary monitor.
It seems that the disappear and reappear act is due to showing the progress window. After testing with a larger archive, that’s exactly what happens: The main window disappears, the progress window appears (on the primary monitor), then the main window reappears on the primary monitor instead of the secondary monitor where it was originally.
Bump. Bug still exists in 11.50.37 (Beta 2).
Child dialogs (e.g. Configuration Window, About Screen) also don’t show up in the correct place when PA is on 2nd monitor. They’re showing up on the main monitor.
I’m going to dig around a bit. I wonder if this is a VCL bug?
I would also like to vote (again) to have these little multimon problems fixed.
thanks for the bumps… we will take an look.
Please check beta 3 via web update or download page and let us know if this issue has been fixed… thank you!
Yes, this is fixed all around for me with Beta 3 on XP SP 3. The progress window shows up where the window was, and the main window returns to its original position. Thank you!
There’s still a very minor bug in that if the child window to be shown is larger than the main window, and the main window is near the edge of the screen (or near the edge of a monitor), then the child dialog/window may show up partially off screen. But that’s a pretty minor thing.
screenshot for that issue?
Sure. Pic 1 shows the “ready” state. I positioned PA’s window near the edge of my monitor.
Then I went to open the configuration window. Since it’s larger than the main window, it completely obscures the main window. This is fine. The problem is it’s “centered” over the main window, so part of the window hangs offscreen. This is what pic 2 shows.
The same effect happens on a multi-monitor setup, only the child window shows up partially on the other monitor, but it’s harder to provide screenshots for. And you probably don’t want to see crappy pics from my cell phone. :)
so you want it centered on screen instead of PA?
No, centered over PA is great, just nudged to ensure that the entire window is on the current monitor.
It’s a very minor thing to me, and if it’s more trouble than its worth to fix, I’d rather see the current behavior over any other.