-
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.
-
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. -
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
-
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.
PAE file issue
-
Hi there, am new to these forums.
I created a PAE file (encrypted) containing folders from my old laptop (Win XP) that had issues.
I’ve recently needed these files and tried to open the PAE file on my new Vista laptop, however upon opening the file it just shows as a “10+” under a plain file icon.
The file properties of this file shows “File Size: ?” and “Ratio: ?” as if it cannot recognise it.
When trying to extract this ‘file’ I get a message that says “Unknown encryption method”
Any ideas?
-
@Paz:
… however upon opening the file it just shows as a “10+” under a plain file icon.
The file properties of this file shows “File Size: ?” and “Ratio: ?” as if it cannot recognise it.
When trying to extract this ‘file’ I get a message that says “Unknown encryption method”
Most important - are you saying that PA accepts the password OK?
Do you remember what version of PA you used to create it? (If you always keep up to date - maybe how long ago it was?).
What type of archive did you encrypt?
What is the file size reported by windows of the PAE file? -
Hi mate,
To be honest I can’t specifically remember creating a PAE or a ZIP - something messed up and it changed the extension of the file. But I always created PAE so am 99.99% sure it was a PAE - when I change the extension to a ZIP it doesn’t recognise it at all, and when I change it to the PAE that I am sure it was - then it doesn’t show any error and goes straight into the file (not asking for any password).
It was a long time ago, so I probably created it using 2007 or so and am now trying 2009 to open it - could this be something to do with it?
The file contents are various other PAE files!
File size is 63.2MB -
@Paz:
Hi mate,
To be honest I can’t specifically remember creating a PAE or a ZIP - something messed up and it changed the extension of the file.
I am not sure what you mean by “it” - that changed the extension. If not done bu the user, that usually only happens with disk cleaner/recovery utilities - but then to “tmp” etc. The only time PowerArchiver changes the extension is when the user uses it to Encrypt an archive and create the PAE file (and entering a password).
@Paz:
But I always created PAE so am 99.99% sure it was a PAE - when I change the extension to a ZIP it doesn’t recognise it at all, and when I change it to the PAE that I am sure it was - then it doesn’t show any error and goes straight into the file (not asking for any password).
If PowerArchiver does not ask for a password, then it is not a valid PAE file. Changing the file extension doesn’t change the contents.
@Paz:It was a long time ago, so I probably created it using 2007 or so and am now trying 2009 to open it - could this be something to do with it?
The file contents are various other PAE files!
File size is 63.2MBIf it was created using a release version of Powerachiver then that is not the problem. I was just asking (in a roundabout way) for confirmation that you did use PA to create the file.
A (valid) PAE file will be an archive file (Zip, 7z, Tar, Gzip etc) that was created first and then encrypted as it only works on single files. If PA does not ask for a password then the file is not a PAE file and you need to determine what file type it actually should be. Even with multiple PAE files as the contents, you would have to create a single file (e.g. TAR file) first to encrypt again.
Otherwise, it “was” a real PAE file that has been so corrupted as to be unreadable - but that would mean the contents are not retrievable.
This is why you should only use encryption if you test/verify immediately after creation before deleting anything(and keep alternate/multiple backups as well).
-
or it could be corrupted if it was stored on cd/dvd media especially.
