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.
PowerArchiver Toolbox 2016 [16.00.46] => right-click crashes of Explorer.exe etc.
-
Hi,
I bought the PowerArchiver Toolbox 2016 [16.00.46] via here: Click
When I right-click a file / folder / shortcut etc.pp. via Desktop, File-Explorer, Total Commander Ultima Prime etc.pp., then I get pretty much every 2nd time a “blabla had to be closed” - Error and the Explorer.exe restarts itself or closes the File-Explorer / Total Commander Ultima Prime if I’m lucky or completely takes off me the ability to right-click.
Faulting application name: explorer.exe, version: 10.0.11099.1000, time stamp: 0x56918bfb
Faulting module name: PASHLEXT64.DLL, version: 16.0.6.1, time stamp: 0x567a6bc2
Exception code: 0xc0000005
Fault offset: 0x00000000000306f1
Faulting process ID: 0x4ea4
Faulting application start time: 0x01d1526a75a9c9d4
Faulting application path: C:\WINDOWS\explorer.exe
Faulting module path: C:\Program Files (x86)\PowerArchiver\PASHLEXT64.DLL
Report ID: b1dfdd24-4949-4562-ac65-29f83f5b9cec
Faulting package full name:
Faulting package-relative application ID:-
System
-
Provider
[ Name] Application Error
- EventID 1000
[ Qualifiers] 0
Level 2
Task 100
Keywords 0x80000000000000
- TimeCreated
[ SystemTime] 2016-01-19T03:55:54.964936700Z
EventRecordID 2671
Channel Application
Computer MOTHER-PC
Security
- EventData
explorer.exe
10.0.11099.1000
56918bfb
PASHLEXT64.DLL
16.0.6.1
567a6bc2
c0000005
00000000000306f1
4ea4
01d1526a75a9c9d4
C:\WINDOWS\explorer.exe
C:\Program Files (x86)\PowerArchiver\PASHLEXT64.DLL
b1dfdd24-4949-4562-ac65-29f83f5b9cecDXDIAG: Click
I have no issues with other stuff.
:confused:
-
-
Please try build 53 - http://www.powerarchiver.com/forums/showpost.php?p=34606&postcount=62
-
Please try build 53 - http://www.powerarchiver.com/forums/showpost.php?p=34606&postcount=62
Thanks for your help, but it didn’t solve the issue unfortunately.
Here are the errors for the different tries:
Total Commander v8.52a / Total Commander Ultima Prime v7.0:
Faulting application name: TOTALCMD64.EXE, version: 8.5.2.1, time stamp: 0x00000000
Faulting module name: PASHLEXT64.DLL, version: 16.0.8.1, time stamp: 0x568fd3b0
Exception code: 0xc0000005
Fault offset: 0x00000000000306f1
Faulting process ID: 0x2be0
Faulting application start time: 0x01d152af85c0558f
Faulting application path: C:\Program Files (x86)\TC UP\TOTALCMD64.EXE
Faulting module path: C:\Program Files (x86)\PowerArchiver\PASHLEXT64.DLL
Report ID: 227c0e69-6aca-483a-9f5e-2ec2a3574484
Faulting package full name:
Faulting package-relative application ID:-
System
-
Provider
[ Name] Application Error
- EventID 1000
[ Qualifiers] 0
Level 2
Task 100
Keywords 0x80000000000000
- TimeCreated
[ SystemTime] 2016-01-19T12:39:27.093038300Z
EventRecordID 3024
Channel Application
Computer MOTHER-PC
Security
- EventData
TOTALCMD64.EXE
8.5.2.1
00000000
PASHLEXT64.DLL
16.0.8.1
568fd3b0
c0000005
00000000000306f1
2be0
01d152af85c0558f
C:\Program Files (x86)\TC UP\TOTALCMD64.EXE
C:\Program Files (x86)\PowerArchiver\PASHLEXT64.DLL
227c0e69-6aca-483a-9f5e-2ec2a3574484File Explorer:
Faulting application name: Explorer.EXE, version: 10.0.11099.1000, time stamp: 0x56918bfb
Faulting module name: PASHLEXT64.DLL, version: 16.0.8.1, time stamp: 0x568fd3b0
Exception code: 0xc0000005
Fault offset: 0x00000000000306f1
Faulting process ID: 0x249c
Faulting application start time: 0x01d152af7632a073
Faulting application path: C:\WINDOWS\Explorer.EXE
Faulting module path: C:\Program Files (x86)\PowerArchiver\PASHLEXT64.DLL
Report ID: 0c4ecb2e-7165-4091-85c1-e5c0c29a2e42
Faulting package full name:
Faulting package-relative application ID:-
System
-
Provider
[ Name] Application Error
- EventID 1000
[ Qualifiers] 0
Level 2
Task 100
Keywords 0x80000000000000
- TimeCreated
[ SystemTime] 2016-01-19T12:40:38.221749200Z
EventRecordID 3026
Channel Application
Computer MOTHER-PC
Security
- EventData
Explorer.EXE
10.0.11099.1000
56918bfb
PASHLEXT64.DLL
16.0.8.1
568fd3b0
c0000005
00000000000306f1
249c
01d152af7632a073
C:\WINDOWS\Explorer.EXE
C:\Program Files (x86)\PowerArchiver\PASHLEXT64.DLL
0c4ecb2e-7165-4091-85c1-e5c0c29a2e42Desktop Shortcut:
Faulting application name: SystemSettingsBroker.exe, version: 10.0.11099.1000, time stamp: 0x56918de6
Faulting module name: SettingsHandlers_Notifications.dll, version: 10.0.11099.1000, time stamp: 0x56918ea0
Exception code: 0xc0000005
Fault offset: 0x000000000002a551
Faulting process ID: 0x2598
Faulting application start time: 0x01d152b3a5fc09b6
Faulting application path: C:\Windows\System32\SystemSettingsBroker.exe
Faulting module path: C:\Windows\System32\SettingsHandlers_Notifications.dll
Report ID: c4cdc306-4e6a-4608-9ae2-4efb595df3bf
Faulting package full name:
Faulting package-relative application ID:-
System
-
Provider
[ Name] Application Error
- EventID 1000
[ Qualifiers] 0
Level 2
Task 100
Keywords 0x80000000000000
- TimeCreated
[ SystemTime] 2016-01-19T12:40:55.901450000Z
EventRecordID 3029
Channel Application
Computer MOTHER-PC
Security
- EventData
SystemSettingsBroker.exe
10.0.11099.1000
56918de6
SettingsHandlers_Notifications.dll
10.0.11099.1000
56918ea0
c0000005
000000000002a551
2598
01d152b3a5fc09b6
C:\Windows\System32\SystemSettingsBroker.exe
C:\Windows\System32\SettingsHandlers_Notifications.dll
c4cdc306-4e6a-4608-9ae2-4efb595df3bfFaulting application name: explorer.exe, version: 10.0.11099.1000, time stamp: 0x56918bfb
Faulting module name: PASHLEXT64.DLL, version: 16.0.8.1, time stamp: 0x568fd3b0
Exception code: 0xc0000005
Fault offset: 0x00000000000306f1
Faulting process ID: 0x3714
Faulting application start time: 0x01d152b6a3945c51
Faulting application path: C:\WINDOWS\explorer.exe
Faulting module path: C:\Program Files (x86)\PowerArchiver\PASHLEXT64.DLL
Report ID: f2390bbd-b321-4e12-9997-355db62ff9c6
Faulting package full name:
Faulting package-relative application ID:-
System
-
Provider
[ Name] Application Error
- EventID 1000
[ Qualifiers] 0
Level 2
Task 100
Keywords 0x80000000000000
- TimeCreated
[ SystemTime] 2016-01-19T12:43:07.898766600Z
EventRecordID 3032
Channel Application
Computer MOTHER-PC
Security
- EventData
explorer.exe
10.0.11099.1000
56918bfb
PASHLEXT64.DLL
16.0.8.1
568fd3b0
c0000005
00000000000306f1
3714
01d152b6a3945c51
C:\WINDOWS\explorer.exe
C:\Program Files (x86)\PowerArchiver\PASHLEXT64.DLL
f2390bbd-b321-4e12-9997-355db62ff9c6All apps / tools are bought. No cracks etc.pp.
:confused:
-
-
Can you try uninstalling PA 2016, rebooting and then installing it again please?
Thank you!
-
As a fast workaround, can you please set language manually to English or other language you might be using. This is in Options> Language.
After that check it out, it should be working.
-
Please check this release:
http://dl.powerarchiver.com/2016/powarc160055.exeAnd let us know how it goes… should be fixed. Thank you.
-
Please check this release:
http://dl.powerarchiver.com/2016/powarc160055.exeAnd let us know how it goes… should be fixed. Thank you.
Thanks a lot for your help !
v16.00.55 doesn’t have the right-click issues anymore.
:)
-
Thanks a lot for your help !
v16.00.55 doesn’t have the right-click issues anymore.
:)
thanks, this was due to automatic language selection and we fixed it in one of the internal releases but it came back… since we already knew what it was and we noticed it day before, we were able to quickly fix.
-
thanks, this was due to automatic language selection and we fixed it in one of the internal releases but it came back… since we already knew what it was and we noticed it day before, we were able to quickly fix.
Awesome work !
:)