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
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.
Missing Explorer Shell entries PA 2021 20.00.56
W10 Pro 1909 64 bit
I admit I don’t often need to use the facility, but today I went to the right-click context in Windows Explorer, and found that none of the usual PA shell options, as set up and defined in Configuration>Shell (screenshot) were to be seen.
Looking at Sysinternals Autoruns, I notice that a couple of the PA shell context entries show a couple of DLLs PASHLEXT and PASHLEXT64 as missing (File Not found) - see screenshot. The highlighted error shows up for every occurrence of these files in the HKLM\Software\ shell keys.
Looking in Program Files \PowerArchiver, the files listed above are not present, but there are some similarly named (see screenshot). The files present are not very recently dated, but I feel that I have used the PA shell feature since their March 2020 dates. However, I cannot be sure of that.
Any advice welcome.
I’ve checked with 2021 and have set up the shell extensions in Config the same way you have, and they appeared fine when I right clicked a file.
How do they appear for you when you right click a file, with this setup?
@Mili They don’t appear at all I.e. there is no PA entry offered.
@Mili I’ve had another look through this, and note the following:-
there are no right-click Explorer shell options offered for any file types, and this includes PA archive files .pa and .zipx - see screenshots
I’ve looked at the file associations for PA in Windows settings, and they look OK.
when, after opening several archives in PA, exiting and then starting PA again, there are no recent files listed in the “Open” dropdown - see screenshot
When I updated from 20.00.55 to .56, the update process via PA crashed on every attempt. I thought this might be due to Bitdefender blocking it, but this is not so. In the end, I downloaded .56 from the website and installed it from there and, it seems to me, most if not all these problems have ensued since that update.
I am not sure what else may be problematic, but so far, on this system and .56, they are:-
- missing icons on the Backup file screen (as reported in another thread here)
- missing shell entries
- missing recent file entries on archive “Open” button
I’m making some progress with this.
I have re-downloaded .56 from the website and reinstalled it over the top of the existing .56.
I now have PA appearing as an Explorer right-click set of options, Autoruns and the Nirsoft applications now no longer show missing .dlls, and the previously-missing files PASHLEXT.DLL and PASHLEXT64.DLL from Program Files\PowerArchiver are now back there, with a date of 20-9-2020.
The conclusion therefore is that the first installation of .56 by downloaded .exe rather than through the PA built-in Patchbeam service was corrupt.
Although I’m not absolutely sure that the shell choices are working exactly as they should, and I wonder why the Configuration>Shell Extensions right hand “To” pane self-populates with an unremovable “PowerArchiver 2019” entry (this appears in my first Configuration screenshot above), they seem to have at least returned.
I am therefore left with two (so far) unresolved problems, which are:-
- non-appearing toolbar icons in the Backup Files and Folder screen (other thread)
- no recent archive files showing in the Open dropdown.
Not sure why I’m finding these as an end-user when previously I was finding bugs as a Tester, but never mind.
One last question. In the case where any application reinstall appears to be a solution to a problem, my normal instinct is to completely uninstall, notwithstanding the chore of setting up preferences and re-registering purchased software all over again. However, I have on this occasion reinstalled “over the top”, mainly because I don’t want any problems with re-registering and so forth. What in these circumstances do PA think the best route?
@PA_Fan This feels as if your AV has removed the file for testing and then later whitelisted it. What AV are you using?
Same installer is in both Patchbeam and website, as long as it is same version.
@spwolf It’s Bitdefender, and it did indeed interrupt a previous update, at which point I whitelisted PA, and all was well.
I don’t think it was the AV, and I’m still puzzled as to why the PASHLEXT/64 DLLs were absent in the program folder (and reported as missing in all the Shell utilities from Nirsoft and Sysinternals) when the program was first installed, but reappeared when I re-ran the instal and the Shell entries were then available. I’ve been through the Bitdefender logs and Quarantine, and those files are not mentioned or there, and the only explanation seems to be that the first install failed to complete 100% for some reason, but not the AV.
I have found the reason for the missing Recent files in the Open dropdown is that Private Mode was enabled under Options (toolbar). I don’t think I set it so, but reversing it fixes that particular thing.
I’m left (I think) with the missing icons in the Backup section. Here, I’ve tried several more permutations of icons and skins, but I still have square, blank icon boxes. Not a big problem, as the titles appear on hover, and more a cosmetic thing, but it would be good to see the icons as well.
We have the missing icons issue logged in and the devs will take a look to fix that. We will respond with further questions if needed.
Also, the Ribbon interface open button will not show an MRU menu at the moment. We have that logged in for implementation as well.
Thanks for all the information!
@Mili Thanks for the update, and you’re welcome.
I’ll wait to hear about the icons which, as I mentioned, I seem to recall having been a minor glitch in the past, but otherwise .56 is excellent.