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.
FTP – sorry not closed
-
I spoke prematurely.
The FTP works with FTP + SSL.
But there is a huge problem.
Once I use it in a pbs job, it resets the profile to SFTP – which does NOT work.
As long as I don’t try to use a pbs, all is fine. But once I do, it’s all over.
You might want to fix this before the new patchbeam.
ADDITION: I thought maybe complete redoing the pbs files from scatch would help. Nope. FTP + SSL will not stick in a pbs file. It defaults to SFTP which does not work.
-
Reproduced this, logging it in. Thanks!
-
Thanks.
-
I tried running a PBS with encryption.
The progress bar went to 100%, but never said it was done – not even after 2 minutes after it reach the end of the bar.
What would cause this?
Ideas?
-
send the pbs to support and they will try to reproduce the issue, i have no idea… btw - does the new version work fine with FTP in backup?
-
After waiting for 2 minutes I finally stopped it — and it had worked (although the update is much slower (by at least a factor of 2) than the same transfer with FileZilla using the same encryption.
So I will try it a couple more times and if isn’t fixed, I can just use FZ.
Having the FTP is nice, but its not the main thing I like about PA. Your program already does so much. I cannot expect it to do everything well.
Thanks for trying.
-
oh you meant the sftp transfer was slow? i didnt quite understand… it should be exactly the same speed, maybe there was something else going on? ssl overhead is pretty small.
-
I realize I was unclear. It created the archive just fine.
And it uploaded the file (albeit, very slowly). But THAT is where the progress bar showed that the upload was 100% complete, but I never saw the “it’s finished” (sorry, don’t remember the wording) dialogue box. Finally I manually stopped it (2+ minutes later). Although there was the no notice that the PBS has finished uploading, the upload was successful.
-
After two reboots, everything went smoothly.
-
we have tested it ourselves in the meantime, same speed between the two… it was probably something specific with connection at that particular time.
