-
PA 2023 22.00.08
Long time no seeing. So I start up the new year with a first problem : the virtual driver cannot be installed. Reason : it is missing in the Fast Ring PatchBeam Update Service…
Virtual driver PA 2023-01-28 152607.png
It seems a standard problem with new releases :-)
Can I have a link or can it be fixed. Thank you. CU later -
When the function for testing archives is invoked via the shell context menu (PowerArchiver > Test) then all the files in the archive get extracted to the current folder.
The test dialog reports as many errors as there are files in the archive but it fails to give any hint as to which files are supposed to be erroneous or what the nature of the problem might be. Comparing the extracted files to the originals shows no differences at all.
The .7z in question was produced with maximised compression settings in 7zip (taking forever but resulting in smaller archives than .7z produced by PowerArchiver with maximised settings). Therefore I wanted to see whether PowerArchiver can at least test .7z that it produced itself. Hence I had PowerArchiver convert a .pa with the same contents to .7z. There weren’t any errors reported but the resulting .7z contained fewer than half of the files contained in the .pa (137 of 366), so I scratched that test.
Performance is abysmal when testing via the context menu (e.g. almost 2 minutes for testing a .7z that 7zip tests in 4 seconds), but that is most likely due to the fact that the extracted files are written to disk. Testing the same .7z in the PowerArchiver GUI takes only 8 seconds but causes the mysterious appearance of a UAC dialog, as reported elsewhere.
The testing function is vital because PowerArchiver has a history of producing archives that it cannot unpack without errors or that do not conform to the respective file format standards (e.g. ZIP) so that other programs report them as erroneous.
The point of creating archives is that the files in them will most likely have to be extracted at some point. If the extraction cannot be guaranteed to produce correct results then the whole program is absolutely pointless. Actually, worse than pointless - it causes data loss and hence damage.
-
In PowerArchiver 2023 22.00.06 configuration, the option labelled “Start PowerArchiver 2023 Starter when my computer starts” seems to be redundant.
I am only allowed to change this option when PA Starter is disabled, and then it seems to be ignored.
When I enable PA Starter this option is forced to the enabled state.
I think it’d be good to remove “Start PowerArchiver 2023 Starter when my computer starts” completely. I’ve always found it confusing having both options.
Added later: However i don’t particularly want to use queue but I do like having the PAStarter icon in my tray area.
-
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. -
Clipboard02.jpg
See the, supposedly, blank space where the green box is? It’s like that in Modern Light theme too. I can toggle it, but it’s missing text or shouldn’t be there I guess?
Thanks :)
-
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.
Bug & more - Runtime error 217
-
Bug - random runtime error when extracting ZIP archives. Don’t know if it happens with other type of archives, but with zip files happens a lot.
More - PA can extract self-extraction zip archives but can’t explore them, only showing a file named “[NSIS].nsi”. Almost all free file archivers can do this.
-
Hello, please email support at support@conexware.com , so we can send you debug version… also send us an link to that SFX file as well so we can add better support.
We did not have any reports of this error before so debug version is necessary to catch the problem.
Thank you!
-
Please also send us your settings (Export option), make sure you .cab the .reg file so it can pass the filters… that will be very helpful! Thanks!
-
Reinstalled PA (repair) and the runtime error keeps appearing (random but with high rate).
Have been trying to replicate it in two virtual machines with Windows 8 and Windows XP (VirtualXPVHD from Windows XP Mode) but, so far, I couldn’t do it.
Maybe it’s related to my PC or OS setup (Windows XP SP3 32bits), but I don’t have any issue with other applications or file archivers. It only happens with PA.Update: It happens with all kinds of archives. I can replicate the error by doing the following steps:
1. Open any archive with PA. Drag and drop some of the archive files to an exctraction folder.
2. Do not close the PA window from step 1.
3. Select another archive using the Windows explorer or the PA explorer from step 1, and use the shell context menu option "extract to folder "
4. Loop 1-4Sometimes I don’t get the error in the first try and need to repeat the cycle. It happens almost every time in the second try. After getting the error, it will happen every time I repeat the cycle.
As I said before, it only happens in my system and I only have this issue with PA. Followed the same steps in the virtual machines, but I got nothing.
-
Here is the latest release:
http://www.powerarchiver.com/test/release15/powarc150106.exeemail us at support again to get debug exe which will tell us what is going on when error appears… thanks!
-
Runtime error persists with new version
Self-extraction zip explorer fixed–-Debug—
Replaced the PowerArc.exe with the debug version.
Every time I exit PA it ends with “runtime error 216” (ntdll.dll)
Replicating the original issue gives “runtime error 216” (ntdll.dll) instead of “runtime error 217” (kernel32.dll) -
send us a screenshot please… you dont get debugger? Are you sure you are using debug version? Thanks!
-
send us a screenshot please… you dont get debugger? Are you sure you are using debug version? Thanks!
The, on exit, runtime error 216 just happens since I replaced the original PA with the debug version (pa150105witheureka.7z). And yes, I don’t get the debugger log.
-
what happens when you click on click here in upper window?
-
what happens when you click on click here in upper window?
I get the following window (similar to the non debug version, when I get the runtime error 217):
