-
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 :)
Error when using shell extensions and Total Commander
-
I’m using PowerArchiver since years and never had problems with this. Actually I’m using PA2011 with Windows 7 Home Premium x64.
Now I bought the program Total Commander and every time I rightclick on a file or a folder Total Commander is crashing down.
With ShellExView I tried to disable all shell extensions which are not from Microsoft. So Total Commander did not crash any more. But after enabling the shell extensions from PowerArchiver Total Commander crashes down when right clicking.
Is there any possibility to fix the shell extensions so that Total Commander works without crashing down?
-
is TC 32bit or 64bit? Problem might be our 64bit shell extension then?
-
ok, so I tried:
PA 2011 12.01.03 Int
TC 7.56aon Win7 64bit.
All works fine… both 32bit and 64bit shell ext work fine, and even UAC elevation works as advertised.
Maybe you are using different version of TC or PA? If not, maybe some PA setting is different? Send us your settings via Options> Save (7z first), to support at conexware dot com and refference this thread…
thanks!
-
I’m using TC 8.0 beta 7 x64 with PA 2011 12.01.02 GER.
Saved my options, zipped the reg file and sent this to you…
Best regards,
PoooMukkel -
did you try reporting this to them? This seems to be the issue with their 64bit TC that just came out. Same PA works fine in their official release.
Keep in mind that this is first release of Delphi 64bit, so these issues will arise.
-
Yes, I reported this to them. But they said that it must be a shell extension which works not correctly. So they put me to ShellExView and I disabled all of the non-Microsoft extensions. Then I enabled them one by one and tested with TC.
-
it worked fine in 7.65a, it works fine in Explorer… just doesnt work in their betas and new 64bit code :-).
-
Ok… That’s a fact… ;)
By the way I tested WinRAR and their shell extension works fine with the beta of TC.
I don’t know what to do now. I asked again in the forum from TC. Hopefully there will be a fix. :(
-
Ok… That’s a fact… ;)
By the way I tested WinRAR and their shell extension works fine with the beta of TC.
I don’t know what to do now. I asked again in the forum from TC. Hopefully there will be a fix. :(
tell them it works fine in official release, just not in their new 64bit release, and that works fine in x64 Explorer.
-
Okay, I will try…
-
anything?
-
Sorry for letting you wait…
I asked the support from Total Commander. TC is only using 1 function for shell extensions. The rest is made by Windows. So they are not able to help. :(
But they showed me some workarounds for the problem. One is to use the x86 version of TC. Then it will work. Or using the x86 shell extension from PowerArchiver should also work. But I don’t know how to use the x86 shell extensions because I don’t have the possibility to install x86 version of PA on x64 system.
May be you can do something in one of your next versions with the shell extensions? That would be great. :)
-
did you have any luck with this?
-
No, I didn’t have. I’m waiting for another version of PowerArchiver. Hopefully the shell extensions will work then… ;)
-
you can unregister x64 bit shell extensions, will that work?
-
What does that mean? And how can I do that?
-
I don’t know, how to unregister x64 shell extensions…
Installed PowerArchiver 2011 V12.10 but shell extensions still not work with Total Commander 8 Beta x64. :(
-
Go to cmd.exe
and run:
regsvr32 /u PASHLEXT64.DLLit will unregister 64bit shell extensions!
-
That does not work. There appears an error which I only have in German.
[Window Title]
RegSvr32[Content]
Fehler beim Laden des Moduls “PASHLEXT64.DLL”.Stellen Sie sicher, dass die Binärdatei am angegebenen Pfad gespeichert ist, oder debuggen Sie die Datei, um Probleme mit der binären Datei oder abhängigen DLL-Dateien auszuschließen.
Das angegebene Modul wurde nicht gefunden.
-
you need to navigate to PA folder first, or else specify the path before… like C:\program files (x86)\powerarchiver\pashlext64.dll
-
After that there are no shell extensions from PowerArchiver available although I checked the box in the settings. :(
-
but you should have 32bit ones in TC? PA installs both x86 and x64 shell extensions.
-
No. There are no extensions from PA after that.
-
run this:
%windir%\SysWOW64\explorer.exe /separate, /root, c:
do you see PA shell there now?
-
Still no shell extensions from PA.
-
May be did you change something in PA2011 12.11 to solve this problem for me? ;)
-
No… It still does not work. :(
-
PoooMukkel,
Sent you a PM :)
-
bumping this thread again, should be fixed in .22
let us know
