Win 11 64 bit
I have some archives which have been encrypted, using the encrypt option either in pbs or when interactively creating a zip. When I open these, and look at files, I am asked for passwords, which I know, and then can view items or decrypt the files in the archive (tools>decrypt files).
However, when I use the Actions>Remove Archive Encryption (whether using the same zip or asking to write another), the routine shows progress bar to the end, but then just hangs i.e. “OK” never activates. All process information shows this stalled/hanging.
What can I do to sort this out?
Download this ZIP file: http://dslstats.me.uk/files/dslstats32W-6.5.zip
Everything in the ZIP file is in a directory “dslstats32W-6.5”.
However when I extract using right click “Extract Here” the name of the directory created is “2W-6.5” !
I am running PA 22.00.09 on Windows 11. I have seen the same happen with some other kinds of archive too.
If I compress a folder to a .pa using right click, Compress to folder.pa and use the new Windows 11 menu then the Options, Configuration, Miscellaneous, Use normal relative path setting is always enabled.
But I like this option disabled so I have to use the old style menu in order to get PA to compress a folder in the way I wish.
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)
I have PB set to run when I start PA.
The last two days it has been very slow – multiple minutes to check for updates.
It could be a glitch in PB, or some a glitch on my computer. Not sure which.
thanks… i notice now something on my computer as well, so we will check it out.
i have no idea why is this happening… do you have BD installed? Maybe firewall?
It cant be anything but firewall since PB did not change in 6 months, and URL that it looks up loads super fast. But I disabled firewall on my computer and it still happens.
No BD. And the firewall I have has been there for a year, and nary a problem. I wonder if whatever in the latest beta of PA that “calls” PB is somehow clashing with it?
I think, though, this just started yesterday . . . so that doesn’t seem plausible.
yeah, nothing smart comes to mind and nothing changed in 6 months.
You might try a tracert to the IP address; you might find that it’s hanging somewhere along the way.
I am running the debug version of PB. Where do I find the logs to send you?
I found a 2011 discussion of the debug logs . . . but I cannot seem to find either one mentioned there. Also, not luck in the App folder, the program folder, or the program data files. Not sure where else to look.
its ok, we dont need debug logs since i have the same issue here.
That’s OK now. But for future reference . . .
it was flood attack on the patchbeam server, our admins “fixed” it, so it back to fast now.
Patchbeam Debug works only for the patchbeam update process, not check, as they are separate… it creates the file in C:\ once you enable it (and once update starts, again not check).