For example:
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.
Hello!
Is there currently no portable version of PA2023 available?
(When) do you plan to release one?
Thanks!
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
powerarc_2023-09-18_17-00-19.png
powerarc_2023-09-18_17-01-05.png
PA 22.00.09
344c6c52-f03f-407b-ad76-8130b31936bb-image.png
PA 22.00.09 shows a nag screen, when I try to open some setting windows. I have already PA 2023 Toolbox and PA shows, that it’s licensed in the info dialog.
a860bd81-3e71-4ce0-9988-74cd4189d43e-image.png
0836bc83-8046-4a91-bc7b-68bd231100a3-image.png
PA 22.00.09
Some labels in the help toolbar are not translated:
b3c1f5c4-b73d-49d8-9ed0-56294840838c-image.png
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.
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.
Compress from shell got killed by update after closing another GUI instance
-
:mad:
I just had a 80% complete job that had been running for >24 hours killed by the stupid patchbeam updater, after closing another instance of the PowerArchiver GUI.
Needless to say, I am 100% seeing red!
The updater should NOT kill ANY running jobs!!
-
Hello,
Sorry you had an unwanted experience.
There are a few prompts asking you to use patchbeam before upgrade starts.
Can you provide some more detail as to what exactly happened? Patchbeam closed PowerArchiver while it was working?Thanks!
-
Sorry, I see now in my hasted anger I forgot to post the details.
In explorer, I selected a folder and from the shell menu chose “Compress to folder.7z”. This then opened a window with the compression progress.
Completely unrelated to that, about a day later, I opened a PA GUI window, NO archives, I just wanted to check some settings (specifically, if there are any ‘multi-thread’ options). After I closed this GUI, my other dialog stated ‘cancelling’, closed after a while and then PatchBeam opened and updated my PA. -
In the case of PA 2015, full Patchbeam has not yet activated. So it just downloads the installer right now. Installer when it starts actually doing the update, will want to replace powerarc.exe, in order to update it.
Are you sure that you did not have to manually advanced through installer though? I think first step should be manual.
-
Maybe I am so used to PatchBeam doing the updates that I mistyped what happened. I remember that the installer was run, yes, but AFTER my ‘shell compress job’ got killed. That is the important bit.
So, the steps as I recall:
- shell compress was running
- GUI opened and closed
- shell compress got nuked
- update was downloaded/installed
-
Maybe I am so used to PatchBeam doing the updates that I mistyped what happened. I remember that the installer was run, yes, but AFTER my ‘shell compress job’ got killed. That is the important bit.
So, the steps as I recall:
- shell compress was running
- GUI opened and closed
- shell compress got nuked
- update was downloaded/installed
It is installer that kills instance of anything that it has to replace, so it has to be done during install process - Patchbeam or PA do not have ability to do this.
Now, we run installer in reduced mode when you are updating from Patchbeam. So I will check if we show enough dialogues during update. If I remember correctly, we do, but I will check to make sure. Most people usually just click through it super fast though.
But in general, for the future, it would be safe to assume that update will close all instances of anything that it is updating. This is always pa.exe at least. There is no really a way around it except for not updating when PA is running of course.
thanks!
-
I’m assuming POWERARC.EXE will only ever be loaded/running if either the GUI is open or it’s actively doing an archive operation. Are there any other cases where the EXE would be loaded?
In the first case, probably not many people would care if the EXE got killed to update the app…
In the second case (the OP’s case) could you not have some sort of callback to some module in the PA stack that the installer could use to see if there are active operations running - and if so, abort the update?