-
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.
alt text
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.
Reference:
https://www.intel.com/content/dam/www/public/us/en/documents/white-papers/zlib-compression-whitepaper-copy.pdfCan 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.
-
Hi,
After the batch archiving is complete, and if I click on whitespace of the PA app, I get this error.
PA Batch.png
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:
PA Exclusion.png
and also is set us trusted application
PA Trusted Application.png
Scenario:
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.
The issue:
PA when losses the access to file, it is stuck, consumes Resources, and never completes the process or throws any error
Recommendation:
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.Also,
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.
Here’s explaination:
https://youtu.be/XcxG2wxyink
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
-
Hello!
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!
A.BorquePA2021_73.png PA2021_58.png
-
Hello,
PowerArchiver Command Line 7 support file greater than 2 Go ?
Thanks
-
If you have tabbed archive browsing(reuse same window for all archive opening)
and if you open two archives, and right click on older one to view properties it will only show of the recent archive that was opened, on all tabs/archivesupgraded to 20.0.73
-
Hi.
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 ! :)
-
Hello!
While the installable version of PA 2021 has already received two updates and is at version 20.0.73 the portable version still remains at the initially released build 58. Are there plans to update that version, too?
Thanks for a reply! -
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.
-
When you select “Deflate (.zip, compatible)” as the method, it still converts the archive to a ZIPX format.
-
Would like to see uha archives supported compression as well as extraction. I use this all the time and it is a very good compression format
-
In windows 10 you can right-click and select send to and the compressed zipped folder and the zip folder will contain the name of the last selected file.
Does PowerArchiver have a similar function?
Tom
-
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.
-
patchbeam a waste of time never updated with latest version
-
I have just installed 2021, but seems to have similar issues to 2019. If you move the app between differen monitors (with different resolutions) the app does not automatically adjust accordingly, so on one monitor I have the app is too big for the screen, whereas on another monitor it only takes up a small fraction of the screen.
This was worse with 2019, where the fonts were totally screwed up, making the app unusable. This seems better in 2021, but still not working properly. -
Hi! I came across an issue when I tried to uninstall PowerArch 2013. I got an error “The specified account already exists” which broke the process. I got the same error when I tried to install the current version, without uninstalling the previous one.
So I can’t uninstall and I can’t install PowerArchiver. Any suggestions? OS Windows 8.1 x64.Dariusz
-
Good morning,
I have been using all compression programs for over 20 years, I have always found Winrar very easy to use when I create a self-extracting archive, even 7-zip is simple, “right click” and “create self-extracting archive”, because on powerarchiver it must be like this confused ?
It doesn’t just create the archive, it opens a page where I have to select the file again, what kind of archive, which folder to create it, etc … you should learn from your competitors how to make life easier! -
Hi,
So refer this screenshot:
image_2020-12-30_115129.png
The properties panel that you see, is what I tried to compress, using PA, with following settigs:
Extreme Strong optimize
https://forums.powerarchiver.com/assets/uploads/files/1609079025475-image_2020-12-27_195344.pngThe process was stuck at 0% with no progress for over 8 Hours:
PA.png
Then the usual, clicking will make it go not responding.
So, I could not get the files compressed using PA.
I tried 7zip, and it worked, so that’s 1 issue.
PA shows incorrect original(before compression) size of total contents.
Refer the first screenshot.
folder’s size is shown correctly in 7ZIP
but not in powerarc.this happens with every archive, whether they are compressed in PA or not, whether it has only 1 file, or multiple files inside multiple directory.
Neither does the archive property panel shows original content’s size.
Upload to FTP counts -%?
-
I am uploading a .7z file to my FTP and its counting completed it -%'s and not showing a progress bar. I am pretty sure its uploading the file.
Also…when you click on cancel it seems to take it as a suggestion and you have to hit the exit button 3-4 times for the window to finally close. It does this when zipping files as well…any idea on that?
-
Not sure about ftp uploading, but during Compression/Extraction “Cancel” actually means when current file operation (that’s file NOT archive) is finished.
PA has to wait for the “library” function to return control to the GUI.Actually, maybe ftp is similar??
-
I have attached the pic I took of it uploading to my FTP.
As far as canceling or stopping an archive/FTP upload in progress…what is the best method? Like I said currently I hit the x button 3-4 times and it will close.
-
Not sure about ftp uploading, but during Compression/Extraction “Cancel” actually means when current file operation (that’s file NOT archive) is finished.
PA has to wait for the “library” function to return control to the GUI.I understand this is true for PA, but I wish it would cancel when you hit cancel. 7Zip, for example, cancels immediately when you tell it to, there is no waiting, no matter how large the current file happens to be.
-
uploading via File> Send> FTP?
-
Yeah, after I created the archive I right clicked then did PA…FTP it and then the location.
-
I understand this is true for PA, but I wish it would cancel when you hit cancel. 7Zip, for example, cancels immediately when you tell it to, there is no waiting, no matter how large the current file happens to be.
complaining about it is first and major step into fixing it :-)
-
Yeah, after I created the archive I right clicked then did PA…FTP it and then the location.
ok, thats from shell… will take an look
-
Did you want me to try it from the program itself? Also…I second the suggestion that Dragon57 had…hitting cancel should probably cancel the whole thing (at least IMO). Should i start a thread in the suggestions/wishlist area?
-
Did you want me to try it from the program itself? Also…I second the suggestion that Dragon57 had…hitting cancel should probably cancel the whole thing (at least IMO). Should i start a thread in the suggestions/wishlist area?
yes please… and yes, you should want everything to work to your liking… then if something is not possible for whatever reason, we will say so.
but do not be restricted by what we say :-)
-
Odd spwolf….I tried another file and its at 100% uploaded (done same way) but there is no way its done…its a 6 GB file (other was 2gb) both were done in the same way. I just tried to upload them by opening PA and it stays at 0 bytes and wont even attempt to upload. Hmmm.
-
ok, we will try from our end…
-
OK I closed PA and reopened…and inside PA I did another upload (same file and it is now uploading…but has the same issue (% doesn’t change on this one). Must be a % based issue…hope I was of help!
-
very helpful!
-
I have been watching this thread. I have tried it several times, and the progress bars and the %s are working just fine.
I have tried it within PA and using the shell. Works fine either place.
Odd
-
i suspect it has something to do with files over 2 GB / 4GB and since this entirely new component in 2011, it makes sense.
-
Does make sense.
But I am giving it a test right now. If my results are different, I will let you know. But FTPing a file in excess of 2 gig will definitely take some time.
-
I did not wait for it to finish.
For what it is worth, I got a slightly different result.
My progress started at above 250% – and it was counting down (252, 251, 250 . . .)
-
that was file over 2 GB?
-
yes . . . about 2.6
-
Both mine were over 2 GB. One was 2.2 and the other was 6+. Other files do work fine.
