-
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).
-
-
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 :)
Could not upgrade to PA 9.6 beta 1 (9.6.0.8)
-
I upgraded from my previously 9.51
rebooted, and that’s what happens when I call the program (I’m Italian, so errors are in my language):and then
I’m now going to uninstall it then reinstall the last beta, to see what happens.
I’m writing here because it’s really the 1st time I’ve experienced a problem when upgrading PA :(
-
I saw the second error (interface not registered) after updating a PA 9.51 to PA 9.60b1 - but I had not rebooted.
After rebooting, PA 9.60b1 is working fine.
-
I saw the second error (interface not registered) after updating a PA 9.51 to PA 9.60b1 - but I had not rebooted.
After rebooting, PA 9.60b1 is working fine.
That seems to be a problem with the dll which implements the Explorer (shell) options - it is replaced and a reboot is needed.
Not sure about “manuangi’s” first problem. Was the previous version (9.51) using a different skin (non-default) perhaps?
As a “general rule” I would not advise << upgrading >> to a ‘beta’ version of any software. I always do a clean install (uninstall previous/reboot/install ‘beta’).
Still feedback that there was a problem is useful.
-
definetly an old skin. We have to be able to handle that better.
thanks!
-
I saw the second error (interface not registered) after updating a PA 9.51 to PA 9.60b1 - but I had not rebooted.
After rebooting, PA 9.60b1 is working fine.
what OS are you using?
-
definetly an old skin. We have to be able to handle that better.
thanks!
yea, I was using the “bunnies” skin that I love so much :)
so, spwolf, what’s your advice about how to proceed?
thank you
-
try deleting the skin that you were using? If not, you can uninstall it and install it again, which will delete the registry keys…
thanks!
p.s. what OS?
-
try deleting the skin that you were using? If not, you can uninstall it and install it again, which will delete the registry keys…
thanks!
ok…but I really loved the bunny-skin :(
p.s. what OS?
WinXP SP1
-
I think restart is the most important step here, so please restart your computer when installation tells you so!
thanks,
-
I always did, if you read my previous posts.
anyway, uninstalling/reinstalling PA did the trick
can I apply my bunny skin again, or you think there could be problems?
-
skinning engine is completly new, only toolbars will work (complete skin wont)…
-
what OS are you using?
WinXP SP2.
Note that I did not consider the error message I saw to be a bug - the update told me that I had to reboot, but I generally ignore those messages unless I run into problems because reboots are often not really necessary for many products - the install process is just being overly conservative.
However, if you can workaround the need to reboot, obviously that would be a plus!
-
WinXP SP2.
Note that I did not consider the error message I saw to be a bug - the update told me that I had to reboot, but I generally ignore those messages unless I run into problems because reboots are often not really necessary for many products - the install process is just being overly conservative.
However, if you can workaround the need to reboot, obviously that would be a plus!
Did you install PA in same folder as before or in new folder? Did you keep old version installed?
I noticed one case where installer would not register skin dlls until reboot, but in that case PA would have tell you that you cant install until reboot and you would have to delete your registry key for pending renames, which is probably not what you did?
thanks,
-
Did you install PA in same folder as before or in new folder? Did you keep old version installed?
I noticed one case where installer would not register skin dlls until reboot, but in that case PA would have tell you that you cant install until reboot and you would have to delete your registry key for pending renames, which is probably not what you did?
thanks,
I just installed the beta over the existing install (I’m wreckless sometimes). No problems - it told me to reboot, but I didn’t (wreckless…) and it gave the interface registration error when I tried to start PA. After a reboot I tried again, and everything is working fine.
-
… can I apply my bunny skin again, or you think there could be problems?
Not sure what “bunny skin” is.
If you mean “Rabbit XP” then that is a toolbar and not a skin, so…
@spwolf:skinning engine is completly new, only toolbars will work (complete skin wont)…
Maybe? {Can’t try it myself at moment sorry… }
-
Not sure what “bunny skin” is.
If you mean “Rabbit XP” then that is a toolbar and not a skin, so…skinning engine is completly new, only toolbars will work (complete skin wont)…
Nope.
Doesn’t work - or at least I cannot see how to apply the “old” toolbar button “skins”. :confused: -
Config> Skins & Toolbar :-).
-
Config> Skins & Toolbar :-).
:o I was trying via
Options - Skins …
Skins(right click) …
Select Buttons …Missed the Config settings :o
OK it does work.