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 ! :)
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.17188.8.131.52.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.
Converting an archive to .zip (using both the “Deflate (.zip, compatible)” and “Store” compression methods) always creates a .zipx file instead.
Using the “Store” method sometimes creates a .zip file; I have seen it happen just now, but I cannot reproduce it.
How to unpack a five Rar file archive
Wow, you guys need some serious help in user-friendly instructions. The program looks great, and I’ve tried to use it a few times over the past few years, but each time I end up screaming at my computer and removing the program.
The worst problem is deprecating the “new file types”. Inevitably once I pass an archive to Power Archiver it is like shredding the file. Usually file archiver finds a problem, like the worst lab instructor I ever had in college. Then there is no way to fix the problem. When I click on repair archive one of two things happen: the archive gets repaired and then doesn’t work or the archive can’t be repaired and then doesn’t work. Moreover when I try to go back to WinRar to open the archive I’m told that it belongs to Power Archiver now and it is gone forever.
When I look for ways to go back to ordinary Winzip or Win Rar I’m told that the file formats have been changed and thats’ that. Your Forum has some posts about going back to the old winzip or win rar but only under special circumstances, which I think were related to the El Nino climate cycle off the coast of Ecuador. I couldn’t find the right combination of buttons and the other reader couldn’t either.
Now that I"ve gotten some of that off my chest I’ll make a suggestion and ask something specific.
My suggestion is to have a visual quickstart guide taking people through the basic tasks like unpacking a zip or rar archive and storing the program, music or what ever some place convenient. Include a few things that could go wrong. Do this for almost all the operating modes of the program. During the course of my thirty years as a Professor of Engineering I’ve seen that people prefer to build up to the general from the specific and that early on hands on examples are invaluable. Going in the other direction, from general to specific is guaranteed not to work.
In my case I have, or had five zip archives I wanted to open and extract a large executable. Power Archiver got ahold of it and changed the file extensions to file archiver, an extension that no other compression archiver can even see. All this would be fine if Power Archiver were a friend. Instead it tells me my CRC file is off. I don’t recall having a CRC file for this archive. The program then asks if I just want to skip it, and I click yes. But Power archiver does nothing, sort of like a street tough daring you to do something and letting you know you have the problem and not Power ARchiver.
So I try to deprecate to an earlier type of zip but find nothing. I create an SFX archive, which the program lets me do, but when I try to run it an ominous error message comes up saying, if I recall "didn’t we just tell you your CRC is bad, and now your back. Well I didn’t want the program to lose it’s patience, so I somehow got the SFX archive to extract the five component parts.
But the parts are now completely inert and useless in that other unpack archives like Win Rar can’t see it and PA refuses to any more with the mess it created. It was my problem now.
I think the biggest problem here is that you do have to start from start ;-). I dont know how can PowerArchiver explain what are file associations in Windows and how they work for instance - it is general knowledge, or it should be. Just like in your engineering class, I am sure you sometimes had students who did not have enough prerequisite knowledge to understand your lectures…
So let me try to explain few things:
CRC is short hash of every file in every archive, that is done automatically during creating of the archive and serves to identify if files are still valid in the archive, after extraction. Common issue that happens is corruption of archive during download/upload process or CD/DVD media that goes bad and corrupts files on it. In that case, PowerArchiver will report an CRC error (files that are being extracted are not the same as files that were originally compressed). Of course, this is the most common cause, it could be something else as well.
File associations in Windows - when you say PA takes over file associations, it is just that it sets itself (based on your confirmation) as default double-click option. So if PA or WinRar or WinZip are set as default programs to open certain extension, it does not mean that other programs can not open it. It just means that they open it by default. To open archive with other program, you can for instance, right click on it in Windows Explorer and select one of the shell extensions to use… or right click on archive and select Open With… menu. Or you can open program such as WinRar, and then use its Open button/menu to locate archive and open it.
In PowerArchiver, you can disable any specific (or all) file associations by going to PA> Options> Config> File Formats.
Was this at least a bit helpful? Thank you!
My suggestion is to have a visual quickstart guide taking people through the basic tasks like unpacking a zip or rar archive and storing the program, music or what ever some place convenient.
Have you checked the Help section in PA? In the section “Getting Started – Brief Tutorial” there’s basic instructions of how to Create, Add, Remove, View and Extract.
Instead it tells me my CRC file is off. I don’t recall having a CRC file for this archive. The program then asks if I just want to skip it, and I click yes. But Power archiver does nothing, sort of like a street tough daring you to do something and letting you know you have the problem and not Power ARchiver.
It sounds like your problem is that you have a corrupt Archive that can’t be repaired. You can’t blame PA for this, it would be the same if you had a corrupt image that the image program couldn’t open, then the problem is not the program itself but bad corrupt data that’s used to open with the associated program.
Thanks for both replies. I particularly appreciated the Wiki on CRC. I was always curious how they were worked out and what was behind them.
I think my CRC error is what messed up the file conversion. What I will do is try other archives and work with PA to get the hang of it. It truly is the most fully featured and flexible file archiver around.
all the best, Joel
Was struggling with something and you post inadvertantly helped. Yeah, can be a little tricky to get your head around at first.