-
PA2023 Win10, (same problem with older releases but never reported)
PA Soft is installed on partition D. (exclusive for installed progs)
Then I created on my partition G: the folders as configured in PA Settings ‘Folders’.0fcf1b09-1b91-4b74-b250-f8cf908a3348-Ashampoo_Snap_maandag 20 maart 2023_11h54m34s.png
Screenshot 2023-03-20 121152.png
The problem : Any activity on PA is saved in these folders…
PA ignores them and still use the default settings. Whats wrong ? Regards, Pirrbe -
I am still using Powerarchiver 2022 and it does not show pdf markups in the preview. Is there a setting to get version 2022 to show pdf markups in the preview? If not, does this work in version 2023?
-
The question that I have about PA archives is what happens if say ConeXware, as a company, dies in the future? What happens to any PA files that are created today? Can these files be decompressed with a copy of a PowerArchiver that can no longer phone home to the mothership thus can’t be registered or activated?
I mean, I can understand that new PA files wouldn’t be able to be created if the program isn’t registered but what about an un-registered copy because well, the question that I posed above?
It’s questions like this that make me not want to store anything really valuable in PA files out of fear that I, at some point in the future, might lose access to said data inside those files. OK, 7ZIP might not be able to compress as heavily as PA but at least it’s open source and any 7ZIP files will still be able to be read and decompressed ten, twenty, or fifty years from now.
-
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.
-
Is this a known problem? Is there a fix coming? This is a primary reason I buy PA.
I’ve tried both methods I know to extract multiple zips at the same time. 1) Multi Extract feature in the GUI. 2) In Windows File Explorer, select multiple zips, right click, use PA context menu to Extract or Extract To…
Is there a setting I missed? Or maybe it really is processing in parallel, but I can’t detect it? Nothing tells me in the Processes in Task Manager that multiple PA extracts are running. And my CPU, memory and disk resources do not look like a lot of extracts are running.
I’m using PA 2022 Standard version 21.00.18 on Windows 11 Pro version 10.0.22621 Build 22621.
-
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 -
Hi there, been a user since 13 years now and in past whenever I had a problem or question I could email, however since 3 weeks it seems like everybody is dead?
Anyway, as kind of a last resort, I post this email a 4th time but in this forum instead now, in the hope for help:
"This is the 3rd time I am emailing you guys as I am missing a working code for the preview of Power Archiver 2023Can you please help me? I am a 13 years lasting customer of yours, and I am shocked thatr for whatever reason my support tickets are ignored now, why?
thanks in advance!
All the best!
Joerg" -
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).
-
-
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.
UNSOLVED Power Archiver Starter - CPU and power overhead
-
I’m running PA 21.00.17 64-bit on a 64-bit i7 desktop with W10 Pro, latest version. This 32gb of installed RAM.
As I use the PA pbs system for a number of scheduled archiving operations throughout the day, PA Starter is set to load and run at system startup.
In the course of trying to identify some causes of slowness and bottlenecks in other processes, I notice that PA Starter (PAS) always runs at between 11% and 15% of CPU (see screenshot), usually at about 12-13%. This is by far the highest demanding process on the system, as shown by Task Manager. In Performance Monitor, PAS Average CPU is 8.32, with every other process at less that 1 i.e. in decimal places only.
Task Manager also shows PAS Power Usage as “Very High”, and is the only process shown thus.
I have looked again at the information about PAS at https://wiki.powerarchiver.com/en:help:details:powerarchiver_starter, which was last modified in 2016. The article states a low memory usage for PAS of 784k, which is fair enough, but it is the large CPU overhead which is of concern.
It is of course possible to change the PAS priority, but this has no effect on CPU overhead.
However, is it possible to change PAS, which is required only at intervals to initiate PA scheduled tasks, from consuming so much system resource for every moment of the day?
-
@pa_fan Something is very wrong.
The whole of PA should use only a totally negligible amount of CPU when it’s not compressing or un-compressing. -
@brian-gregory Thanks.
PA itself, when running but not doing anything, has almost no CPU overhead.
PA Backup, when running a scheduled (or ad hoc) backup compression job, uses anything between 10% and 25% of CPU when working on a .zipx file. Obviously this will change with the compression type and level specified for the job, and the CPU overhead goes up and down. I think it’s a good thing that PAB uses what it needs to finish the job ASAP, and of course, running these various backups is an intermittent thing, which I schedule for times when my system isn’t heavily loaded with, for example, a Macrium Image Backup and Verify. So no problem there, as far as I can see.
However, PA Starter loads at system startup, and runs with this CPU loading level all the time, until system shutdown. As I understand, its purpose is to manage PA backups, and I guess it interacts with Windows Task Scheduler, where the various scheduled .pbs jobs are listed. In itself, that’s a necessary interface with the OS, and one which requires the PAS job to sit in the background until its called upon to handle a .pbs. My concern is that a background, watching/waiting process constantly consumes this amount of resource.
I should add that I recall raising this some while ago, but various changes to this system and the applications I’m running on it mean that that I’d like to try to squeeze a bit more performance out of it.
-
@pa_fan can you export and send to support at conexware.com your hkcu\software\powerarchiverint settings.
Seems like starter is stuck on something, we would like to reproduce and fix it in next release.
It should never take that much cpu time, it checks registry for new tasks every xx seconds, but that is not cpu intensive and it should be showing 0% otherwise.
-
Additionally, backup tasks should be set via task scheduler.
Starter usually runs waiting for queue tasks.
-
@spwolf Re: registryI’ll do that.
Re: Task Scheduler. All backups I have created and scheduled are listed in Task Scheduler. There is a curiosity, in that a .pbs appears in TS, but not in the pbs list in PA, and isn’t in the folder where I store all pbs files (the location of which is that shown for the job in TS). All very odd.
Am I correct in thinking that pbs scheduled jobs, which appear in the pbs list and on TS, but are not ticked for Queue under Scheduling Options must still have PA Starter enabled and running, or they won’t work? In other words, even if they appear as scheduled tasks in TS, they won’t start without PAS running in background.
Obviously I can test this by turning off PAS and seeing if the tasks due to run will actually do so, but I can’t do this right at this moment.
I have 7 running applications (Firefox, Tbird, FreeCommander etc.), with about 15% CPU, of which PA Starter is about 12.5%.
-
@PA_Fan no, task scheduler starts pab, not pas.
Pas is used just for queue in this case, turn off the queue and disable pas in pas systray settings, and you will be fine.
-
@spwolf Thanks.
That’s working fine, and scheduled jobs are running as required. As I mentioned in a previous post in this thread, my .pbs scheduled jobs are timed to run when other system jobs, like Macrium Reflect image backups, aren’t due or running; and vice versa.
However, I can see a situation in which I would want to use PA Queue, and thus need to run PA Starter, and I don’t think we yet have an answer, as to why PAS grabs so much CPU. I have previously used ProcessExplorer to lower the PAS priority, but this doesn’t appear to make any difference.