-
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.
Extract to dir;PA can't handle;dir's created anyway
-
try to extract an exe file through the context menu, when PA shows you the “extract to” option…sometimes it’s a file PA can’t handle.
also in those cases, if you chose to extract into a folder, that folder will be created.
wouldn’t it be better for it to be deleted, as the extraction process failed so you surely will delete the new dir manually?
-
What happens if some files were extracted and some were not? Or if folder is already present and file doesnt work? Prefferably, we wont delete files or folders that we dont have to since that is just asking for some bug to kreep in and delete your files.
thanks,
-
What happens if some files were extracted and some were not? Or if folder is already present and file doesnt work? Prefferably, we wont delete files or folders that we dont have to since that is just asking for some bug to kreep in and delete your files.
thanks,
you’re sort of right, spwolf…yes, that would lead to problems if the dir was already present.
then…maybe a popup win saying “would you like to delete the dir XXX (which was just created)”?
what do you think?
-
I have fixed so now if folder was created by PowerArchiver and no files were extracted due broked archive (or unsupported SFX file) will be removed by PoweArchiver automatically.
-
I have fixed so now if folder was created by PowerArchiver and no files were extracted due broked archive (or unsupported SFX file) will be removed by PoweArchiver automatically.
you rock, man! thank you so much! :D
-
Hi,
here is the latest TEST version, 9.00.34 with fix for this bug. Please let us know if it fixes the issue and if you notice anything else at all. You can install this version over the last one and restart your computer.
Download TEST version 9.00.34:
http://www.powerarchiver.com/test/powarc90034.exethank you!
-
let me corrupt an archive with WinHex…and I’ll check! :cool:
-
let me corrupt an archive with WinHex…and I’ll check! :cool:
Bug gone…but not completely!
Gone, because PA now tells me at once that the file’s corrupted, and does not create any new dir! :D
WELL DONE!“not completely” because I have to click TWICE on “OK” to close PA warning messages, it seems two identic messages come out.
FYI, the “double click bug” was there in .33 as well…check it! ;)
-
What double click bug - it wasn’t something mentioned in this thread?
-
no, I had not mentioned it anywhere before…yet it’s related to the bug I opened this thread for.
when a corrupted file fails to extract, no folders are created, ok, problem solved.
but PA tells you TWICE that the file’s corrupted and can’t be extracted, and you have to click TWICE on “ok” to get rid of the warning message…I think you can reproduce that behaviour quite easily…let me know!
-
Still cannot reproduce double dialog. Can you please tell me exact message being shown and maybe send me smallest file you are having this problem with - since double dialog does not show on any corrupted archive.
-
download the following file:
http://user1.7host.com/maiuebsait/mix/corrupted.7z
uncompress and see the avi I created.here’s the corrupted zip file I used:
http://user1.7host.com/maiuebsait/mix/CorruptedArchive_TestPurpose.zipso…could you reproduce it now?
pls let me know!the problem persists with v9.01.01 as well!
-
@ivan: did you read my last message? what do you think?
-
Thanks!
I will check it.
-
with the pre-release 9.01.02 PA is back to the situation I reported at the beginning of this thread:
-if you try to extract the corrupted file via “extract here”, you’ll see the extraction windows complete its task but then nothing will be extracted.
-if you choose “extract to \filename” the filename dir will be created, empty
-if you open the archive in PA it will show you the name of the file inside, and if you try to extract or open it from there, you’ll be given the “unexpected end of zip file”, and you’ll have to click twice on the message window to get rid of it.
so, I have to say 9.01.01 was better…ok, you had to click twice on the message win as well, but at least it found out the archive was corrupted, and the message would always pop up!
-
with the latest 9.02.00, nothing has changed with regards to my previous post… :(
@dev’s: is it going to be fixed any shortly? thanks!
-
with the pre-release 9.01.02 PA is back to the situation I reported at the beginning of this thread:
-if you try to extract the corrupted file via “extract here”, you’ll see the extraction windows complete its task but then nothing will be extracted.
-if you choose “extract to \filename” the filename dir will be created, empty
-if you open the archive in PA it will show you the name of the file inside, and if you try to extract or open it from there, you’ll be given the “unexpected end of zip file”, and you’ll have to click twice on the message window to get rid of it.
so, I have to say 9.01.01 was better…ok, you had to click twice on the message win as well, but at least it found out the archive was corrupted, and the message would always pop up!
9.10.06: bug still there, unfortunately :(
W*nR** handles that properly, prompting about the archive being corrupted. -
9.10.06: bug still there, unfortunately :(
W*nR** handles that properly, prompting about the archive being corrupted.9.11.01: still no improvements about this bug…
-
9.11.01: still no improvements about this bug…
9.20.04…bug has not been solved yet :(
@spwolf…it’s annoying! why is it taking it so long…and you seemed to had solved it with the old 9.00.34 (read the first posts here…)
-
I am sorry, we just want to make sure we give it a proper testing, which is what only 9.5 can do…
thank you and I promise 9.5 will fix it!
-
I am sorry, we just want to make sure we give it a proper testing, which is what only 9.5 can do…
thank you and I promise 9.5 will fix it!
ok, thank you! :)
-
I am sorry, we just want to make sure we give it a proper testing, which is what only 9.5 can do…
thank you and I promise 9.5 will fix it!
you are a man of your word! ;)
In 9.5b4 the problem is gone, now no empty dirs are created for corrupted archives anymore! :)
