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.
PAOP: Files not being compressed
For some reason PAOP does not compress the files even though I explicitly tell it to do so.
Windows XP SP2
What could be the problem?
what settings do you have for compression and what type of file is it? did you check file filters?
Compression Format: ZIP
Compression Level: Maximum
AES Encryption: No
Rename Ext to .??_ No
Compress & Encrypt: No
Minimal File Size: 10kb
Excluded Extionsion: None
Include Help File: No
Name based on firth attachment: No
Ask to use PAOP before sending: Yes
I’m trying to compress and Excel file (.xls) of 20.5kb
did you check filters to make sure xls isnt there?
Yes, and it wasn’t there. I even went so far as to clear the exclusion list completely.
whats the name of the file? maybe thats why it wont work… did you try some other file?
I’ve had the same problem with numerous files. Perhaps having white-spaces in the name might be causing problems?
I’ve also uninstalled and re-installed PAOP countless times.
let me know of the filenames that you are having issues with and we will try to replicate it here…
I’ve tried all manner of file names, extensions and settings, but I still can’t get PAOP to work.
I think I’ll just uninstall it.
hm, i tried xls with space in the name and it worked fine…
Do you get compress window when you send files with attachments or?
Yes, the compression window does open, but almost immediately closes again.
so it closes without you pressing anything?
Yes, that is correct.
Before I send you on a wild goose chase, let me rephrase that.
When the setting is ticked for POAP to ask if it should zip the attachments, the compression window opens up, and stays there until a selection is made. But even if one chooses to zip the attachments, it almost immediately closes without doing anything.
When it is set to zip attachments automatically, one can see the compression window open and close almost immediately.
I honestly don’t know how one would troubleshoot this problem, since it seems to have worked perfectly well in all your tests.
Do you at any point of time see PA window (not PAOP but PA)?
If not, please let me know what is the path to PA and PAOP instalation, it seems as if PAOP isnt calling PA for whatever reason.
Also, what other plugins for office do you have installed?
I have the same issue with Outlook 2003. I even have the plug-in to prompt me on every email if I would like to compress the attachment(s). I answer yes and it appears something is happening, but the message is sent without the attachment now as a zip file.
I do have other Outlook plug-ins installed such as Mapilabs duplicates remover. I am also using Spysweeper with Antivirus v5.5.7. Not sure if these could be causing an issue.
Is there a way to activate a debugging feature to possibly see where the problem is happening? I have reinstalled the plugin, and verified the outlook plugin options multiple times.
when you say that something is happening, does that mean that PA 2007 launches or?
To make it easier to explain, I captured a video of the process. I have posted the AVI on my website:
-The video is about 9megs in size. You’ll see exactly what I am seeing.
It’s been a couple of days. Any ideas of why it doesn’t work?
we are working on finalizing 10.20, so in few days we will have time to look at PAOP… thanks.
Have the same problem here.
New windows instalation with:
Outlook 2003 SP2 11.8118.8132
MS Proofing Tools
Windows XP 5.1.2600 SP2 Build 2600
I have been having this problem for a while and I have formatted my machine a installed the latest versions of PAOP and PA in order to see if the problem would be solved, but it didn´t. The PAOP 1.10 worked fine on my machine. Do you know if there is anyplace I can download the old version?
we will take an look at this this week, so please patient… we will need more info for sure.
Found the 1.10 version in PA´s download site.
Uninstalled the 2.0 version, installed 1.10 and it works fine.
I´ll be waiting for a new version.
Here is what we need to know:
1. location of your temp folder
2. Send us paarcce.dat from your temp folder.
You can send it to support conexware.com.
Important - the parcce.dat must be the one that is created after reproducing the bug (creating new email message, adding attachment, clicking on “Compress” in PAOP dialog that shows upon “Send” action, and after loading/closing PA).
two things to ask what version of outlook are you using and what windows are you using. the second thing is to ask have you installed any other outlook plugin or have you reinstalled outlook after installing this plugin. i would suggest uniunstalling pa and outlook and pa and then install outllok then pa then this plugin and tell us what problems you encounter after that.
Windows XP Professional
Build 2600.xpsp_sp2_gdr.070227-2254 (Service Pack 2)
Microsoft Office Outlook 2003 (11.8169.8172) SP3
Formatted my computer, installed Windows XP, Updated (Windows update), installed Office 2003, updated. Using a MSExchange connection.
The older version works fine. The newer doesn´t.
Couldn´t find the parcce.dat file.
check this out:
it should fix the issue. Please report back if it did.