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.
Another issue with virtual drive
-
I can reproduce this.
I have not used virtual drive for a while. I mount an ISO…NO drive letter appears. I mount a second ISO, no drive letter appears. The ISOs cannot be deleted so something is happening. When I mount a third ISO, I get a BSOD. I mount by right-clicking an ISO and selecting 'Mount as Virtual Drive…@
I am writing this from Linux as my Win7 x64 PC reboots for the 6th time with this issue. I casn test it on other OSs on other PCs if needed.
Please just ask for any further info. I go through phases of using this feature and am lost without it.
Using the latest version of PA 2012 and the Starport drivers - I check for updates quite frequently.
Please advise.
Regards
DrTeeth
Update: Uninstalled the Starport drivers and reinstalled via PA with no change (2 no drive letters and 3rd one gives BSOD). Until I get advice for troubleshooting, I will uninstall and have to use another software solution for virtual drives.
-
did something change in your system? It seems as if something is blocking virtual drive drivers or something like that… actual drivers have not changed in years.
-
Hi,
I am not aware of anything that has changed. I have another x64 bit Windows OS on this main PC, that is running the same system drivers etc and The Virtual Drive works perfectly. I assume that that rules out anything ‘low level’?
I thought I had found the conflict, but further investigation revealed that I had not. The virtual drive worked immediately after the driver install.
I can mount an ISO, but no drive letter appears. I can TRY to unmount an ISO, but, in spite of a message saying that the drive has been unmounted, it still appears as mounted in the unmount dialogue. The presence of the mounted ISOs stops a reboot. I’m completely stuck now.
DrT
-
Just to confirm,
It works fine on one system but it does not on another one? -
Yes, it also works fine on the same system in another 64 bit Windows setup (Vista SP2) using the same drivers as the Win 7 x64 setup (I multi boot my main PC). I have uninstalled and reinstalled both the PA and SPTD drivers several times without any change.
They have always worked flawlessly for me before.
DrT
-
it is obviously something that has caused this, some other driver or something similar… i need to check how to actually uninstall the driver properly (aka clean installation)… Remind me if I dont post anything in few days :-)
-
Will do spwolf.
Thanks
DrT
-
Reminder for spwolf for manual driver uninstall instructions as requested. Thanks in advance, DrT
-
Could you please post the manual uninstall instructions for the virtual device drivers that you mentioned?
Thanks again,
DrT
-
Could you please post the manual uninstall instructions for the virtual device drivers that you mentioned?
Thanks again,
DrT
i am on vacation until Sunday :-)
I tried to quickly figure it out but didnt help….
-
I thought you were a bit quiet ;-). Sorry to hassle you on holiday, but I had known I would have stayed schtum.
Though the issue is very annoying (as PA’s virtual drive works the best out of all the others I have tried as a replacement) I do have a working replacement, though don’t like it. At least I can wait for the manual uninstall.
Regards
DrT
-
Any news on this one yet?
DrT
-
still not Monday :-)
-
still not Monday :-)
Sorry, I thought you posted over a week ago - damn my addled memory. I am REALLY sorry.
DrT
-
Gentle reminder<hoping spwolf=“” has=“” not=“” extended=“” his=“” holiday=“” and=“” is=“” sipping=“” pina=“” coladas=“” on=“” some=“” distant=“” sunny=“” beach=“”>
Regards
DrT</hoping>
-
Device Manager> Storage Controllers> Starport Storage Controller… uninstall it and then reboot… then install pavd again and see if that helps?
thanks and sorry for the delay! I couldnt find it initially, who knows where was I looking.
-
Hi,
Device Manager> Storage Controllers> Starport Storage Controller… uninstall it and then reboot… then install pavd again and see if that helps?
That was the first (and second and third and…) thing I tried and it does not help at all.
Please see screen shot - still no drive letter. Problem still remains.
Regards
DrT
-
Sorry for my impatience, but I use this feature daily and am really missing it. Can anything else other than a standard uninstall be advised?
DrT
-
Sorry for my impatience, but I use this feature daily and am really missing it. Can anything else other than a standard uninstall be advised?
DrT
unfortunately it seems that something else in your Windows installation is blocking it as it works on the same computer but different Windows installation.
Is it too much work to reinstall Win?
-
Reinstalling is not an option as a) it would be a massive undertaking, but more importantly, b) I would very likely install the software that is conflicting as I would not know which was the guilty party.
I am more than happy and able to modify the registry or anything else that could fix this if you have any ideas.
What sort of things could conflict? All chipset drivers are the same version across all versions of Windows on this machine.
Regards
DrT
-
Can you try and (“Repair”) windows via the recovery disk?
That way your not going down a route of formating and installing from scratch. It could be anything from Driver’s, Corrupt Windows Components such as Registry issues.Windows Repair might help, if it doesnt then even i would suggest a rebuild.
An Odd one indeed!
-
Thanks for your input Sir.
The problem is that although I really like the PA implementation of virtual drives, that is the ONLY issue I have with my current setup. Also, all other virtual drive software that I have tried as replacements work flawlessly - the only common denominator is that they have drive letters pre-allocated…they appear as empty CD/DVD drives.
The issue could be down to some installed software, which I would unknowingly reinstall.
TBH, as much as I do not like computers to ‘win’, trying to fix this one by way of repairs and rebuilds just is not worth it.
Like last night - installed Fedora 17 - used to work well when first released, then had issues with some updates not taking. Tried again (last night) after a couple of months and after 2 hours of installing and updating, the sod would not boot up correctly (it did initially, but not after all the updates). problems with the free source nouveau nVidia driver. Not worth the hassle to fix either - I have 4 other Linux distros installed and OpenSuSE 12.2 is out in 5 days.
I will be happy to test any fixes that the team can come up with if this is found to be fixable.
Regards
DrT
-
did you try using System Restore to the time when you think it all worked? I think it makes new restore point automatically, but you can make sure it does…
-
The issue is with the automatic issue of drive letters. I found another piece of software that worked similarly to PAs and also used StarPort drivers. I have updated these drivers via windows device manager without any difference. Anybody have any ideas where the upper and lower filter keys for the PA virtual drive are in the registry or even what the drive is called (Rocket, StarPort, PowerArchiver, SPTD)? Restore points will not help, old ones gone as many installs and uninstalls have written new ones.
