-
Hello,
PowerArchiver Command Line 7 support file greater than 2 Go ?
Thanks
-
When viewing a zip archive with .TGA image files (https://en.wikipedia.org/wiki/Truevision_TGA) the file preview shows Unknown Picture File Extension (.tga).
Seems strange that such an old image file format is not supported. -
Hi,
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.
-
Hello. My problem with Powerarchiver is as follows:
First of let me say that I am running a Windows 7 Starter edition on my Toshiba NB505 laptop. You can see my specs if you google it. Needless to say that it has very limited resources and has low ram and roughly 1.66 GHz Atom processor.I am currently using the latest version of PA. But mostly the tasks I do with it are create and uncompress zip files, as this comes in handy with my needs for compressing older files which I dont need. There is where it comes my issue with program and it is just that version after version it becomes harder for my computer to load and create zip files and 7zip ones. Needless to say that the same goes for zipx.
I have been using PA for a decade and its a good program but it is just that the current version has things which I don’t need or seldom use it, such as the preview file panel, and also the explorer tabs, skin customization and the nagging conexware update tool. Thus I was just asking, Does it exist a minimalistic version of PA or perhaps some ultra light version of it?. Something which it can be run on older computers.
Please don’t say to install an older version or going back to 2003, as well, this is not what I had in mind. I know that I could use the command line version but for me usng a GUI is more convenient. Regsrding compression speeds, I mostly use deflate for legacy zip files on the fast setting.
So far what I am doing is to set PA to use the classic skin windows view and while it does alleviate some of the lagging symptoms it doesn’t really seem to make the program to run or load faster.
Any help or advice on my problem?. By the way, I use the PRO version as that’s my current license. By the way, does PA has any pdf user’s manual or reference book? I see there are changes and numerous functionality that has been added but I have no clue on how to use it. I hope somebody could help me with that as well.
-
Converting an archive to .zip (using both the “Deflate (.zip, compatible)” and “Store” compression methods) always creates a .zipx file instead.
pa-convert-zip-1.jpg
pa-convert-zip-2.jpgUsing the “Store” method sometimes creates a .zip file; I have seen it happen just now, but I cannot reproduce it.
-
Hi,
I thought, I’ll give it a try and upgrade my PA 2018 Toolbox on my production machine to PA 2021 (20.10.03)
Sending registration codes in your order recovery doesn’t seem to work at the moment (I also checked my junk folder), online activation works Using registry to disable modules (for example HKLM\SOFTWARE\PowerArchiverInt\General\DisableBurning) doesn’t work as expected with modern ui. The module is visible, but I’ll get the trial nag, if I try to open it. It’s almost fine in classic and ribbon mode.7989017c-3cd2-4a99-a1f6-06ce62329dec-image.png
“DisableClouds” and “DisableExplorer” seem not to be respected at all, while the classic UI seems to respect the setting to disable any other unused module:
In settings I won’t be able to access the SmartAI settings and the settings for the internal editor if the FTP module is disabled
89843f23-ad89-45bf-92bc-406b1a11dfc9-image.pngcc40877b-d8d0-404c-b7f8-d5ae0a1ee445-image.png
-
New version: 20.10.03
Download:
https://powerarchiverdl.cachefly.net/2021/powarc201003.exeRelease Notes - PowerArchiver - Version 20.10.03
** Bug
[PA-2899] – PowerArchiver icon should be yellow for shell and main interface
[PA-2906] – Add Window size should be remembered
[PA-2901] – Cloud: when started as standalone, skin should be fully applied
[PA-2896] – Cloud config window not skinned in Dark Ribbon skin
[PA-2900] – Cloud: close button enabled when no connection, should be disabled
[PA-2902] – Cloud: change name of Amazon option in cloud
Various fixes and improvements. More fixes and updates coming up! Thanks for everyone’s help!
-
Re: Using the Queue Feature affects Compression Ratio negatively
I’m sorry if the dev team is affected by pandemic, and if anyways that is affecting their quality to provide quality software.
But honestly, it’s been an year I have been complaining about the queue feature, it is taking them ages to fix.
referencing the above bug, I have been waiting patiently, but the bug isn’t fixed at all.
The old queuing bug where PA gets stuck randomly, isn’t fixed either.
The Bug where you keep 10-15 files in queue at once, will cause the software to miss few in queue.
and sometimes it would compress into a corrupt archive, so you have to manually open each archive and make sure everything is there as expected.
There’s way too many bugs, and I see none getting fixed.
I’m disappointed with this software.
I should have sticked to 7zip or given a shot to other archivers than this, at least they don’t provide update once in 4 months and fix nothing.
-
Is there any way to reset the compression profiles back to install default??
-
When viewing an archive I want to be able to preview the text files within the archive. In past versions, there was a preview pane on the right side of the screen. How do I enable this in the most recent version (20.10.02)?
-
Hi guys,
I have some mistakes today with PowerArchiver Installation with GPO.
I checked permissions of the share folder and I already installed some app from this.
I have downloaded 32b and 64b it’s the same problem.
App is on the install list of the GPO, but don’t install on the client. All app can be install but only powerachiver not. What the hell !So i tried :
Checked : security of share folder --> ok (install of other app ok!)
RSOP checked --> nothing special
(obviously force GPO, multiple reboot)Can you help me please ?
Capture.JPG
-
48a99323-a8a8-4c60-9e10-dba0f65b3e33-image.png
The speed is too high to show properly.
-
I’ve been dealing with an intermittent explorer.exe crash for 5-6 years now. It happens randomly and will usually occur multiple times within a single session of an hour or two on my machine when manipulating files through Windows Explorer. explorer.exe is the only thing that ever crashes, so it’s not hardware IMO. I’ve done all hardware diagnostics and RAM is good. I’ve even swapped out motherboards with different brand and even the exact same one and it still crashes. sfc /scannow indicates system files are fine. I’ve done multiple reinstalls of the OS with no positive results. This crashing has happened on Windows 7 64-bit and Windows 10 64-bit. It seemed to get more frequent with Windows 10 after upgrading last year. I’ve also been using PowerArchiver throughout that time period (upgrading over time with new releases). I recently disabled all non-Microsoft extensions via ShellExView and saw no crashes for about 10 days, which is really unusual. I turned back them all back on after 10 days and saw another explorer.exe crash within the hour. So I disabled all 32-bit extensions and saw another crash. Following that I disabled all the PowerArchiver shell extensions and haven’t seen a crash after a day of heavy usage manipulating files within Windows Explorer, which doesn’t happen for me. The crash dumps I’ve captured don’t seem to indicate PowerArchiver is involved but I have a hunch it has something do with PowerArchiver shell extensions. The system even feels smoother with the PA extensions disabled. Windows 10 reliability monitor always has the same type of problem:
Description Faulting Application Path: C:\WINDOWS\explorer.exe Problem signature Problem Event Name: BEX64 Application Name: explorer.exe Application Version: 10.0.17134.165 Application Timestamp: 4031a9f8 Fault Module Name: StackHash_e78e Fault Module Version: 0.0.0.0 Fault Module Timestamp: 00000000 Exception Offset: PCH_8D_FROM_ntdll+0x000000000009AA54 Exception Code: c0000005 Exception Data: 0000000000000008 OS Version: 10.0.17134.2.0.0.256.48 Locale ID: 1033 Additional Information 1: e78e Additional Information 2: e78e327659b46c9a0c6916396b253cbf Additional Information 3: cebf Additional Information 4: cebf952c5db535ae7880488aafce55d9 Extra information about the problem Bucket ID: 1a57e4e784fbc735c231c68bd88581a9 (1311047270476906921)I know this is a very nebulous explanation but is there any way to link this up to PA shell extensions as the cause? I can provide the crash dumps and additional information if necessary.
-
I was looking around in PA 2021 20.10.02 and discovered an issue. When I hit close to close out of this window, nothing happens. I have to go into taskman and kill the PA application.
-
Latest version: 1.00.32
Download:
https://powerarchiverdl.cachefly.net/macos/powarc-macos10032.dmgRelease Notes - PowerArchiver 2021 for MacOS 1.00.32
** Latest fixes:
Extracting RAR4 archives -Previous version was not able to extract RAR4 archives properly. This has now been fixed and RAR4 archives are properly extracted.
Password Policies text in Encrypt window – Password policies section shown in the password entrance dialog is not meant to be configurable in that window, as it is meant to display those settings which can be configured in the Configuration menu that was added in the previous version of PowerArchiver 2021 for MacOS.
Fixed registration and crashing issues on BigSur 11.1 operating systems.
More fixes and coming up in the coming update! Thanks for everyone’s help!
-
Configuration:
Powerarchiver 2021 20.00.73
Windows 10 Education 10.0.19042 Build 19042When 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:
98773b3b-65c0-48fa-8cd4-d081b2e0adee-image.png
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 freeWhen 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.
-
Is there a command line to include the Registration Code when pushing an install using Microsoft Intune/Endpoint Manager?
I am able to push the software, but I’d like the PowerArchiver to be registered when it gets to the workstation instead of entering the Registration Code on each workstation individually.
Thanks
-
Hi,
The “Print button” to create a file listing of the files in the archive opens an empty drop down menu.
there are some issues with the UI in the classic interface:
610bb5df-42a7-4a67-85ab-163ca0c655a9-image.png
Clicking on the empty entry let me save the file listing as txt file, the entry for html files is missing completely. The toolbar for the file preview feature is cut at the window edge. Options on the right aren’t accessible at all.Kind regards
-
Hi,
I can’t close ZIP archive comments. Neither in archive nor in explorer view the “x button” works. I’m testing with PA 20.00.73 (x64 and x86)
e5f2dd8c-e008-4c26-a364-4b1a0a8f8c69-image.png
PowerArchiver 2016 not registered anymore after updated to v16.00.56 RC3
-
I’ve already sent a support request but as I got no response yet I will post it here.
I was using PowerArchiver Toolbox 2016 (probably v16.00.46 RC2) until it updated itself this weekend. When I started PA again it showed me the “trial expired” screen. So I tried to register it again with the key I retrieved about a month ago when PowerArchiver updated itself from 2015 to the 2016 version. After PowerArchiver restarted I still got the “trial expired” screen. Thus the Toolbox registration key that worked for 2016 RC1 does not work for RC3.
Thus I logged in the “Order Recovery” website to request a new key. A few seconds later I got the new key but the new key does also not register PowerArchiver Toolbox (still giving the trial expired screen). I requested a new key again, but still no luck.
Now two days later I requested again a new key, but also this key does not work.
So I uninstalled PA 2016 v16.00.56 RC3 and reinstalled v16.00.43. After installing the older version opens already registered with the Toolbox key.
So it seems somewhere between v16.00.43 and v16.00.56 something changed that makes existing Toolbox 2016 keys not work anymore.Robert
-
OK, I downloaded several older versions to determine in what version the registration problem starts. It turns out that v16.0.0.50 is the last version where my Toolbox key works. After installing v16.0.0.51 I get the “trial expired” dialog.
Hope this helps in tracking down the problem.Robert
-
Hi Robert,
Was this ticket #44151?
We replied to it yesterday, if that was it.Thanks for the details. Can you send the complete registration email to the reply of that ticket? You can copy the complete 2016 registration email and paste it in your reply there.
We will take a look at it immediately.thanks again!
-
Hi Robert,
Was this ticket #44151?
We replied to it yesterday, if that was it.Thanks for the details. Can you send the complete registration email to the reply of that ticket? You can copy the complete 2016 registration email and paste it in your reply there.
We will take a look at it immediately.thanks again!
Hi Mili,
I don’t know what ticket number it was. I didn’t receive an e-mail confirmation with a ticket number or any reply (it is not in the spambox). Seems I’ve mistyped my e-mail address in the support form. Sorry.
I’ve sent the mail with the non working Toolbox 2016 registration code in a new support request.
Thanks and regards,
Robert
-
got it! thanks very much for sending it again
looking into it now
-
Hi Robert,
I’ve just sent another email with a question that will help us, we’re in the middle of investigating and figuring out the issue and your assistance would help.
Many thanks again!
-
I’ve already sent a support request but as I got no response yet I will post it here.
I was using PowerArchiver Toolbox 2016 (probably v16.00.46 RC2) until it updated itself this weekend. When I started PA again it showed me the “trial expired” screen. So I tried to register it again with the key I retrieved about a month ago when PowerArchiver updated itself from 2015 to the 2016 version. After PowerArchiver restarted I still got the “trial expired” screen. Thus the Toolbox registration key that worked for 2016 RC1 does not work for RC3.
Thus I logged in the “Order Recovery” website to request a new key. A few seconds later I got the new key but the new key does also not register PowerArchiver Toolbox (still giving the trial expired screen). I requested a new key again, but still no luck.
Now two days later I requested again a new key, but also this key does not work.
So I uninstalled PA 2016 v16.00.56 RC3 and reinstalled v16.00.43. After installing the older version opens already registered with the Toolbox key.
So it seems somewhere between v16.00.43 and v16.00.56 something changed that makes existing Toolbox 2016 keys not work anymore.Robert
thanks for the report. It seems to have something to do with PowerArchiver version you are getting free upgrade from. I have created reproducible ticket in our system and we will figure out until next release. This is only for people who had purchased PA 2011 Toolbox English with BD.
In the meantime, we will add PA 2016 Tbx with 12 months of select to your account so you can continue using latest PA 2016.
thank you!
-
Hi Robert,
I’ve just sent another email with a question that will help us, we’re in the middle of investigating and figuring out the issue and your assistance would help.
Strangely I didn’t get your e-mail with your question while I double checked if the e-mail address I entered in the support form was correct. Anyway, I got the e-mail with a new registration key that works. Thank you very much.
The non-working key was indeed from an update from PowerArchiver Toolbox with BitDefender.
Many thanks to both of you!
Robert
-
I had the same issue with an automatic update going from 16.00.46 to 16.00.56. I found the old installation file and reverted to .46. It was still registered with no action on my part. I sent an email to support with more details, but if you need information from another ‘bad’ system I can supply it if needed.
(Question: Does the registration code change each time you request it? I had looked up the email from December with the registration code and tried that, then requested it again to confirm that I had it correct and it provided a different code.)
-
I had the same issue with an automatic update going from 16.00.46 to 16.00.56. I found the old installation file and reverted to .46. It was still registered with no action on my part. I sent an email to support with more details, but if you need information from another ‘bad’ system I can supply it if needed.
(Question: Does the registration code change each time you request it? I had looked up the email from December with the registration code and tried that, then requested it again to confirm that I had it correct and it provided a different code.)
Hello,
this has been solved update few days later, here is the latest release:
http://dl.powerarchiver.com/2016/powarc160060.exeYes, the code changes each time due to encryption used. Thanks!
