Hello, I used the support form to ask this a couple weeks ago but never received a response. Perhaps here would be better? Here’s the issue:
Powerarchiver 2019 was locking up testing a .7z file so I looked for and found a new version (note- new version didn’t fix this- I ended up using 7-Zip itself. Archive was large and contained a ton of files)
Upon installing it, I was prompted to register it or “continue unregistered” so I logged into the website and used the order recovery option to get my new codes for PA2021. However, after cutting and pasting my name and registration code, upon restart when I click on the help button it still shows as unregistered (it did not show the nag dialog again). I tried two different codes (see below). I also tried installing again using the link in the email but there was no difference. Where do I go from here? Thanks.
Update: After a couple weeks it still hasn’t negged me, but continues to show as unregistered in the (?) area- will this stop working altogether soon?
OS: Windows 10 Pro version 2004
File installed: first used PA 2019 to check for and install update, then used link in email which downloaded powarc200073.exe and installed that.
Codes used: first tried the toolbox/english code in first email, then tried the standard/international code in second email
I hope that despite my poor control of English, you can understand me.
When compressing a file, by default the extension is included as part of the file name. for example, if the file is name.pdf, the compressed file will be name_pdf.zip.
Is there any way for the extensions not to be included in the compressed file name? As much as I have searched I don’t see such an option.
Thanks for your time
I’m using Convert Archives on a local folder of .zip files, converting them to .lzh files, and I’m finding that perhaps 1 in 75 files is actually converting and outputting a file. Even then, the .lzh file is incomplete, missing most of the source files.
The progress bars completes OK, say 75/75 files, but only one .lzh file exists in the output folder.
It seems to be the same with different source and output folders on both local and USB disk - I can’t see a pattern.
The files extract and compress (to .lzh) without issue on their own.
Is there a log file I can check please, to see why PA does not like these files as part of the batch conversion?
Thanks very much, Rich.
I’m experiencing very slow extraction speed of multipart RAR files. For the first part the extraction is super fast but when PA reaches the part2.rar the extraction from there on gets super slow. PA needed for a 6,3 GB multipart archive 30 minutes to extract. I tested then with another program and it just took 70 seconds. I had this slow extraction speed with PA for quite a long time and I always thought that is maybe because of a high compression rate that the extraction would take longer. But it seems that only PA gets that slow.
I have lots of multipart archives that are 10+ GB and with PA it would be really time consuming. Is there any solution to this?
I have powerarchiver licenses for powerarchiver standard and toolbox (and also as a result for pro).
I can successfully register powerarchiver with my pro/toolbox codes, and it unlocks the majority of the content/features. However if I try and create a .pa style archive I get the registration popup saying I need PowerArchiver Pro (if I go to help/about I can verify I have the relevant version and it’s registered to me).
Powerarchiver 2021 20.00.73
Windows 10 Education 10.0.19042 Build 19042
When extracting gcc-arm-10.2-2020.11-mingw-w64-i686-arm-none-linux-gnueabihf.tar.xz , Powerarchiver wrongly thinks some .exe files have a length of zero:
Once extracted:D:\Temp\Powerarchiver\gcc-arm-10.2-2020.11-mingw-w64-i686-arm-none-linux-gnueabihf\bin>dir *.exe Volume in drive D is DATA Volume Serial Number is 0E12-BCA2 Directory of D:\Temp\Powerarchiver\gcc-arm-10.2-2020.11-mingw-w64-i686-arm-none-linux-gnueabihf\bin 2020-11-20 07:10 PM 1,391,599 arm-none-linux-gnueabihf-addr2line.exe 2020-11-20 07:10 PM 0 arm-none-linux-gnueabihf-ar.exe 2020-11-20 07:10 PM 0 arm-none-linux-gnueabihf-as.exe 2020-11-20 07:41 PM 3,030,119 arm-none-linux-gnueabihf-c++.exe 2020-11-20 07:10 PM 1,389,293 arm-none-linux-gnueabihf-c++filt.exe 2020-11-20 07:41 PM 3,027,513 arm-none-linux-gnueabihf-cpp.exe 2020-11-20 07:10 PM 4,040,503 arm-none-linux-gnueabihf-dwp.exe 2020-11-20 07:10 PM 391,769 arm-none-linux-gnueabihf-elfedit.exe 2020-11-20 07:41 PM 0 arm-none-linux-gnueabihf-g++.exe 2020-11-20 07:41 PM 3,026,926 arm-none-linux-gnueabihf-gcc-10.2.1.exe 2020-11-20 07:41 PM 609,607 arm-none-linux-gnueabihf-gcc-ar.exe 2020-11-20 07:41 PM 609,607 arm-none-linux-gnueabihf-gcc-nm.exe 2020-11-20 07:41 PM 609,607 arm-none-linux-gnueabihf-gcc-ranlib.exe 2020-11-20 07:41 PM 0 arm-none-linux-gnueabihf-gcc.exe 2020-11-20 07:41 PM 2,165,533 arm-none-linux-gnueabihf-gcov-dump.exe 2020-11-20 07:41 PM 2,343,605 arm-none-linux-gnueabihf-gcov-tool.exe 2020-11-20 07:41 PM 2,450,233 arm-none-linux-gnueabihf-gcov.exe 2020-11-20 07:54 PM 9,605,899 arm-none-linux-gnueabihf-gdb.exe 2020-11-20 07:41 PM 3,028,997 arm-none-linux-gnueabihf-gfortran.exe 2020-11-20 07:10 PM 1,412,943 arm-none-linux-gnueabihf-gprof.exe 2020-11-20 07:10 PM 0 arm-none-linux-gnueabihf-ld.bfd.exe 2020-11-20 07:10 PM 0 arm-none-linux-gnueabihf-ld.exe 2020-11-20 07:10 PM 0 arm-none-linux-gnueabihf-ld.gold.exe 2020-11-20 07:41 PM 25,546,567 arm-none-linux-gnueabihf-lto-dump.exe 2020-11-20 07:10 PM 0 arm-none-linux-gnueabihf-nm.exe 2020-11-20 07:10 PM 0 arm-none-linux-gnueabihf-objcopy.exe 2020-11-20 07:10 PM 0 arm-none-linux-gnueabihf-objdump.exe 2020-11-20 07:10 PM 0 arm-none-linux-gnueabihf-ranlib.exe 2020-11-20 07:10 PM 0 arm-none-linux-gnueabihf-readelf.exe 2020-11-20 07:10 PM 1,393,083 arm-none-linux-gnueabihf-size.exe 2020-11-20 07:10 PM 1,392,464 arm-none-linux-gnueabihf-strings.exe 2020-11-20 07:10 PM 0 arm-none-linux-gnueabihf-strip.exe 32 File(s) 67,465,867 bytes 0 Dir(s) 1,002,422,431,744 bytes free
When the same archive is being extracted from a git bash session (after having installed git 2.30.1 for Windows 64 bit version from git-scm.com), the .exe files are extracted as expected:xz -k -d gcc-arm-10.2-2020.11-mingw-w64-i686-arm-none-linux-gnueabihf.tar.xz tar xf gcc-arm-10.2-2020.11-mingw-w64-i686-arm-none-linux-gnueabihf.tar cd gcc-arm-10.2-2020.11-mingw-w64-i686-arm-none-linux-gnueabihf/bin ll *.exe -rwxr-xr-x 1 User 197121 1391599 Nov 20 19:10 arm-none-linux-gnueabihf-addr2line.exe* -rwxr-xr-x 2 User 197121 1421598 Nov 20 19:10 arm-none-linux-gnueabihf-ar.exe* -rwxr-xr-x 2 User 197121 2028927 Nov 20 19:10 arm-none-linux-gnueabihf-as.exe* -rwxr-xr-x 2 User 197121 3030119 Nov 20 19:41 arm-none-linux-gnueabihf-c++.exe* -rwxr-xr-x 1 User 197121 1389293 Nov 20 19:10 arm-none-linux-gnueabihf-c++filt.exe* -rwxr-xr-x 1 User 197121 3027513 Nov 20 19:41 arm-none-linux-gnueabihf-cpp.exe* -rwxr-xr-x 1 User 197121 4040503 Nov 20 19:10 arm-none-linux-gnueabihf-dwp.exe* -rwxr-xr-x 1 User 197121 391769 Nov 20 19:10 arm-none-linux-gnueabihf-elfedit.exe* -rwxr-xr-x 2 User 197121 3030119 Nov 20 19:41 arm-none-linux-gnueabihf-g++.exe* -rwxr-xr-x 2 User 197121 3026926 Nov 20 19:41 arm-none-linux-gnueabihf-gcc-10.2.1.exe* -rwxr-xr-x 1 User 197121 609607 Nov 20 19:41 arm-none-linux-gnueabihf-gcc-ar.exe* -rwxr-xr-x 1 User 197121 609607 Nov 20 19:41 arm-none-linux-gnueabihf-gcc-nm.exe* -rwxr-xr-x 1 User 197121 609607 Nov 20 19:41 arm-none-linux-gnueabihf-gcc-ranlib.exe* -rwxr-xr-x 2 User 197121 3026926 Nov 20 19:41 arm-none-linux-gnueabihf-gcc.exe* -rwxr-xr-x 1 User 197121 2165533 Nov 20 19:41 arm-none-linux-gnueabihf-gcov-dump.exe* -rwxr-xr-x 1 User 197121 2343605 Nov 20 19:41 arm-none-linux-gnueabihf-gcov-tool.exe* -rwxr-xr-x 1 User 197121 2450233 Nov 20 19:41 arm-none-linux-gnueabihf-gcov.exe* -rwxr-xr-x 1 User 197121 9605899 Nov 20 19:54 arm-none-linux-gnueabihf-gdb.exe* -rwxr-xr-x 1 User 197121 3028997 Nov 20 19:41 arm-none-linux-gnueabihf-gfortran.exe* -rwxr-xr-x 1 User 197121 1412943 Nov 20 19:10 arm-none-linux-gnueabihf-gprof.exe* -rwxr-xr-x 4 User 197121 2572182 Nov 20 19:10 arm-none-linux-gnueabihf-ld.bfd.exe* -rwxr-xr-x 4 User 197121 2572182 Nov 20 19:10 arm-none-linux-gnueabihf-ld.exe* -rwxr-xr-x 2 User 197121 4550029 Nov 20 19:10 arm-none-linux-gnueabihf-ld.gold.exe* -rwxr-xr-x 1 User 197121 25546567 Nov 20 19:41 arm-none-linux-gnueabihf-lto-dump.exe* -rwxr-xr-x 2 User 197121 1404945 Nov 20 19:10 arm-none-linux-gnueabihf-nm.exe* -rwxr-xr-x 2 User 197121 1531656 Nov 20 19:10 arm-none-linux-gnueabihf-objcopy.exe* -rwxr-xr-x 2 User 197121 1991350 Nov 20 19:10 arm-none-linux-gnueabihf-objdump.exe* -rwxr-xr-x 2 User 197121 1421598 Nov 20 19:10 arm-none-linux-gnueabihf-ranlib.exe* -rwxr-xr-x 2 User 197121 1163376 Nov 20 19:10 arm-none-linux-gnueabihf-readelf.exe* -rwxr-xr-x 1 User 197121 1393083 Nov 20 19:10 arm-none-linux-gnueabihf-size.exe* -rwxr-xr-x 1 User 197121 1392464 Nov 20 19:10 arm-none-linux-gnueabihf-strings.exe* -rwxr-xr-x 2 User 197121 1531656 Nov 20 19:10 arm-none-linux-gnueabihf-strip.exe*
The same archive file does extract properly under a native Linux Ubuntu 20.04 system, or under Windows 10 using the WSL2 Linux subsystem using xz and tar.
I just saw, that on the Website, PowerArchiver 2021 20.00.73 is advertised as latest version. (Actually, the downloaded version says, it’s 20.00.70 in the about dialog)
But it still comes with the “red icon set” for preview versions and has some known unfixed bugs, as I read here.
Is it sufficiently stable to be used on production systems?
Hi I recently bought PowerArchiver and found some bugs and issues that I hit testing some of the features out.
If you are doing a backup and on the compression options screen its default is compression format is PA with no option to change disk spanning. If you change to 7-zip you can change disk spanning. If you change the disk spanning then move back to PA format the field for disk spanning disables but the option stays set to what you changed it to. When you do a backup it will use PA with files spanning but PowerArchiver says that its not a valid format when you open it. If PA can’t really do file spanning then this screen is allowing it.
I have attached an image where the progress bar is in the middle of the CD/DVD/BD Tools screen.
I have a 7-Zip file I created using the backup tools doing an increment backup. It opens and extracts just fine but if you using the Test option PowerArchiver locks up. Link to file: Backup-2021-02-05-20-35-36 TEST LOCKUP.7z
On any Zip/PA/7-Zip process the pause and cancel buttons do not work. You have to hard kill the entire application to get out.
There would be many of us with Intel Processors.
and they have their own optimized zlib algorithm, which can result in more efficiency if used combined with their hardware processor.
Can we get the same Functionality Under Hardware Acceleration Feature?
Zlib is not the only feature that intel has included with their processor, there’s many, which if combined can result in efficient and better compression ratios.
After the batch archiving is complete, and if I click on whitespace of the PA app, I get this error.
I did check for ongoing process and ensured no archives were corrupt, It seems like activity did complete successfully but the error is shown for no reason, and only after clicking the whitespace.
Please see if this can be removed.
I’m using the Kaspersky Total Security.
I have configured PA as exclusion as followed:
and also is set us trusted application
PA Trusted Application.png
My Antivirus likes to scan for everything, and it’s safeguarding behavior is to prevent the access to the file until the file is properly scanned for.
PA when losses the access to file, it is stuck, consumes Resources, and never completes the process or throws any error
PAStarter should also work as PAMonitor:
There should be a monitoring process, at least if I’m using queuing feature, that should check for never ending compression processes and terminate them so the queue can be little bit automated.
There should be multiple attempts at retrying if PA loses access to or is denied, instead of having to see process was stuck for longer duration.
Or, better, save the parameters I used for keeping the files in compression, and automatically restart the whole compression process after termination the same, of same folders and files set, this should happen in case if compression was stuck.
If you use Queue Feature, you are not saving on space, you are just squeezing less.
I did test the same on multiple files, and of different types.
It does have large difference for each large file you are trying to squeeze.
Folders with multiple files, just have no benefits if you use Queue Feature
I am using the portable version of PA2021. After switching from build 58 to 73 I have problems with the color-scheme:
While 58 behaves like expected and showed everything in light or dark colors according to the settings, 73 always shows the lower part of the window in dark colors, no matter whether I select automatic, light or dark.
This happens on a clean installation of 73 as well as on an update from build 58. I have attached two images generated on the same machine at the same time with the same settings. The upper shows build 73, the lower 58. Is it a bug or some changed setting I miss?
Thanks for help!
I currently own the PowerArchiver Select - lifetime free upgrades and support for PowerArchiver Toolbox English license.
This license is active on 1 device. Does the license allow me to activate PowerArchiver on a second device that I own? Or do I need a separate license for that?
Thank you ! :)
AutoUpdates not working
I’ve been using PA for many years now, but this Patchbeam technology is a pity. While it’s working fine on my home network, it drives me crazy behind my corporate firewall and proxy.
I’ve entered my proxy information in the settings dialog as with most other programs. But whenever I start Patchbeam (or PA does it by itself), the complete interface freezes for several minutes (~3-5) preventing me from using PA or aborting the updates. I just used Process Monitor from Sysinternals to check what’s going on.
What irritates me are several things:
- I cannot see any network activity neither from the POWERARC.EXE nor from the PatchBeam.Exe
- Although these two processes are creating >20000 file and regsitry accesses during the first few seconds, they seem to completely sleep for the rest 4 minutes of freezing
- After Patchbeam starts, It takes around a minute to display the special news in the lower half
- After the five minutes, PatchBeam teel me there were no updates found and that my currently used versions (PA 12.12.02, PB 1.01.07) are the most recent
This leaves me with 3 questions: Why does it take so long? Why is it freezing and which process actually tries to get the updates from the server? And shouldn’t it show me PA 13 as an update?
Before you ask: The behavior is the same since PatchBeam was introduced - it never worked for me. It also affects every machine in using in office. So currently I have to update manually and disable PatchBeam completely.
Any help is appreciated :)
There is obviously problem due to the firewall, it seems it gets blocked by something… possibly AV as well? Because if it shows empty, it means it could not access the internet.
As to the news, thats displayed by Internet Explorer system control, actually not PowerArchiver itself. So if it shows after a minute, thats not related to PA itself.
We need to setup something similar to see why is it not working.
I also believe that the request gets blocked somewhere. But I believe more it’s a proxy problem and not a firewall one (as long as you’re not using special ports). The firewall would ask for access and despite that, it works with other programs flawlessy.
I just tried to install the Virtual drive at work - no chance. This time patchbeam just closes without any message after searching for a while. No error, no success - nothing.
Could you maybe give me an example on how a working proxy configuration looks like? Or how I could check that PA is actually using the proxy that I’ve entered in the options dialogue correctly?
Here is the direct link to PA’s VD drivers;
let us know if the link works properly or not…
Sorry that I didn’t reply. Yes, the link worked. But I had some problems updating PA and since I was in a hurry, I manually reinstalled everything instead of trying to get Patchbeam to work. I anyway have the feeling, that over the years PA updates had some leftovers and the Patchbeam/VD updates and drivers weren’t cleaned up correctly (do you have by chance a removal tool to clean up everything?).
However, even with the current version of PA and Patchbeam on a different PC, the problem still persists. I now have another computer, where I would like to install the VD driver, but the Patchbeam process hangs completely until I kill it. (I know I could use the direct link, but I want PA to work correctly ;-) )
For me it looks like it either can’t get through the proxy or it uses a different port which might be blocked.
I’ve entered my proxy details (host+port, no login) in the settings and after a couple of tries (with and without “http://” in front of the hostname) I think I’ve managed to get the normal update running. At least I can see it connecting to the proxy as well as trying to reach vip1.g-anycast1.cachefly.net (what is that??). However, the process still hangs for >1 Minute until telling me there is no update (which is wrong, since I still have 14.01.06).
But if I click the Virtual Drive button and accept the popup to download the drivers, the Patchbeam process never tries to connect to any server. I can see that it gets called with different parameters and apparently doesn’t even try to read the proxy settings or connect anywhere. It also never shows this AD-Frame in the lower section.
Could you give me an example of correctly entered proxy settings (I mean the format), just to be sure?
In the options I can check “Use Debug version of PatchBeam update system” - what does it do? Could it help to investigate the problem?
Do you have a proxy environment where you could check such things? 'cause I have the feeling that this never worked ;)
RJWaring last edited by
I have always loved the idea of Patchbeam and in most circumstances it works.
However, going back to when we were testing during Alpha, beta and Release phase this was something I raised a few times suggesting the application hung and wasn’t very helpful when things didn’t work.
For example, things I have requested in the past were;
1. Test Connection (before it proceeds to open Patchbeam) this would be helpful with FTP as well.
2. Turn on or off News page (at bottom of patchbeam) this I find slows things down on poor networks or systems with highly restrictive firewalls etc.
3. Direct download links (old fashioned way to obtain full downloads should PB not function)
I have had in work networks countless issues and even when I have configured everything I can it would still not work.
Typically, if you want the best use your Internet Explorer’s LAN settings as an example for connection as in most businesses they filter this through their proxy firewall.
The catch is many companies block “unknown” or “misc” traffic and unless you report it then it will remain blocked.
This is to help reduce the load on the network and increase security. Obviously, the firewall doesn’t know PowerArchiver is a safe application its up to the IT dept to make that adjustment.
I’m glad to hear that I’m not the only person having issues with PatchBeam behind Firewalls/Proxies.
I fully understand the reasoning behind such measures (I’m a software developer myself) and I also know the correct settings for my network here.
I also fully agree to all points you mentioned.
Having a connection check in advance would really help here, since I don’t even know whether PA is using my proxy settings, whether they are correctly parsed or where the problem is.
As long as PA only uses a normal http connection, there shouldn’t by any firewall issue apart from the proxy stuff.
It seems to be proxy/firewall issue… when it comes to PAVD installation, it is very simple and not usual Patchbeam mode where we patch the changes via our engine.
Basically here is how it works (for PAVD):
a. Downloads txt file on our server to see what is the latest release.
b. Shows update option if there is new release.
c. Downloads full installation file, closes PA and executes it.
For the Patchbeam update of PA, it seems that it is not actually downloading the txt file with the update - basically it times out after 1 minute since it is not getting the file. What it is likely working is downloading of file in IE frame below.
Cachefly is CDN provider we use for all of our downloads… they have servers around the globe and you go to the closest one for the best speed/reliability.
Thanks for the info spwolf. But then this looks like a bug to me, since PAVD is not using the proxy settings and instead tries to connect directly. So basically, I see 3 issues here:
- PAVD installation doesn’t use proxy settings
- Patchbeam update doesn’t use proxy settings correctly (or connects via a non-standard port)
- Both variants don’t give any feedback to the user what went wrong and freeze the whole application completely
I anyway never understood, why the Updater is a modal window and doesn’t allow me to continue using PA.
RJWaring last edited by
It would be good if the Patchbeam application had a option to collect a debug text file detailing what went on in the background… ie like you see during FTP… making connection, logging in username , logging password, syncing , approved etc
so for this attempting connection, logging in , Error leaving proxy.
The autoupdater dialog is not that different from other applications Avast, norton etc have it built in and if theirs crashes it can cause the application to require a restart. However, they have autodetect features that try’s to establish a connection using its own code logic.
I wrote something similar
1. Code uses the settings provided by IE Proxy settings
2. If user enters in details it uses this instead
3. if neither of the above worked it then attempts some alternatives
4. if 1,2,3 fails it prompts the user requesting advanced details.
but take into consideration the auto update hasn’t really changed since it was 1st introduced and for the majority of users it works.