-
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.
-
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).
-
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. -
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 :)
Shell extensions not working, solution: reinstall and reboot.
-
if you have a spanned zip archive ending in a letter like e.g tersta and then next one terstb the problem sayes there is an error and locks up so you have to crash powerarchiver.
when will a fix be avaliable. in teh archives are more spanned zips which need to be extracted before i can extract them, this time the spanned zips insode the archives have 001 when will a fix be avaliable as this is an urgent problem
the archives with 001 etc can not be extracted via powerarchivers shell extensions but can be opened and installed which is not a problem but why is shell extensuiosn not working the files are.
attached is the screen shot i get when trying to extract these files via the shell extensions. i have windows 2000
-
When I right click to use the feature extract to directory
I get the pop up message saying unspecified error
Then I get a blank dialogue box saying
corelbutton1 - pause - cancelbutt
The PA program is great, but if the small bug can be fixed, it will be better.
Thank You
-
you need uninstall PA 2009 reboot your computer and install it again, and reboot again :-).
It seems as if PowerArchiver dll’s are not properly registered on your computer.
thanks!
-
can you please write exact filenames that are creating the issue so we can take an look? Hard to understand from the post… thank you!
-
I have the same problem with spanned rar archives, if I R-Click on the first archive and select (extract to…) I get an (unspecified error) then the same popup as illustrated above, if I click on corelbutton it shrinks to the task bar If I click cancel another box opens with Archive interrupted continue?, If I select YES I get into an eternal loop if select NO power archiver ends. But if I open power Archiver from it’s icon I can search for the first rar file and every thing works OK. I am using PA 11.03.04 with Vista 32
-
duckndive - i believe thats the problem due to not properly registered dll’s with PowerArchiver.
Did you reboot your computryer after installation? If not, try doing it now.
If it still does not work:
1. uninstall PA
2. Reboot PC
3. Install PA againthat should make sure it is installed properly.
-
david is probably having the same issue…
-
We changed in 11.03 the way our installation works, and are not allowing it to crash explorer.exe in order to install PA (which is what Windows Installer does by default), because we found out that sometimes, due to some unspecified Vista bug, Explorer.exe would not restart, so newbie users would not know what happened - they would only see black screen and didnt know how to restart explorer.exe manually.
I am seeing same thing in Windows 7 right now so not sure how will that get solved as it is Microsoft issue (Restart Manager and Explorer.exe).
-
spwolf- thanks for your quick reply
I have had PA installed now for several month’s, so restart was not one of the problems, I will as you suggest uninstall and re-install and report the results. Has Kaspersky Internet Security any relation to this problem, I get a lot of pop-ups telling me how Kaspersky is treating various files and DLL’s and what category they represent.
Again thanks for all the help. -
let us know what happens… does it only happen when you try to extract rar files, or anything you do with shell extensions?
-
you reproduce it using my steps ibn my first post.
though one thought came to mind the spanning of these archives causes powerarchiver problems coulsd it be the engine pa uses.
Are these spanned archives actually spanned archives as sorry to mention it winzip can not touch them either but pa can of sorts if you only open they from within pa
The error produced in future shouls show an error number so you can pinpoint the problem area of the fault.
-
i need specific filenames from you david, or i cant try to reproduce it… also does anything else in shell work for you?
-
All OK now, uninstalled and re-installed after a restart, works perfectly, had one problem with PA Starter, which would not close down for the uninstall, had to go to task manager and force it to stop.
Thanks for all the support spwolf, ( I always feel uncomfortable thanking with any feeling to a forum profile).:(
Richard:D -
All OK now, uninstalled and re-installed after a restart, works perfectly, had one problem with PA Starter, which would not close down for the uninstall, had to go to task manager and force it to stop.
Thanks for all the support spwolf, ( I always feel uncomfortable thanking with any feeling to a forum profile).:(
Richard:Dnp, drazen :-)
-
Thank you Drazen
Hvala -
if you have a spanned zip archive ending in a letter like e.g tersta and then next one terstb the problem sayes there is an error and locks up so you have to crash powerarchiver.
…
you reproduce it using my steps in my first post.Well, I don’t have any spanned archives using that naming method.
If I assume they are spanned zips, how are they named
a) tersta.zip; terstb.zip etc
b) tersta.001; terstb.002 etc
b) tersta.zip.001; terstb.zip.002 etcor what?
@davidsplash:… in teh archives are more spanned zips which need to be extracted before i can extract them, this time the spanned zips insode the archives have 001 …
Actually, are you sure the ‘a’, ‘b’ … files are spanned zips and not just split files (using e.g. HJSPLIT or similar)?
-
well not sure if they are split files but split files ca made with HJSPLIT can not be opened by pa so i assume they are not. iF they are how comes powerarchiver lists them as archives when other compression programs don’t
-
-
nema grešaka:cool:
-
The same results happened as my spanned archive posting the zip file in question is 134mb and when i try to extract it i get an yun specified error message
so i ran a test on the zip file from within powerarchiver and obtained these results
Done. – 25/01/2009 14:34
There were no errors in the archive: TEST.zipThe file in the archive are a setup, txt file, windows.link file
i’m using windows 2000
they can be extracted only from the main powerarchiver windows indicating a shell extension bug
-
i already wrote what the solution is… you need to reinstall PA and reboot your computer.
none of your shell extensions will work until you do that.
-
seems to be fixed for shell extensions on zip archives using extract to here option. though i stress too many people have had this fault. So is there going to be safe guards against this happening in the future?
-
:-)
-
safeguard would be that when it tells you to restart, it means it.
-
true but it didn’t not even on uninstalling and reinstalling did it mention this. So this needs to be rectified.
Also even after a restart this happened only after i decided to unistall and restart delete all reg entries of powerarchiver restart and then install restart did it work. what does that say.
