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.
AVG reporting PABurnerTools is a virus?!
-
I just installed the 61 update and AVG Free is reporting PABurnTools is a virus? I read a comment on this before but now I’m getting this message as well. Can anybody clarify what’s going on? Did I just install an infected version on my PC?
-
I just installed the 61 update and AVG Free is reporting PABurnTools is a virus? I read a comment on this before but now I’m getting this message as well. Can anybody clarify what’s going on? Did I just install an infected version on my PC?
report false positive to AVG so they can fix their stuff.
-
Although by this point, i dont think they are able to fix their engine, since this has been happening for over a year now.
You can see report from other engines here:
http://www.virustotal.com/analisis/a14727238e1ea5558a5da93c2e7d79355e9988ac804cb17f73881672688d00de-1259084219 -
False positives are nastiness. One of my mates is testing out PA, and he says he got a probable false positive from Sunbelt’s sandbox saying that the PA 11.61 installer is infected with some Trojan.Win32.Generic!SB and “creates hidden EXE in System”. He also said that _PAUTIL.EXE is detected as Win32.Worm.H or something by McAfee. I guess when you get one false positive fixed, another is created. :(
-
False positives are nastiness. One of my mates is testing out PA, and he says he got a probable false positive from Sunbelt’s sandbox saying that the PA 11.61 installer is infected with some Trojan.Win32.Generic!SB and “creates hidden EXE in System”. He also said that _PAUTIL.EXE is detected as Win32.Worm.H or something by McAfee. I guess when you get one false positive fixed, another is created. :(
AV companies are so overwhelmed it seems…
-
p.s. there is an reason we sign all our executables with digital signatures. As long as signature is not broken (you can check in properties for that file), file has not been altered.
-
Sometimes I get the feeling AVs detect more false positives than real virii. :p I’m amazed they can’t get them fixed. Don’t they do anything when you report them they’re detecting PA falsely? If I was you I’d be really really annoyed because of that LOL
It’s really cool that you do digital sigs on all your exes. :)
-
Sometimes I get the feeling AVs detect more false positives than real virii. :p I’m amazed they can’t get them fixed. Don’t they do anything when you report them they’re detecting PA falsely? If I was you I’d be really really annoyed because of that LOL
It’s really cool that you do digital sigs on all your exes. :)
AVG fixes it for that version (after 1-2 weeks) and then when next version is out, it is flagged again ;-).
-
AVG fixes it for that version (after 1-2 weeks) and then when next version is out, it is flagged again ;-).
LOL that’s actually sad. They make a false positive, they fix it, and then they make it again in the next version! WTH man… I’m knocking on wood, but Security Essentials hasn’t given me false positives about PA or anything else yet.
-
… Security Essentials hasn’t given me false positives about PA or anything else yet.
Yeah - makes you wonder if MSE is actually doing anything :p
-
Why you continue to use that crappy AV software (AVG)? The problem is not within PA. AVG has a long history of false positives with many different software, last year it deleted Windows user32.dll :D
-
it is very tiring dance we have with some AV vendors. It makes me wonder how they run their business at all, with so many complaints thrown at them.
-
AVG has fixed their issue after notification by us. In the future, please notify them of false alarm as soon as possible.
