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.
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
X64 support
-
Will PA support windows xp 64bit?
some other compression utility that I wont name here dont as the shell extention doesnt work right now
-
-
thats not a good thread to look at and I dont want to bring it up by responding there. Basically we have to re-write shell extensions in 64bit and then they should work. When we get time, we will check it out and see if it works.
Problem is that Win64 does not support 32bit shell extensions, and hence they wont/dont work…
-
ok thanks for the quick answer
-
Basically we have to re-write shell extensions in 64bit and then they should work. When we get time, we will check it out and see if it works.
That means, x64 support is far away? You gave the same answer for sfx support, but in the last four years you didn’t find time to update the sfx support. It seems that the only way to get x64 support is to use another archiver. :(
-
That means, x64 support is far away? You gave the same answer for sfx support, but in the last four years you didn’t find time to update the sfx support. It seems that the only way to get x64 support is to use another archiver. :(
Interesting, we certainly did update PowerArchiver over the years, did we not? :-). Of course, feel free to use any software you wish to use. As I said, we will check it out once we have time (since 9.5 is priority), if we can get it to work, great.
-
Yes, of course you did. But some users are still waiting for self-decrypting .pae files. ;)
But I think it’s not only done with rewriting the shell extension. Even a 64bit shell extension has to check if the right-clicked file is an archive. So you have also to move your archiver libraries to 64bit too.
-
Could you make 1 shell extension work in x64. It only has to work in the alphas. It doesn’t have to be in the final. I would like The extract to folder (name)
Is very annoying to have to work from with in main window to extract….
Thanx…
Guido
-
Hi!
I hope 64 bit support will be available for PowerArchiver too soon.
I understand that it involves some work to convert it, but I think you guys will make more and more people very happy with this. A very good way to go ahead of the competition!
Besides converting the whole application to something 64 bit, I think it is possible to use the simple context menu options really simple with the use of command line switches. I know some people fixed it for WinRAR as you can see in this forum: http://www.neowin.net/forum/index.php?showtopic=311399&pid=585832076&st=0.
Could you please instruct us Windows XP x64 people how to do such thing for PowerArchiver?
Thanks in advance!
-
The shell extension / context menu items of PowerArchiver are accessible from the 32-bits version of Windows Explorer by using the workaround described on http://www.extended64.com/blogs/bhpaddock/archive/2005/05/22/539.aspx.
I do not know the exact implications from this, but it is usefull for tools like PowerArchiver, TortoiseCVS and others.
-
The shell extension / context menu items of PowerArchiver are accessible from the 32-bits version of Windows Explorer by using the workaround described on http://www.extended64.com/blogs/bhpaddock/archive/2005/05/22/539.aspx.
I do not know the exact implications from this, but it is usefull for tools like PowerArchiver, TortoiseCVS and others.
Hopefully we will check it out soon enough so we can see if it is possible for it to work properly under 64bit…
thanks for the tip.
-
Any plans already to release a version with support for Windows XP 64-bit?
There is a lot of talking about it on PlanetAMD. I am sure you win some new customers if
64 bit support is implemented. WinZip doesn’t got it yet (but something called Squeez does). I only don’t want all that other stuff, I want Powerarchiver! -
Any plans already to release a version with support for Windows XP 64-bit?
There is a lot of talking about it on PlanetAMD. I am sure you win some new customers if
64 bit support is implemented. WinZip doesn’t got it yet (but something called Squeez does). I only don’t want all that other stuff, I want Powerarchiver!we are working on it right now…
-
:D :D :D :D :D :D :D :D :D
-
great to hear ;)
-
we are working on it right now…
Great! I hope PA could be the first choice of Win64 users. ;)
-
we are working on it right now…
Good to hear because some competitors are starting to offer x64 Shell Ext. support.
By the way, as I’m new to the forum I must say this: PA 9.x rocks … ;)
-
Any flash news on progress?
-
We are working on it - I hope this month we shall have patch for Win XP x64.
-
We are working on it - I hope this month we shall have patch for Win XP x64.
Any chance for x64 support in PA 9.5?
-
It should be available for testing quite soon.
-
It should be available for testing quite soon.
You need a smilie for “Thumbs up” in the forum. :)
-
p.s. just an reminder - x64 shell extensions were added to Beta 7 of PA 2006…
-
Doesn’t work on my pc with B7
Guido
-
did you restart your computer after installation?
-
ofcourse ;)
guido
-
ofcourse ;)
guido
well give us more info, we have tried with 4-5 different computers and it all went well….
-
what do you want?
I have a english Windows…
I also installed winrar. Maybe that’s the problem.
Guido
-
You have english Windows X64, build … And you are running AMD…?
etc, etc… And after installation, you do not get any shell extensions for PA? (quick check if they are on in the config?).thanks,
-
You have english Windows X64, build … And you are running AMD…?
- AMD 3500+
etc, etc… And after installation, you do not get any shell extensions for PA? (quick check if they are on in the config?).
- I’m not getting any shell ext at all. I tried turning them on and off. Also in combination with the shell ext from winrar.
Do you want me to check some reg keys ?
Guido
edit: typo
-
ok, so you WinXp x64 users - make sure PA installs under Program Files and not Program Files (x86). Windows will not let shell extensions to run from x86 folder!
This is only valid for people who had already installed PA on the computer so PA’s installation will look at last installation folder. New installations will go into “64bit” Program files by default.
thanks!