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.
'New' Zip File
-
Can’t for the life of me recall if this has been dealt with in the past but I’ll pose the question…
is it possible to stop PA adding entries to the ‘New’ menu as seen in screenshot 1 ?I do remove them manually by deleting the ‘shellnew’ entries in the registry (see below) but as soon as I open PA again it adds them again.
please excuse my ignorance if this is an old issue that I seem to have missed. :)
-
I had no idea ZIPX was even there :-)
-
I had no idea ZIPX was even there :-)
I’m guessing then that this will be maybe looked into at some later date perhaps ? :D
-
at very least, we will make association during the setup, not startup, so if you decide to delete it, it will not come back.
-
I surely will be deleting it…I’m forever removing items from the ‘New’ menu…
many thanks…:)
strange but it seems more persistent in this latest build…I’ve removed it before in earlier builds
but don’t recall it continually adding itself once I’d removed it…:confused: -
found a temporary fix for this issue…
I just rename the ShellNew key to ShellNew- and they no longer appear in the ‘NEW’ Desktop context menu…:)Hmmm…forget that solution…PA adds NEW keys in addition to the ones I’ve renamed so I’m right back to square one…:rolleyes:
PA is just way to smart for my liking…:D
‘ShellMenuNew v1.01’ seems to have fixed the issue for now…:)
-
delete now and patchbeam the latest update and let us know how it works :-)
-
still the same I’m afraid…:(
but thank you for your efforts…:) -
hm, so I deleted those shellnew entries, and started PA, exited PA, still not there?
-
ah understood…I’ve now removed reg entries and they haven’t returned…stupid me thought some other means had been incorporated into PA as opposed to me removing them manually.
thanks team…:)
-
we didnt want to auto remove for everyone, as someone might be using it and then they will complain, etc, etc :-).
thanks!