-
PA 21.00.18 running on Windows 7 64 bit.
I made a big .PA file and thought I’d check it was made correctly with Menu / Actions / Test.
Discovered:
a) PA always issues a UAC prompt to do this!
b) PA always says there are many errors in PA files. -
Re: Explorer.exe Crash on right click
This appears to be happening again with the Power Archiver 2022 shell extensions.
When I have Use Explorer Shell Extensions enabled in Power Archiver Configuration and right-click on c:\Users\username\Start Menu, (hidden Junction file), File Explorer crashes.
I have version 21.00.15 (03/2022) 64-bit installed in Windows 10 Version 21H2 (Build 19044.1826).
-
In the latest version of PA, on W11 (latest build/SP) when you try to use the first level context menu - NOTHING HAPPENS (particularly when you do this from Downloads or Documents folders) - however I noticed that it DOES WORK when you use the context menu from the Desktop. Going to the second level context menu does work however.
-
PA 2023 22.00.08
Long time no seeing. So I start up the new year with a first problem : the virtual driver cannot be installed. Reason : it is missing in the Fast Ring PatchBeam Update Service…
Virtual driver PA 2023-01-28 152607.png
It seems a standard problem with new releases :-)
Can I have a link or can it be fixed. Thank you. CU later -
When the function for testing archives is invoked via the shell context menu (PowerArchiver > Test) then all the files in the archive get extracted to the current folder.
The test dialog reports as many errors as there are files in the archive but it fails to give any hint as to which files are supposed to be erroneous or what the nature of the problem might be. Comparing the extracted files to the originals shows no differences at all.
The .7z in question was produced with maximised compression settings in 7zip (taking forever but resulting in smaller archives than .7z produced by PowerArchiver with maximised settings). Therefore I wanted to see whether PowerArchiver can at least test .7z that it produced itself. Hence I had PowerArchiver convert a .pa with the same contents to .7z. There weren’t any errors reported but the resulting .7z contained fewer than half of the files contained in the .pa (137 of 366), so I scratched that test.
Performance is abysmal when testing via the context menu (e.g. almost 2 minutes for testing a .7z that 7zip tests in 4 seconds), but that is most likely due to the fact that the extracted files are written to disk. Testing the same .7z in the PowerArchiver GUI takes only 8 seconds but causes the mysterious appearance of a UAC dialog, as reported elsewhere.
The testing function is vital because PowerArchiver has a history of producing archives that it cannot unpack without errors or that do not conform to the respective file format standards (e.g. ZIP) so that other programs report them as erroneous.
The point of creating archives is that the files in them will most likely have to be extracted at some point. If the extraction cannot be guaranteed to produce correct results then the whole program is absolutely pointless. Actually, worse than pointless - it causes data loss and hence damage.
-
In PowerArchiver 2023 22.00.06 configuration, the option labelled “Start PowerArchiver 2023 Starter when my computer starts” seems to be redundant.
I am only allowed to change this option when PA Starter is disabled, and then it seems to be ignored.
When I enable PA Starter this option is forced to the enabled state.
I think it’d be good to remove “Start PowerArchiver 2023 Starter when my computer starts” completely. I’ve always found it confusing having both options.
Added later: However i don’t particularly want to use queue but I do like having the PAStarter icon in my tray area.
-
W10 Pro 22H2 - 64 -bit
PA 22.00.06 (PA 2023)
It has been the case with previous versions of PowerArchiver, but I had hoped that the latest might behave differently. Not so, I’m afraid.
I have, for various obscure reasons, created a few .pa archives, mainly in the hope that they will save me some more space. From time to time, I use the “Test” option to check that important archives are OK and uncorrupted.
With every .pa archive I’ve tested, the process runs through OK but then reports that there are errors. This is always the number of files in the archive e.g. if 11 files, then 11 errors reported.
In the .pa, I can:-
preview the files (usually PDF) extract some or all files and look at or use them convert the .pa to a .zip or .zipx archive, which then works fine and tests without errorsIs it the case that the Test routine isn’t designed for .pa archives, or is there another reason? Although the .pa seems to function properly, despite the test reporting errors, I would like to be sure that every .pa is OK and not “broken”.
Some of the .pas are quite old and produced with earlier PA versions (they are truly “archives”). If I extract all the files in the old .pa, create a new, fresh .pa and add back the files to that, then test the new, no errors (at least in the .pa I’ve tried this on) are reported. This would suggest a mismatch between old .pas and newer versions of PA itself.
-
Clipboard02.jpg
See the, supposedly, blank space where the green box is? It’s like that in Modern Light theme too. I can toggle it, but it’s missing text or shouldn’t be there I guess?
Thanks :)
-
Dear @Alpha-Testers and all of our users,
time has come for testing of PowerArchiver and PACL for macOS.
Please let us know here if you have Mac and can test latest builds.Features implemented:
PowerArchiver 2020 - tabbing, opening, extracting, adding, testing, favorite folders, support for multiple languages, opening via Finder, explorer mode, installer.
PACL 10 - support for most formats and features in Windows version.Upcoming: Tools such as archive converter, batch zip, multi-extract.
To start testing, please sign up here in this thread, and we will send you latest build.
thank you!
Ashampoo_Snap_Wednesday, November 20, 2019_12h54m56s_008_.png Ashampoo_Snap_Wednesday, November 20, 2019_12h55m05s_009_.png Ashampoo_Snap_Wednesday, November 20, 2019_12h55m14s_010_.png Ashampoo_Snap_Wednesday, November 20, 2019_12h55m30s_011_.png Ashampoo_Snap_Wednesday, November 20, 2019_12h55m39s_012_.png Ashampoo_Snap_Wednesday, November 20, 2019_12h55m49s_013_.png Ashampoo_Snap_Wednesday, November 20, 2019_12h56m00s_014_.png Ashampoo_Snap_Wednesday, November 20, 2019_12h54m43s_007_.png
76e97ab9-8d75-4175-9ce8-446500031f38-image.png
Associating archive files with pa
-
i have tried to assocoiiate archives with pa tried all methods avaliable and before anyone asks i even used the button on the configuration menu. No luck when will this be fixed.
-
What file type isn’t working? I have zip, rar, and 7-zip files and they all show up associated with PA.
-
seems to work here
-
i have installed a clean version of pa latest one onto the computer with windows 2000 installed.
i have even tried winrar and winzip and they both associate with all files ok even zipgenius can be associated with archives ok. So I know the problem has to be powerarchiver
i also have installed the latest opus directory 9 and that can also be assocvauted ok
I have checked pushed the assicate now button only to find nothing happens no changes are made to the associations.
when will a fix be made as this make it very hard to use pa. I likde pa loads more than the other archices even pas freeware version works ok on assocations so does versioin 9 of powerarchiver.
Is there a fix i can do till you fix the fault within pa’s assocaties now button
-
what is “pa latest one”… what exact version? What is the date of _pasetup.exe inside of your PA folder?
thanks,
-
10.10.10
The Same Version On Your Download Page For The English Version
date of _pasetup.exe 21 May 2007, 23:00:00
-
I have tested this feature out to find that the only archive that pa doesn’t associate with is zip files for some reason. When will a fix be issued this is a serious fault and needs to be corrected asap
I found this out by testing it along side winzip as that program can tell you what program is ASSOCAITED WITH WHAT ARCHIVE PROGRAM. I have asked for this feature to be included with powerarchiver, so i can give more info if this happens as it has.
Basically what i am saying is, is that powerarchiver has lost the ability to assocaite with zip files.
fix on way i hope as i use zip files all the time.
-
does anyone else have issues with associating files? I tried it on all of our test computers and it worked fine…
-
I tried this :
Starting with PA associated.
Using WinZip associate (all files)
Then using PowerArchiver associate (all files)No problems - Everything worked as expected.
Windows XP SP2. -
think i’ve found problem opus directory 9
this takes over control of the associations but does not work with the assocaites of powerarchiver or for that matter winzip or winrar.
you need to talk to these people to find out why this happens.
I have let microsft run some tests on my computer and that is what they say.
Itsd opus directory 9 fault as it handles assocaitions differently which means pa winzip and winrar all have2 to be assocated by hand via opus directory 9 if you are using that.
-
:-)
-
v10.10.10
I started with PA associated with .zip extension.
Verified PA had .zip association by double-clicking a .zip file and saw that PA opened the file.
Closed PA.
Ran WinRAR, told it to associate with .zip extension.
Verified WinRAR had .zip association by double-clicking a .zip file and saw that WinRAR opened the file.
Closed WinRAR.
Ran PA, told it to associate with .zip extension.
Verified PA had .zip association once again by double-clicking a .zip file and saw that PA opened the file.Summary:
Everything worked as expected.Prognosis:
File extension association would seem to be corrupt on bug reporter’s pc.davidsplash, try testing on another pc or a virtual pc with only PA and one other archive utility installed such as WinRAR or WinZip. I think too many archive utilities installed at one time may be the culprit here. Or you can try uninstalling the others one at a time, each time telling PA to grab the .zip association and test if it works. Opus may also be conflicting here.
-
Looks like we were testing at the same time. ;) Glad you were able to figure out the root of the problem. :)
-
p.s.: Did you really let Microsoft use your pc, I hear those guys write trojans :p
-
p.s.: Did you really let Microsoft use your pc, I hear those guys write trojans :p
Davidsplash likes to “live on the edge” :D
-
well a mate of mine works for microsoft and he checked my system and found that to be true about opus directory, so does this mean that pa has to rewrite its associations to work round opus 9
-
I have let microsft run some tests on my computer and that is what they say.
!=
well a mate of mine works for microsoft and he checked my system and found that to be true about opus directory
;)
so does this mean that pa has to rewrite its associations to work round opus 9
Good question. In the meantime…if a powerful Windows Explorer replacement solution is what you’re seeking, perhaps give Total Commander a try - it is very nice and useful with plugins etc. There’s also 2 custom versions you might find called Total Commander PowerPack and Total Commander Ultima Prime. Happy hunting! :)
