-
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.
-
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. -
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
-
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.
FTP from shell = high CPU usage
-
Hello,
I registered on the forum to report a couple of problems I’ve been having with Powerarchiver 2012 Professional.
I am glad to see that the first problem has already been taken care of, namely, the hanging of PASTARTER.EXE introduced with 13.01.03 - fixed in 13.01.04.
The second problem is high CPU usage when using “FTP It…” shell extension. I made a few PA backup scripts which make encrypted 7z archives, copy these archives to two other locations (nice feature), and then FTP these archives to a remote FTP server (another nice feature). All is well, with regard to CPU usage, when PABackup.exe is doing the FTP file transfer, but when I right-click a file and click an FTP profile the CPU usage of POWERARC.EXE doing the file transfer goes way up - maxing out a core if I set process affinity to just one core. I cannot tell you when this problem started since I have not been using this feature for long, and I only noticed this summer due to high revving CPU fan.
Hopefuly this is something that can be fixed in a future release.
Best regards,
iDunk
-
Hello,
I registered on the forum to report a couple of problems I’ve been having with Powerarchiver 2012 Professional.
I am glad to see that the first problem has already been taken care of, namely, the hanging of PASTARTER.EXE introduced with 13.01.03 - fixed in 13.01.04.
The second problem is high CPU usage when using “FTP It…” shell extension. I made a few PA backup scripts which make encrypted 7z archives, copy these archives to two other locations (nice feature), and then FTP these archives to a remote FTP server (another nice feature). All is well, with regard to CPU usage, when PABackup.exe is doing the FTP file transfer, but when I right-click a file and click an FTP profile the CPU usage of POWERARC.EXE doing the file transfer goes way up - maxing out a core if I set process affinity to just one core. I cannot tell you when this problem started since I have not been using this feature for long, and I only noticed this summer due to high revving CPU fan.
Hopefuly this is something that can be fixed in a future release.
Best regards,
iDunk
thanks a lot, we will try to reproduce it and let you know if we have any questions.
Does the actual FTP upload finish?
-
thanks a lot, we will try to reproduce it and let you know if we have any questions.
Does the actual FTP upload finish?
Yes, the upload always finishes ok. Process Explorer shows a high cycles delta at offset 0x875470, if that is of any help.
System info: Windows 7 Pro, Core i5 750, 8GB RAM, latest NIC driver
Antivirus is Kaspersky Internet Security 2013 (happened also with 2012). I think I can exclude the antivirus/firewall as the culprit since all Conexware programs are in the trusted group and yet pabackup.exe and powerarc.exe behave differenty doing FTP. -
ok, sounds good… we will let you know when our testing goes though it… if we can reproduce it, it will probably be fixed in next release (few weeks).
-
I was able to reproduce this and have logged it in.
thanks for the detailed report! -
I was able to reproduce this and have logged it in.
thanks for the detailed report!Hi,
I’m a new user of PowerArchiver and I’m experiencing this too however I’m not activating any extensions - I performed a clean install on two computers, and both frequently go to 50 - 51% CPU usage. Windows 8 on both machines.
Any suggestions?
Thanks.
-
Hi,
I’m a new user of PowerArchiver and I’m experiencing this too however I’m not activating any extensions - I performed a clean install on two computers, and both frequently go to 50 - 51% CPU usage. Windows 8 on both machines.
Any suggestions?
Thanks.
disable pa starter from starting, it is issue that was solved in last release. Ctrl-alt-del and kill pastarter.exe process.
pastarter was not compatible with win8 so we had to rewrite it completely. You can disable its startup in Options> Configuration> PA Queue.
-
disable pa starter from starting, it is issue that was solved in last release. Ctrl-alt-del and kill pastarter.exe process.
pastarter was not compatible with win8 so we had to rewrite it completely. You can disable its startup in Options> Configuration> PA Queue.
Thanks, I’ll give that a shot!
-
High CPU usage with FTPit still present in 13.03.01 and 13.03.02 :(
-
thank you, we got stuck on 2013 for a while, but now we are good to go.
-
The problem is still present in 14.0.17.0.
-
Any chance of fixing this in 2013 final?
-
aaaaaa!
will check it out this week, final or no final.
-
Hi!
Sooo, is there a chance of this ever getting fixed? I just tried with 15.0.35 and the same problem is present, as always. FTP it… shell extension maxes out a core. Shame, such a nice little feature but not really usable for large files, mostly for power issues.
Thanks
-
I will check with team whats going on here.
-
I have ample CPU, so it does not create a problem for me.
I can verify CPU usage spikes (goes from 1-2% to 25%).
With FileZilla, it never moves my CPU about 2%.
I think, though, that the problem is more general than FTP. Just compressing a folder from the shell jacks my CPU up to almost 25%.
And . . . Compressing a folder from within the PA main window gets the CPU to 29%! Maybe it is the nature of multi-core compression. Not sure.
-
there was a specific problem with ftp where cpu would spike with no reason.
For ZIP compression, it is best to use all of the cpu :-) -
Yes, compression will do that to a cpu ;) But we are talking about ftp file transfers here. Something which should not task a cpu so much.
-
Tested with the newest RC 2015 and putting on the list for the dev team to check out for the next update.
Thanks for bringing it up :)