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.
Password for backups changing
-
I did a search and only found a few deadended threads on the subject, so I apologize if this has already been discussed.
The problem I am having is the password that I entered using AES-256bit on a backup script is getting changed to a bunch of random symbols and the backup .zip file cannot be opened using the original password entered.
Here is a screenshot:
-
Hi,
try re-creating the script and send us pbs that you have to support email, replying to the ticket you already opened.
I tried it with simple pbs and it seems fine, it might be more complicated than that.
thanks!
-
Thanks for the reply. I will recreate the script and send it to you first thing tomorrow morning when I get in.
-
Sorry for digging up an old post but we are encountering the same problem again. I created a test backup job and ran it, downloaded the .zip it created from the FTP and was able to extract the file using the password I specified when creating the Job “password”. After I ran the job a second time and downloaded the newly created .zip and tried to open it, it told the password was incorrect. Upon the opening the job I noticed that the password “password” had changed to “adyÁq‡ü–c’ ‘ý™º²¼Œ)é8ô,_Ø´Í©44ý%zªó}gfÔ/½’r)½J0° „)ѽ[~l §censored{{>°5#ý¥œ›vQà ”òÈw_ù+1+L!-ÞÓwX¦ðCé«”.
Please advise.
-
send us that pbs please (with original settings) so we can try and reproduce it… what version of PA are you using now?
-
you are also not editing or running this pbs on other computer?
-
Currently using Version 11.71.04 (12/2010). I’ll email you my test.pbs now.
Thanks
-
you are also not editing or running this pbs on other computer?
No. The problem started on another computer so I tried to duplicate it on another one with a fresh .pbs file and it did the exact same thing.
-
thanks a lot… that password is AES encrypted, so thats why it appears like that (so nobody can simply take your pbs and easily find out what the password is)… but it seems it is either not saved correctly or not read correctly, which is why you get garbage… we will update the thread once we have more info!
