Just tried using the Modern (Windows 10) Icon set and seeing a few missing icons in both PowerArchiver Burner and PowerArchiver Encryption screens . They are all there in the Minimalistik icon set and the only difference I can see is the former is blue and the latter grey. In version 22.00.9
there were some security issues fixed in 7zip:
As it seems, that PowerArchiver and PACL use the 7zip libraries, could you please update them to the latest version?
I noticed that the version of ZPAQ used is older than the latest released 7.15 https://mattmahoney.net/dc/zpaq.html also there seems to be a newer fork that adds several features https://github.com/fcorbelli/zpaqfranz
It would be useful to implement this latest version (it also maintains the same syntax and behavior as the latest official release if used the -715 flag) and add when opening a zpaq file a choice of the version of the files to show (e.g. as dummy folders represented the various versions present). Since any previous changes are stored with this format, it is possible to extract a snapshot of a certain date/version.
If I open a password-protected zipper file (created with WinRAR but I think that’s irrelevant), open it with PowerArchiver and run “Remove Encryption” on the same file, then reopen it and add a password with “Encrypt Archive,” the resulting archive will be protected with the old ZipCrypto algorithm and not AES as indicated.
(this can be verified, for example, by trying to open the archive files with Windows Explorer, which does not support the AES algorithm)
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.
a) PA always issues a UAC prompt to do this!
b) PA always says there are many errors in PA files.
[solved] Right-click to extract error
If I right click to extract a RAR file, I get the dialogue box as in sshot-11, then when that is cleared, I see what is in sshot-12.
ZIP files produce the same error.
[solved] A reinstall over the top of the current install fixed it. Posted as it may help somebody.
shell extensions did not get replaced properly.
I did have to uninstall and reinstall recently (I can see that during the install process, some uninstalling takes place) so the RC4 that was ‘faulty’ was installed after a user-generated uninstall rather than an in place upgrade.
Regards and belated birthday wishes
during installation “upgrade”, same type of uninstall is always done as well by Windows Installer.
It is just that due to some “random” Windows issues sometimes things dont get registered properly.
I can tell you that it should not happen on perfectly fine and perfectly new windows installation, but who has that, right? :-).