I’m looking forward to deploying PowerArchiver 2023 to my users. Can you tell us when the MSI will be available for download and distribution?
Thanks.
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
powerarc_2023-09-18_17-00-19.png
powerarc_2023-09-18_17-01-05.png
Hi there,
there were some security issues fixed in 7zip:
https://www.zerodayinitiative.com/advisories/ZDI-23-1165/
https://www.zerodayinitiative.com/advisories/ZDI-23-1164/
As it seems, that PowerArchiver and PACL use the 7zip libraries, could you please update them to the latest version?
Hi,
From where I get PAVD2023.EXE? PowerArchiver 2023 tries to open it.
But it seems, it tries to download PAVD2021.EXE.
Thanks
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.
Discovered:
a) PA always issues a UAC prompt to do this!
b) PA always says there are many errors in PA files.
PA fails to run after install on non-admin accounts
-
I use PA at my university. Students have a limited user account.
I always install PA to the desktop, since I have write access there.When I install PA 9.6 (beta 2 or 3), I get file error messages on WBHELP2.DLL and WBOCX.OCX, access is denied, so cannot write to windows directory.
Now when I try running PA, PA crashes with “PowerArchiver 2006 has encountered…… We are sorry for the inconvenience.”
I can bet that the WindowBlinds skin engine is causing this! Even if I remove all PA entries from the registry (the admin missed something…), or delete the Skins folder, it still happens.
No other version of PA does this, but 9.6.I dunno how this can be solved; maybe you shouldn’t initialize the skin engine if there is no skin selected, which is the default.
PS: why not install the WB files in the PA dir? PA is the only app that needs to use those files!
-
we cant add it to any other folder. Thats the way it works. So you have to have an admin account to install it.
-
With 9.6 final, PA will skip around missing dll’s and continue working…
thanks
-
Thanks!
Until the problem is fully resolved, I’ll have to use 9.51 on campus and 9.6 at home… :-)
-
OK, the problem is solved - PA runs!!!
If I try to select a skin, nothing happens!!
Great work!!! ;-)
