Hi everyone, some good news about PowerArchiver… I’ve managed to get in touch with the original developer of PowerArchiver, Ivan Petrovic, and he has confirmed that the product is not dead or abandoned, in fact it is still very much alive! There has been a hiatus over the past months for various reasons, but that we should expect to see stuff coming through in the coming months (hopefully the next 2 months).
The Windows 11 context menu for PowerArchiver on normal files (to be compressed, etc.) is now showing multiple tiers with two identical menus. See attached captures of the issue:
Screenshot 2025-01-08 082909.png
Screenshot 2025-01-08 082935.png
Screenshot 2025-01-08 082953.png
Edition Windows 11 Pro
Version 24H2
OS build 26100.2605
Hello!
I’ve just created SFX-Archives both from ZIP and 7z-Archives and none has an Icon as it seems.
I use the new version 22.00.11.
Zwischenablage_10-22-2024_01.jpg
Basically I used powerarchiver context menus to zip up a folder then i used windows 11 own built in zip extractor via the context menu to extract all and this is where it throw up a fault. , I’m using windows 11 .
The file that was a problem in the zip that windows 11 could not extract was iva “babe” cotton.jpg
I know it has non standard quotes in it.
However I had winrar on the computer and tried the exact same method with their context menu compress to zip and then I extracted the file with windows own extract all context menu and it had no problems. This indicates that powerarchiver is doing something different with iva “babe” cotton.jpg compressing to zip.
Then I changed iva “babe” cotton.jpg to iva babe cotton.jpg and compressed it with powerarchiver and then tried it with windows 11 extract all and had no problems. It looks like powerarchiver is doing something to that one file that has quotes in it.
Please note that powerarchiver extracted both zip files with no problems, only windows built in zip extraction had the fault. Reason I’m letting people know in case they send zip files with special characters in files names to people who do not have powerarchiver.
When will a fix be implemented?
On installing the program I am getting the error message:
"Unable to execute file c:\Program Files\PowerArchiver\pashutil.exe
CreateProcess failed: code 2
The system cannot find the file specified"
This can’t be right!
I am using the latest official build of Windows 11
Buttons are not properly aligned on About screen.
about window.png
Buttons not aligned on configuration window.
configbuttons.png
New version:
PowerArchiver 2023 - 22.00.10:
Download:
https://u.powerarchiver.com/pa2023/powarc220010.exe
New build for some bug fixes and issues - full list to come with new update. Please test and see if you have any issues.
Thanks everyone for your assistance!
New version:
PowerArchiver 2023 - 22.00.11:
Download:
https://u.powerarchiver.com/pa2023/powarc220011.exe
New build for some bug fixes and issues - full list to come with new update. Please test and see if you have any issues.
Thanks everyone for your assistance!
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
I had a large .tar file (a backed up WSL) and I want to delete a few directories and their contents from it using PA2023.
PA just destroys the whole archive as soon as I try to delete a directory, leaving it in a state where PA2023 won’t even open it any more.
I tried several times and also tried compressing it to .tar.xz instead - same result.
This should either actually work, or it should say operation not supported and do nothing.
Hello!
The regular version of PA 2023 is out for over 6 months now, but there is still no sign of the portable release.
(When) will there be one?
Thanks!
Hello!
Is there currently no portable version of PA2023 available?
(When) do you plan to release one?
Thanks!
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?
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.
PA2009 Backup Function Date Selection Error
-
I’m pretty sure this issue came up and was resolved a couple of years ago, but . . . .
Last night I ran my daily backup routines after just having upgraded to PA2009 and after checking my backup files I noticed that they got much bigger than previously. Obviously more files were now being included. I checked the backup routines (the .pbs files) and confirmed that my selection criteria of “newer than 30 days” had not changed during the upgrade process. However, checking the contents of my backup files revealed that files that had been modified MORE than 30 days ago were also included. However, not ALL files were included, so it was not effectively a full backup, but more like “newer than 70 days”.
I’m not sure if there is a connection, but I use the Canadian date format of day/month/year, but this is a Windows system setting and is application independend.
-
are you overwriting the backup file? or updating it? That might be the issue - PA will not delete old archive anymore, it will update it with new files.
-
After I read another thread (“PA Backup File” by Martin), that thought occurred to me as well, but looking at the dates of the files contained in the bakup file, that would not appear to be the case.
The backup job ran on Oct.2,2008 and was configured to select files “newer than” “30” days. Files found in the resulting ZIP file range in “modified” dates from Oct.2 to July 22. I think that is 71 days (perhaps that is significant somehow).
-
ah, newer… modified or created? there is an world of difference just there…
-
I’m not quite sure what you mean with your response spwolf.
Just to clarify, I have not changed my PBS files, just updated (uninstalled PA2007 and installed PA2009) the program. The “newer than” option and my “30” days setting are still the same as in PA2007 (1022). The resulting ZIP file shows the “modified” date column, just as before. So the “newer than” option has always applied to the modified date, not the created date.
Are you perhaps saying that in PA2009 the definition of “newer than” has changed?
-
Any more thoughts on this spwolf? Is this being investigated?
-
@Joe:
Any more thoughts on this spwolf? Is this being investigated?
fixed, waiting for release… :-)
-
please check with 11.01… thank you!
-
Well, the latest PA2009 updates have fixed the original bug, but today I’ve discovered another problem with the “newer than xx days” option.
It would seem that there is a fundamental error in the way the actual date is calculated. For instance, if I specify “newer than 30 days”, on the 30th day of the month the backup job will just sit there without doing anything. I suspect if I specify “newer than 1 day” the same problem will occur on every 1st day of each month.
I’ve changed my monthly backup jobs to a “newer than 32 days” selection criteria, to circumvent this bug, but I need a solution for my weekly jobs (where I specify “newer than 7 days”).
-
@Joe:
Well, the latest PA2009 updates have fixed the original bug, but today I’ve discovered another problem with the “newer than xx days” option.
It would seem that there is a fundamental error in the way the actual date is calculated. For instance, if I specify “newer than 30 days”, on the 30th day of the month the backup job will just sit there without doing anything. I suspect if I specify “newer than 1 day” the same problem will occur on every 1st day of each month.
I’ve changed my monthly backup jobs to a “newer than 32 days” selection criteria, to circumvent this bug, but I need a solution for my weekly jobs (where I specify “newer than 7 days”).
so backup will not run on certain date = if that date= amount of days you entered on newer than?
-
It sure looks that way…the pattern is obvious…(newer than) 30 (days) minus (Oct.) 30 (th) = 0, hence PA2009 launches, but just sits there and processes 0 (nothing).
I just tested another scenario and changed my system date to the 7th then ran a weekly backup (with “newer than 7 days”) and the same situation occurred again: PA2009 launches, but does nothing.
-
who da best support in the history of man kind?
http://www.powerarchiver.com/test/release10/powarc1102.exe:-)
-
p.s. let us know if it works properly… thanks