-
-
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
UNSOLVED Making .EXE from encrypted .zipx creates a buggy file that doesn't work
-
I’m reporting a bug in the SFX module that creates an .exe file that doesn’t extract and shows unexpected behavior.
Steps to reproduce
- Compress files to optimized zipx format with ultra compression and AES 256-bit encryption;
- Put a password. Here I put: password ;
- Select the option Make .EXE file from Actions menu;
- Create the SFX with Default “UnZip To” folder similiar to the screenshot and the checkbox Hide file list CHECKED;
- Try to extract the files;
- It’s a weird and unpractical thing that it will ask for a password for each file instead of using the same pass for all of them. It should be and exception to ask for an other password when some file has a different one.
So, type in the password. My pw is password as I stated before;
- Strangely, it will keep asking the password for the same file over and over. You will have to skip or cancel. Skipping it will eventually lead to the same error below, so let’s cancel it;
- When you cancel, it will give a Incorrect Password error;
- Remember that we CHECKED Hide file list when we created the SFX file? Now, as well as the dialog being completely bugged, 2 of the 3 files now are apearing in this list that never should have appeared.
I will leave here links to the original .zipx file and the .exe I created.
Remember that the password is just password.PowerArchiver version used:
Also, there’s one more bug I found out. If you add a file to that same archive that has some russian characters in the name, the SFX file list will show weird characters instead of the correct file name. Look:
- I used a file named рисунок-арт-красивые-картинки-удалённое-1710969.jpeg ;
- Created a new SFX file, this time with Hide file list UNCHECKED on purpose. This is how the russian file name was presented:
Based on what I saw, it seems for me that the SFX creator module is in need of some work, looks kinda abandoned and outdated. The question mark button on the title bar ( ? ) also didn’t do anything for me, the cursor changed for a question mark but it didn’t work for anything.
-
@gui-lherme Hello, indeed, make sfx uses old code… Please use SFX Wizard to create SFX Archives.
It will use 7zip format for better compression.
-
@gui-lherme And thanks for nice big report. For make sfx in zip, we use tiny assambler code to minimize the size of sfx. Adding all of the zipx format support would make it as big as 7zip sfx. So it is much better to use 7zip sfx, since it will also lower the size of archive.
For near future, we are looking into supporting PA SFX, which gives more options, is more secure.
-
My suggestion to completely rework the SFX module. Take as an example the WinRAR’s SFX generator module; it’s pretty decent and very customizable. I think that PowerArchiver SFX is currently very poor and deserves a lot of work.
-
@gui-lherme said in Making .EXE from encrypted .zipx creates a buggy file that doesn't work:
My suggestion to completely rework the SFX module. Take as an example the WinRAR’s SFX generator module; it’s pretty decent and very customizable. I think that PowerArchiver SFX is currently very poor and deserves a lot of work.
Indeed, as mentioned, we will create .PA SFX module for next release. It will use PA or 7z format, not ZIP, since there are no benefits of using zip sfx over pa/7z.
Thanks.
-
@spwolf Ok, sounds interesting. Make sure to rework the SFX interface and make it very customizable, so we can distribute professional looking installers.
Thanks