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 errors
Is 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.
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.
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.
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
For some reason, the PowerArchiver functions in the Windows 11 context menu no longer work after the last Windows Update. Only the functions in the classic context menu function as they should.
I’ve tried uninstalling PowerArchiver and using RevoUninstaller to remove all bits and pieces that were left behind and did a clean install of PowerArchiver, it didn’t fix the issue. Other items in the Windows 11 context menu work.
FTP - works differently, depending
If I am in the PA window and choose FTP, the transfer works fine using both plain FTP and FTP +SSL/TTL.
Using the shell extensions, FTP works for me only if I use plain FTP, even to the very same site.
I assume this is a glitch.
It would be nice if the shell extension FTP option allowed some encryption.
Basically, uploading to an FTP +SSL/TTL site via shell does not work for you, but others work OK?
Yes. I can use encryption if I am in PA. I cannot use it from the shell.
And in both cases I am going from the same folder to the same folder on the off-site location.
It would be nice of the encryption FTP options also worked from the shell.
thanks! logged in
Please check this version and let us know if it fixes your issue:
Not only does it not fix the problem.
Now I cannot use encryption in ftp even within PA.
So I will have to uninstall and reinstall the previous version.
One thing that would be helpful. with major upgrades, I lose all my settings. I can save and import some of them. But others, like the location and content of the quick access bar are lost and have to be rebuilt. Now we are only talking about a couple of minutes here, but . . .
BTW, odd thing, at the very instant I tried to do this, I got 2 copies of an update to adobe flash player. Not sure if it is just a coincidence, or . . .
thanks… i have setup ftp ssl server now for the dev team to test against, so we should have another build hopefully soon.
BTW, With FileZilla going to the same folder at the same site, I use “Explicit FTP over TLS.”
do you know what ftp server is being used? If we can get access, it would be helpful, since on our ftp/ssl it works fine. But there are many different server softwares for ftp.
if it is confidential you can email the info… if it is impossible, then let us know the name of the server.
I can use plain FTP without a problem. Just none of the encrytion options.
And I have no problem using FileZilla to that site.
I guess I will just have to use FZ for the last step of my transfer.
Or send it unencrypted.
but do you know which ftp server is being used? it should say so when you login in ftp client, it would be one of the first strings…
But I don’ see that is going to help. But try.
Never had problem logging onto ANY FTP server with FZ.
But if that will help, give it a whirl. However, I expect I will just need to plan on using the two step process.
Actually, I cannot even do it from the PA window any more. Maybe installing the rc1 changed a setting somewhere else.
Silly me. I should have stuck with what I had.
i mean the actual ftp server software… like filezilla server or what exactly?
i got it from the server, it is Pure-FTPd… will let you know more.
Glad you figured out. I wasn’t sure what you were asking.
The server type (using FZ) is set to autodetect.
ok, repeated here since this is real thread:
This is new version PA 2012 RC1 13.00.24:
Now explicit SSL works on Our server (which is different server software), so please check with yours!
SSL works. Cannot use TLS, but this is great.
it is the same, we just call it differently - what is explicit SSL we call ftp+ssl and what is implicit SSL in filezilla, we call ftp + ssl/tls… but otherwise it is same encryption used.