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.
Problem opening file inside a compressed file
I wanna first thank the programers for their works to build the powerarchiver program that is very useful.
when I want to open a file that is in a compressed file with powerarchiver , nothing append…
(open the file by double clicking in the file or with right clicking and open menu)
It was working in the 2010 version.
I have tried to uninstall et reinstall powerarchiver but it doesn’t work.
I have Windows 7 64bits
Nice to help me.
Welcome to the forum NCIBX.
Can you give more details as this will help the devs when they read your post.
What type of archive? zip, rar, etc.
Is this file a specific file type or do you get the same behaviour with all file types?
Or are you trying to open an archive within an archive?
If it’s the latter then there have already been reports about this issue here.
I have made some test and the problem is only with the RAR archives.
And for the files inside the RAR archive, when I want to open a PDF file it work but it doesn’t work with EXE, MSI, TXT, pictures files.
Other detail: when I want to open a file, the red bar on the right bottom of the windows change to green but at the end nothing happend
are you sure rar is not broken maybe? did you try extracting and then opening those files?
I have made some new tests and I have see something: the problem occur only with RAR archives that have in their propriety (See in File Menu of Powerarchiver ):
- Version to extract: 2.0
- Version build by: 2.0
I have tested other RAR files with 2.9 version and the opening of files work perfectly
With the 2.0 RAR version where is the problem, when I want to extract all the archives, there are no problem. It’s only when I want to open the files directly by Powerarchiver without extracting all the archive.
Correction with my previous message, the PDF file thats work was a 2.9 RAR version, maybe it will not work in a 2.0 RAR version (I have no PDF in a 2.0 RAR version to test and check it)
The issue happens when wiles are compressed within a folder. So when you open a RAR file where the compressed files are within a folder structure (inside a folder), they do not open when double clicked.
If files are compressed with no path (no folder structure/not inside a folder) they open fine.
The issue has been logged in.
this issue has been fixed in later PA versions… if you still follow PA, please let us know if it works fine.