-
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
Plugin's
-
i have version 10.21.17 and have downloaded the MSI plugin however its file extension is .ppf and when i go to instal a plugin its looking for extension .wcx will the above plugin work or do i need to rename the extension.
-
just doubleclick on .ppf file in windows explorer and PA will ask to install it.
-
just doubleclick on .ppf file in windows explorer and PA will ask to install it.
Sorry, Spwolf, but .ppf files are not associated with PA (at least on my system) and I can’t find this extension in Options > Configuration > File Formats…
So after double clicking that file, please select the PowerArchiver from the list (or provide the path to POWERARC.EXE, by default - C:\Program Files\PowerArchiver\POWERARC.EXE) and click OK
Then PA will ask to install…Thanks,
-
@NTFS:
Sorry, Spwolf, but .ppf files are not associated with PA (at least on my system) and I can’t find this extension in Options > Configuration > File Formats…
So after double clicking that file, please select the PowerArchiver from the list (or provide the path to POWERARC.EXE, by default - C:\Program Files\PowerArchiver\POWERARC.EXE) and click OK
Then PA will ask to install…Thanks,
thats an bug then… you can also open it inside of PA via Open button and it will ask for installation…
thanks.
-
How do I know the plugin installed? There’s nothing in the plugin folder.
-
How do I know the plugin installed? There’s nothing in the plugin folder.
You don’t see the files in Program Files because PA stores them in:
C:\ProgramData\ConeXware\PowerArchiver\Plugins
(in Windows Vista)
(common Application Data folder)Vista UAC requirements do not allow writting to Program Files…
You can see the plugins list and add/remove them in Configuration > Plugins…
Thanks,
Serhiy
-
Found it.
The strange thing is, this plugin is installed in the folder.
C:\Documents and Settings\All Users\…
My guess is that everybody gets the plugin instead of only me. Is this wanted behavior?
-
-
Found it.
The strange thing is, this plugin is installed in the folder.
C:\Documents and Settings\All Users\…
My guess is that everybody gets the plugin instead of only me. Is this wanted behavior?
As I wrote, PA stores them in Common Application Data folder. And from there they are avaiable TO THE ALL WINDOWS ACCOUNTS.
You are using Windows NT/2000 or XP…
so it is in C:\Documents and Settings\All Users…
In vista it is
in C:\ProgramData…And it is normal behavior because it allows to install Plugins without Administrator permissions
-
One more thing. If I install a ppf by double clicking it, it looks like it is installed by a admin account instead of Current User.
-
@NTFS:
As I wrote, PA stores them in Common Application Data folder. And from there they are avaiable TO THE ALL WINDOWS ACCOUNTS.
You are using Windows NT/2000 or XP…
so it is in C:\Documents and Settings\All Users…
In vista it is
in C:\ProgramData…And it is normal behavior because it allows to install Plugins without Administrator permissions
It could also install it for my account only. The files would be placed in C:\Documents and Settings\Guido\… I can access this folder also. And remove it without admin permission.
My question was if installing the it for all users is wanted behavior. I would at least expect a question if I want to install the plugin for myself or for all users.
I it’s for all users I guess C:\Documents and Settings\All Users… is fine. If it’s for myself only, I would expect the files to be in
C:\Documents and Settings\Guido…
-
One more thing. If I install a ppf by double clicking it, it looks like it is installed by a admin account instead of Current User.
Did you receive UAC elevation prompts in vista? If you did that in WinXP then how do you know that it requires Admin rights?
-
It could also install it for my account only. The files would be placed in C:\Documents and Settings\Guido\… I can access this folder also. And remove it without admin permission.
C:\Documents and Settings\Guido
is “User Application Data” folder avaiable only to specific Windows Account and unaccesible to others (except Administrator’s , of course)…My question was if installing the it for all users is wanted behavior. I would at least expect a question if I want to install the plugin for myself or for all users…
Ok, this Prompt can be added in the future version…
-
It’s in XP. The thing is. After install, PA is opened. This installation is not registered.
Second point. If I close PA and reopen PA and look for my plugins in the configuration it’s empty.
I have open PA and from the main window I have to open the ppf file to install it. If I don’t do this, the plugin does not get installed.
-
It’s in XP. The thing is. After install, PA is opened. This installation is not registered.
Second point. If I close PA and reopen PA and look for my plugins in the configuration it’s empty.
I have open PA and from the main window I have to open the ppf file to install it. If I don’t do this, the plugin does not get installed.
It is because PA doesn’t seem to check if there any plugins in the folder. It looks up the Windows Registry in:
HKEY_CURERNT_USER\Software\PowerArchiver\Plugins
for them…
And when you install the plugin it writes it’s path to the registry…Look! it uses HKEY_CURERNT_USER this means that plugins will be visible as “Installed” only for the current windows account.
I think it wold be better instead of storing this information in registry just scan the Plugins folder for them…
-
BTW, storing this data to the registry privents the For-All-Users installation without admin permissions…
-
Will have to think about the answers :-).
-
well i have vista UAC turned off and i opened the files by selecting open archive, change file type to *.ppf then install it and it appears to be working.
thanks for your help guys
-
well i have vista UAC turned off and i opened the files by selecting open archive, change file type to *.ppf then install it and it appears to be working.
thanks for your help guys
Actually you don’t have to disable UAC to do this. Just open the file as standard user. I don’t recommend disabling security features such as UAC at all. If some application requires disabling UAC to work properly then it’s its developers’ problem.
