-
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. -
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).
-
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 :)
-
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.Features implemented:
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.
thank you!
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
76e97ab9-8d75-4175-9ce8-446500031f38-image.png
UNSOLVED Windows Explorer Dalay
-
Hi
I feel significant delay Opening Windows Explorer after each Windows restart after Installing PowerArchiver 2018.
Windows 10 x64
CPU: Intel i5 6600
RAM: 8 GB DDR4
SSD: Samsung 960 EVORegards
-
@shahin said in Windows Explorer Dalay:
Hi
I feel significant delay Opening Windows Explorer after each Windows restart after Installing PowerArchiver 2018.
Windows 10 x64
CPU: Intel i5 6600
RAM: 8 GB DDR4
SSD: Samsung 960 EVORegards
try uninstalling it and see if it helps. In general, it should not cause Windows Explorer to be slower unless you are right clicking on a file. It does not really matter what computer you have.
-
@shahin you can disable shell extensions by using shellexview:
https://www.nirsoft.net/utils/shexview.htmlOpen it up after install, find PowerArchiver and disable all of them. Then in Task Manager, right click on Windows Explorer and select Restart.
PA Shell should not show in the menu anymore.
Windows Explorer takes around 2s-3s on Win10 build that I have, but there is no difference if PA is enabled or disabled, nothing noticeable… I went ahead and disabled most of my shell extensions and is still seems slow.
Right clicking on archive is super fast though.
-
@Shahin i tested a bit more, disabled all 5 different compression utilities i have installed / their shells, and Explorer startup speed is the same 3s according to the stopwatch.
Check on your side, and lets see whats happening.
thanks.
-
Powerarchiver shell extension enabled about 1s 20ms, PowerArchiver shell extension disabled about 55ms.
WinRAR shell extension enabled about 80ms
WinZip shell extension enabled about 90ms
-
@shahin said in Windows Explorer Dalay:
Powerarchiver shell extension enabled about 1s 20ms, PowerArchiver shell extension disabled about 55ms.
WinRAR shell extension enabled about 80ms
WinZip shell extension enabled about 90ms
Is this for right click menu or for actual explorer.exe startup? It is interesting thats so fast for you and so slow for me, might be network drive.
-
It’s for actual Explorer.exe
yes, so fast, my drive is Samsung 960 EVO M.2
-
@shahin said in Windows Explorer Dalay:
It’s for actual Explorer.exe
yes, so fast, my drive is Samsung 960 EVO M.2
I have same ssd and 7700HQ :)
Now I envy you.
Can you try disabling various different PA extensions listed there and see how it affects speed? Maybe we can gain that 0.3s back. I cant really reproduce it here right now, there is no difference whatever I do.
thanks!
-
@shahin said in Windows Explorer Dalay:
Hi
I feel significant delay Opening Windows Explorer after each Windows restart after Installing PowerArchiver 2018.
Windows 10 x64
CPU: Intel i5 6600
RAM: 8 GB DDR4
SSD: Samsung 960 EVORegards
Are you using firmware 3B7QCXE7? If so its a know issue with the Samsung 960 EVO. More info below.
Really long thread, but worth the read.
Samsung 960 Pro -
@spwolf I’ll test ASAP
-
-
It’s hard to decide witch extension has the most impact
after long testing I think “Context Menu” “Context Menu 64” and Property Sheet" have the most impact on Explorer Opening Delay
