-
-
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).
-
In the latest version of PA, on W11 (latest build/SP) when you try to use the first level context menu - NOTHING HAPPENS (particularly when you do this from Downloads or Documents folders) - however I noticed that it DOES WORK when you use the context menu from the Desktop. Going to the second level context menu does work however.
-
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.
-
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
Binary-files not added to archive
-
Hi all,
I wonder if this is only me or I am doing something wrong…
Since lately, I cannot add binary-files (exe and dll files, maybe others too) to a ZIP-archive using PowerArchiver. I’m using version 2015 but I have had this issues also with it’s predecessor PowerArchiver 2013. It doesn’t work via explorer’s context-menu nor does it work if I open an archive in PA and drag-and-drop such a file into an existing archive…
Using the Windows built-in functionality for creating ZIPs works flawlessly. Also using 7-ZIP I see no problems.
I’m running PA under a Windows 8.1.
Anybodey has any clue? Would be highly appreciated.
EDIT: is there any way to create a logfile or any debugging info??? At the moment, PA is completely useless to me… :(
Thanks in advance
Frank -
No one…?:mad:
-
I just created a zipx file of a single .exe from the shell. Went without a hitch.
-
weird, never saw that before… you are doing it via shell?
What AV do you have? I wonder if it is some kind of interference.sorry, did not notice the thread… always good to email support at conexware dot com to get to ticket based system as well.
-
weird, never saw that before… you are doing it via shell?
It behaves like this via explorer’s shell extension, but also if using PAs normal UI…
What AV do you have? I wonder if it is some kind of interference.
No special one - I’m using the Windows 8.1 builtin Windows Defender.
sorry, did not notice the thread… always good to email support at conexware dot com to get to ticket based system as well.
OK - just thought that one of the users here perhaps had a similar problem…
So again: is there any way of creating some kind of debug-info (logfile, eventlog or something like this)?
Thanks, Frank
-
Just attempted to create a new ZIPs with EXE’s and DLL’s inside, worked fine.
Also attempted to add EXE’s and DLL’s to existing ZIPs and that worked fine as well.What exactly happens when you attempt the same? What kind of an error do you get?
You can send us your zipped reg settings(save settings to file below config button) to support at conexware dot com and we can try with your settings. -
One more question - did you try using cab format or tar for instance and does the same thing happen?
-
What exactly happens when you attempt the same? What kind of an error do you get?
Nothing happens - this is weird… I get a “pling” system-sound and the file(s) are not added to the archive. No error or message at all is shown…
@Mili:You can send us your zipped reg settings(save settings to file below config button) to support at conexware dot com and we can try with your settings.
OK, will do that… thanks…
Frank
-
One more question - did you try using cab format or tar for instance and does the same thing happen?
Yes, tried that with same results (not working)…
Thanks, Frank
-
Hi franky13,
thanks for sending over the settings. tried with them and still worked fine.
As I replied in the support ticket, if possible, send over the files you are using and we will try with those exact files to attempt to reproduce.thanks!