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.
Dear @Alpha-Testers and all of our users,
time has come for testing of PowerArchiver and PACL for macOS.
Please let us know here if you have Mac and can test latest builds.
PowerArchiver 2020 - tabbing, opening, extracting, adding, testing, favorite folders, support for multiple languages, opening via Finder, explorer mode, installer.
PACL 10 - support for most formats and features in Windows version.
Upcoming: Tools such as archive converter, batch zip, multi-extract.
To start testing, please sign up here in this thread, and we will send you latest build.
Ashampoo_Snap_Wednesday, November 20, 2019_12h54m56s_008_.png Ashampoo_Snap_Wednesday, November 20, 2019_12h55m05s_009_.png Ashampoo_Snap_Wednesday, November 20, 2019_12h55m14s_010_.png Ashampoo_Snap_Wednesday, November 20, 2019_12h55m30s_011_.png Ashampoo_Snap_Wednesday, November 20, 2019_12h55m39s_012_.png Ashampoo_Snap_Wednesday, November 20, 2019_12h55m49s_013_.png Ashampoo_Snap_Wednesday, November 20, 2019_12h56m00s_014_.png Ashampoo_Snap_Wednesday, November 20, 2019_12h54m43s_007_.png
There is a CRC error on file-Rar container
I have been using PowerArc since 8.00. With the change in activation codes I procrastinated until now (Because it was working perfectly) to update from 9.26 to 10.01 last week. I could not get it to work. Today I ran Update, so I’m running 10.10.10 now. I primarily work with large Rar files and small zips.
Whenever I click on a file in an Archive, it says “There is a CRC error on file: D:\WinTemp_PA###\filename.ext” Volume … And it always lists the last rar file in the set. Continue Yes/No. (Of course it will say the actual temp file number and file name which changes each time.) And when its done, it leave partial directory names in the same directory as the rar files.
I can still do a right-click, extract here, or a extract full to xxx, or partial. It seems to be the Preview process I am having trouble with.
I have worked with these same files previously with 9.26 no problems. The files have par2 files and are confirmed still good.
Edit: And… I haven’t looked too hard at the queue function yet, but if I open 2 instances of Powerarc, I get a low GDI Resource warning from Norton System Doctor. I used to be able to run 8 to 10 instances before I got that warning in the past.
are you using classic or modern view?
I am not sure we changed this from past behaviour (opening files inside of MV rars), but we will check it out and let you know.
p.s. you got new codes, right?
I’m using Classic, Explorer style. I tried switching to modern, and the first set worked perfectly. But the same set tried again gave me the same error.
I don’t know if any of this will help; I am opening the Rars and Zips from Windows Explorer. I tried disabling Queue and Quick launch, no difference. The upgrade picked up all the configuration settings from my previous version except the “Default Checkout Directory” which defaulted to c:\program files\ instead of the Windows temp directory, which I have set to D:\wintemp rather than c:\windows\temp. This is System wide, not just for PA. When I launch PA the first time after a reboot, I now receive a warning that GDI resources are down to 9% with one instance open THE FIRST time. Subsequent rar opens do not generate this warning, but GDI resources remain a little low at about 53% with PA closed and 23%-28% when its open. Both times I ran the Installer, it told me I was missing two components, but it would only download the 2nd item, GDI 1.0 something I believe. I am running Win98SE on a fully patched (With the new Unofficial Windows 98SE Update Patches) system with 1gig of Mem configured down to 980 megs. Multiple EIDE drives, some over 250GB for a total of 1.2TB on a total of 8 volumes, nVidia video, Avira Antivirus, AMD Athlon 2.4ghz, Asus A7N8X Mobo.
I did re-receive the new codes. The date on the 10.01 install file is 04/03/2007, so I must have done it then. If you’re looking for my Registration, it is under this same email address. For a while, you guys were sending me the Beta versions to try.
I ran into the same problem today. Using most current version, modern skin, explorer view. I was dragging and dropping and had a problem. Right clicking on the archive and saying extract here gave me no problems.
Well, I was hoping this was some “standard” issue. Please don’t spend any more time on this, since I’m using an obsolete OS, and I have a non-standard Windows temp file configuration. I’ve reinstalled 9.26 and it’s working great. Feel free to delete this thread. Thank You.
we will check it out for next release… thanks