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
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).
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.
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.
Could not upgrade to PA 9.6 beta 1 (9.6.0.8)
-
I upgraded from my previously 9.51
rebooted, and that’s what happens when I call the program (I’m Italian, so errors are in my language):and then
I’m now going to uninstall it then reinstall the last beta, to see what happens.
I’m writing here because it’s really the 1st time I’ve experienced a problem when upgrading PA :(
-
I saw the second error (interface not registered) after updating a PA 9.51 to PA 9.60b1 - but I had not rebooted.
After rebooting, PA 9.60b1 is working fine.
-
I saw the second error (interface not registered) after updating a PA 9.51 to PA 9.60b1 - but I had not rebooted.
After rebooting, PA 9.60b1 is working fine.
That seems to be a problem with the dll which implements the Explorer (shell) options - it is replaced and a reboot is needed.
Not sure about “manuangi’s” first problem. Was the previous version (9.51) using a different skin (non-default) perhaps?
As a “general rule” I would not advise << upgrading >> to a ‘beta’ version of any software. I always do a clean install (uninstall previous/reboot/install ‘beta’).
Still feedback that there was a problem is useful.
-
definetly an old skin. We have to be able to handle that better.
thanks!
-
I saw the second error (interface not registered) after updating a PA 9.51 to PA 9.60b1 - but I had not rebooted.
After rebooting, PA 9.60b1 is working fine.
what OS are you using?
-
definetly an old skin. We have to be able to handle that better.
thanks!
yea, I was using the “bunnies” skin that I love so much :)
so, spwolf, what’s your advice about how to proceed?
thank you
-
try deleting the skin that you were using? If not, you can uninstall it and install it again, which will delete the registry keys…
thanks!
p.s. what OS?
-
try deleting the skin that you were using? If not, you can uninstall it and install it again, which will delete the registry keys…
thanks!
ok…but I really loved the bunny-skin :(
p.s. what OS?
WinXP SP1
-
I think restart is the most important step here, so please restart your computer when installation tells you so!
thanks,
-
I always did, if you read my previous posts.
anyway, uninstalling/reinstalling PA did the trick
can I apply my bunny skin again, or you think there could be problems?
-
skinning engine is completly new, only toolbars will work (complete skin wont)…
-
what OS are you using?
WinXP SP2.
Note that I did not consider the error message I saw to be a bug - the update told me that I had to reboot, but I generally ignore those messages unless I run into problems because reboots are often not really necessary for many products - the install process is just being overly conservative.
However, if you can workaround the need to reboot, obviously that would be a plus!
-
WinXP SP2.
Note that I did not consider the error message I saw to be a bug - the update told me that I had to reboot, but I generally ignore those messages unless I run into problems because reboots are often not really necessary for many products - the install process is just being overly conservative.
However, if you can workaround the need to reboot, obviously that would be a plus!
Did you install PA in same folder as before or in new folder? Did you keep old version installed?
I noticed one case where installer would not register skin dlls until reboot, but in that case PA would have tell you that you cant install until reboot and you would have to delete your registry key for pending renames, which is probably not what you did?
thanks,
-
Did you install PA in same folder as before or in new folder? Did you keep old version installed?
I noticed one case where installer would not register skin dlls until reboot, but in that case PA would have tell you that you cant install until reboot and you would have to delete your registry key for pending renames, which is probably not what you did?
thanks,
I just installed the beta over the existing install (I’m wreckless sometimes). No problems - it told me to reboot, but I didn’t (wreckless…) and it gave the interface registration error when I tried to start PA. After a reboot I tried again, and everything is working fine.
-
… can I apply my bunny skin again, or you think there could be problems?
Not sure what “bunny skin” is.
If you mean “Rabbit XP” then that is a toolbar and not a skin, so…
@spwolf:skinning engine is completly new, only toolbars will work (complete skin wont)…
Maybe? {Can’t try it myself at moment sorry… }
-
Not sure what “bunny skin” is.
If you mean “Rabbit XP” then that is a toolbar and not a skin, so…skinning engine is completly new, only toolbars will work (complete skin wont)…
Nope.
Doesn’t work - or at least I cannot see how to apply the “old” toolbar button “skins”. :confused: -
Config> Skins & Toolbar :-).
-
Config> Skins & Toolbar :-).
:o I was trying via
Options - Skins …
Skins(right click) …
Select Buttons …Missed the Config settings :o
OK it does work.