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.
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 errors
Is 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.
Crash at Exit with PA 10.2 Beta 2
PA 10.20.02 on XP x64
Open PA with an empty archive, close PA, boom
First-chance exception at 0x0049890f in POWERARC.EXE: 0xC0000005: Access violation reading location 0x1a000008.
according to VS 2005
I run windows XP Pro SP2 with the latest updates as of 2 weeks ago and installed the same PA Version but did not experience this issue??
Did you do an upgrade or a clean install??
try uninstalling the program, then delete the PowerArchiver Folder in Program Files. Reboot and re-install then to be safe restart again!
If it still happens then send an error report to PowerArchiver Support.
TBGBe last edited by
Open PA with an empty archive, close PA, boom
What is an empty archive ?
What archive format?
My mistake on the empty archive: it’s open PA without an archive loaded.
It was a clean install after a uninstallation of PA 10.2 Beta 1.
I already tried the reinstall/reboot Sir Richard suggested. Same problem.
If not already try this then (only if you know the registry)
1. Uninstall PowerArchiver 2006/07
2. Delete “Program Files/PowerArchiver” Folder
3. Delete Registry Link
then… if you have any registry cleaning software such as CCleaner or tune-up etc… do a full registry clean!
Restart then re-install…
If it still continues then it must be a fault with the program or something on your system is causing a conflict.
Tried the procedure but that did not help
However, I have more information:
the crash occurs only with the classic skin, not with the ribbon interface.
The Default blue skin works nicely.
I though it may have been Windowblinds causing the problem. I unloaded Windowblinds and run PA: with the Windows classic style, PA does not crash, with the Windows XP style, PA crashes.
That’s really odd.
TBGBe last edited by
Well, I have PowerArchiver :: Classic
Windows XP - Appearance XP Style / Color Silver
But no crash.
If you can reproduce it, provide/attach a DR Watson Log File (Zip).
Did I read the original post correct that you are using the 64bit version of XP or is it the 32?
I’m not able to reproduce, but I’m using the 32 bit, so maybe it is a 64 bit problem.
I think I reproduced the error… it ocured when I did the following
1. Open PA With Silver Default Ribbon
2. Change to Blue Default Ribbon
3. Change to silver default Ribbon
4. Change to classic
5. Change to Silver default
(I couldnt replicate it all the time only when I was clicking and changing skins like a mad man)
the errors are as follow’s (does it look familer?)
Yes, I am using XP x64. The errors reported by Sir Richard looks similar.
I will forward those results via your support page for you to look at!
Cheers crew, Vykranth Hopefully, this will support PA to amend the problem ready for the next release!
those are two different bugs - we are looking at 64bit one, already reported here while i will move sir richs to new thread…
p.s. devs on vacation until sunday, so expect new release in 6-7 days…thanks!
To be fair spywolf this is the 1st error I have personally experienced with PA in a long time!!
Looking forward to the next release, keep up the good work!
Please check with Beta 3 preview:
and let us know if it works properly now.
I don’t have the crash at exit I experienced intially.
I did have one crash when changing from the classic skin to the modern silver sking but I cannot reproduce it anymore.
I will try again later to see if I can reproduce it systematically.
Thank for the early preview. As Sir Richard said, it has been a very long time since I reported a problem in PA.
Keep up the good work