-
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.
SOLVED encryption didn't work correctly
-
HI.
I have here a little problem.
Actually I have encrypted a small file, 30MB, to an encrypted 7zip Archiv. This works very well.
But now I wanted to encrypt a big file which is 1.3GB large.
I use the same options like before for the small file. But I now get a 1KB file. When I try to open it I get only an error massege that powerarchiver 2017 can not open this file. The file seems not to be an valid Archiv.But as I said, I use the same Options to create an encrypted file from the big file as I use for the small file.
With powerarchiver 2016 i haven’t this Problems. When I use an big file like the one from above, all works well.
So what can i do to make an valid encrypted Archiv with the big file?
Or I maybe go back to powerarchiver 2016?Thanks for your help.
Michael Duss -
@mduss This should be fixed in new release:
https://forums.powerarchiver.com/topic/5848/fast-ring-powerarchiver-2017-17-01-04/7Can you let us know if it works fine? In PAES, it will prioritize speed over compression here.
thank you!
-
@mduss hello, are you using latest PA version? (.92) and what are your OS and your cpu/memory? What are 7z settings?
Also try using PA format instead of 7z, and let us know if that works. Thanks!
-
Hi spwolf
Today I have installed the new Version from PowerArchiver: 17.00.92.
This Version have the same Problem.
I use Windows 7 Ultimate 64-Bit and 32GB RAM with an Intel core i7 5930When I wanted to encrypt an Archiv I used the following way:
I use the kontextmenue in the file Explorer and use encrypt.Here I use the following Options:
target Format: 7-zip
compression:
Format: 7-zip
method: LZMA2
packing: Ultra
generate solid Archive: yesencryption method: AES - 256 Bit
This are the Options I use.
With small files like 50MB there is no Problem.
But when I wanted to encrypt a large file like an 800MB or several files which have togehter a large file size or so than I will get only a small 1KB file.But after some test I think I have found the Problem Kombination:
When I use the Methode LZMA2 AND one of the following Options for packing: Ultra, Maximum or normal, than I get this error.
When I use fast or None, than I haven’t this problem.So I think there is an error in the packing method Ultra, Maximum and normal with the LZMA2 method
But my Problem is, that I can not use the new PA format because I load this encrypted file to an webhoster so other Users from my Forum can download them. This archives are Game Mods.
And not everyone from my Forum use powerarchiver.
So I use a file format which can open from other archive programs too like 7zip.
So my favorite target Format is 7-zip. And I use LZMA2 and Ultra because the higher compression rate.With powerarchiver 2016 I didn’t have this Problems. With 2016 everything works fine with the same Options I described above.
So I will use 7-zip, LZMA2 and fast Options at the moment.
Thanks.
Michael Duss -
@mduss lets try this - right click on files in explorer and pick compress with options… now try same combination, does it work? It actually should work, there was some fix implemented in main PA, maybe not in paes.exe.
Also, for testing purposes, can you use pa/extreme for same file, just so we can see what is the size difference between PA and 7z?
thanks!
-
@spwolf said in encryption didn't work correctly:
@mduss lets try this - right click on files in explorer and pick compress with options… now try same combination, does it work? It actually should work, there was some fix implemented in main PA, maybe not in paes.exe.
Also, for testing purposes, can you use pa/extreme for same file, just so we can see what is the size difference between PA and 7z?
thanks!
Hi spwolf.
The method with “compress with options” works very well. Here I have no problems.
So the Problem seems to be the paes.exe.The differences between pa/extrem and 7-zip LZMA2/Ultra are very small.
Depending on the used files the differences are 1 till 2 MB.
Here the Files had a complete size from 323MB and they were multiple files with difference file Format like .exe, .pdf and so on. The pa file was 2 till 3 MB smaller.With an other file I had a difference from 8MB. This was an single .zip archiv with 810MB witch I have encrypted with the Explorer Kontext “compress to…”
The filesize was 810MB. And here the pa file was 8MB smaller.So I think the paes.exe needs an fix.
By the way.
Do you have any Infos regarding this Problem?
https://forums.powerarchiver.com/topic/5814/powerarchiver-outlook-plug-in-don-t-works-correctly/3Thanks very much.
Michael Duss -
@mduss not yet for PAOP, we will update bug when fixed. Thanks for the rest of it, entered it for one of the next release.
-
@mduss This should be fixed in new release:
https://forums.powerarchiver.com/topic/5848/fast-ring-powerarchiver-2017-17-01-04/7Can you let us know if it works fine? In PAES, it will prioritize speed over compression here.
thank you!
-
Hi spwolf.
I have tested it today and it work now correctly.
So the problem is solved for me. :-)Thx.
MfG
MDuss