-
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.
-
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
-
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.
-
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.
-
Hi,
So my rig is as below:
CPU: Intel® Core™ i7-4720HQ CPU @ 2.60GHz (Turbo 3.7GHz)
RAM: 16 Gigs DDR3
Samsung SSD 860 EVO
Windows 10 pro for workstations x64, freshly installed on 22nd Dec 2020, and updated.
PA freshly downloaded on same day, so it’s 2021 x.x.62 versionPA Stuck.png
Issue and reproduction:
If you start a compression, and if it’s mid way anywhere or even started, and you try to cancel it, the window will get stuck there, another click or key press will make the window not responding, then, and more will make windows to collect logs for crash, and the process will be terminated by windowsOn the other hand.
If the process is mid way, and if you try to pause it, the compression, CPU utilization, RAM usage will stay/increase as if the compression if still going on, the whole process will take it’s course, instead of doing what we clicked on.
So, both pause and cancel buttons are useless.
-
I recently installed PA 2021. But the PowerArchiver Starter, for my backups, keeps running at high CPU usage, I have to keep killing it, its running about 46% constantly.
I have Windows 10 Pro, 20H2, build 19042.662
Any ideas would be helpful.
Thanks
-
Just installed 2021 v20.00.63
Now, when I add to queue, with or without using always use queue.
The powerarc starter opens up in notification bar.
and that’s it, no matter how many files I add to queue, no compression will start.
I also cannot double click or right click the icon.
If i end task for this, and disable queuing, compression works fine, just that I have to manually start individual tasks.
it’s quite ironic that you guys took whole year to fix one issue, in this versions, which completely broke the queuing feature.
Did you guys test it before releasing?
-
Hi,
You can obtain the original file from here:
https://pcsupport.lenovo.com/in/en/products/laptops-and-netbooks/lenovo-y-series-laptops/y50-70-notebook-lenovo/80ej/59428436/cb32343883/downloads/driver-list/component?name=Power%20Management
For Lenovo Y50-70 win 7 x64 bit, power management, get lenovo energy management
Run the exe it will extract the installable drivers to C:\drivers
I tried to compress the whole folder using PA using following parameters:
Extreme, strong optimize.
image_2020-12-27_195344.pngThis resulted in negative compression.
However same file is compressed by 7zip alpha, with positive compression:
PA Negative compression.png
I understand that there are different algorithms, parameters used, and totally different software with unique sets of logics programmed, but see if compression algo can be optimized for such files.
-
Over the last few months, I’ve been trying to track down the cause of a hanging bug in PA.
I have found a reliable test case (on my computer at least).I am trying to extract the folders/files from: https://github.com/codereader/DarkRadiant/releases/download/2.9.0/windeps.7z
By selecting both folders, then dragging over to a Windows Explorer window on another HDD.
I’m not sure what causes this but this just doesn’t do anything, progress bar appears, but nothing happens.
PA shows about 5% CPU utilization and I’ve left this going all night and it never does anything.
It doesn’t always happen, but this morning this is reliably failing for me.
The folder I’m dragging to is under Git source control, but this also happens when dragging into other folders also, but not always, sometimes it works.If I do a regular extraction and use the dialog box to select the location to extract to, that always works.
Windows 10 64bit Pro 20H2 (19042.630)
Ryzen 3900X
Anti Virus is built in Windows Security only.I captured a dump of the running process if that helps: https://drive.google.com/file/d/1WLzHG_fOAMtzGMMFLHlIElnQXhsoPyYd/view?usp=sharing
-
Hi.
I have noticed after updating PowerArchiver through PatchBeam to 20.00.63, after the installer finished and I recheck for updates, it still tells me that I have version 20.00.62 installed and prompts to download 20.00.63 again.
This also happens when I install from the offline setup file powarc200063.exe ( https://powerarchiverdl.cachefly.net/2021/powarc200063.exe ). It still installs version 20.00.62 and the process goes over and over again.
Also, in PowerArchiver About screen I see version 20.00.62 but in Programs and Features in Windows 10, version 20.00.63 is displayed as being installed.
Can someone check and see if they experience similar behavior?
Thank you!
-
When I double click on a file within an archive the file gets temporarily extracted to being opened with the external program. When I now go back to the windows explorer and want to open another archive while the file from the first archive is still being extraceted, a new window of power archiver opens and immediatly closes. It opens and closes the new window repeatedly until the extraction of the file from the first archive is completed.
I use the option that power archiver opens a new tab when another archive is opened.
This happend with version 20.00.60. I wanted to update it to 20.00.63 as shown in the update window but it just updates to 20.00.62. It still shows that 20.00.63 is available but never seem to update to that version. The bug still exists though.
-
I have some large zip files (~ 40 MB) with a lot of html files. When I double click on one of them in the archive, it takes a long time (eg 20 sec) for the file to be extracted and opened in the browser.
I am using version 19.00.59.
I discovered that the root cause of the problem is that all the files in the archive are extracted to the temporary dir before the selected file is launched.
It does not appear to happen with other file types (such as pdf) nor when dragging a html file into the browser.
I think I recall this issue being raised by someone else, but could not find it.
-
On PowerArchiver 2021 (20.00.60) and windows 10, Both options in the windows explorer shell extension, “Compress to …zip” and “Compress to …zipx” create a .zipx file. ¿Its this intended?
-
My slow ring still reads as 19.00.59… will it ever offer an update to 2021 or is that something I must do manually?
-
Hello there,
I was installing-uninstalling and reinstalling PA 2021 due to another bug when I noticed a minor popup “bug” if it is considered a bug, regarding application association with recommended formats.
During PA installation you get to choose those options
Installation 1.pngI have ticked Associate PA with recommended formats
Installation completes and when you open PA the defult theme is Windows Ribbon.
When I changed it to Classic Theme, PA restarts for changes to take effect and then I get the below popup (Sorry I have a greek system)
It asks: Do you want PA to associate with recommended formats now?
Options: Associate for all users and Never show again.
Popup 2.pngI could swear that once I was changing themes and icons all the time to see which one I prefered and also toggling PA.exe to run as admin and windows compatibility mode and got this popup twice or tripple times.
Well this one does not bother me at all, I just posted it for the records if needed! -
If I the Configuration > View > Standard > Disable Tabs option is checked, when double clicking inside archives on files supported by the internal viewer (PDF, JPEG etc.) they are opened in associated application rather than on a new tab in PA internal viewer, which is expected behavior.
Next, if the Configuration > Miscellaneous > General > Reuse PA Windows is unchecked, when double clicking on archives associated with PA in Explorer they are opened in new PA instance when there is another one already running, which is expected behavior.
But when Configuration > View > Standard > Disable Tabs option is checked AND Configuration > Miscellaneous > General > Reuse PA Windows is unchecked, when double clicking inside archives on archive files they are opened in the same instance of PA with no way to get back to the parent archive. I would expect, that when the user doesn’t want to use tabs AND want to use multiple PA instances, that in such case double clicking on archive located inside another archive, the second one would open in a new PA window. -
I’ve made the sections of the output bold to indicate where the typo is.
Version 7 output
Commands:a : add files to archive (default)
u : update files to archive
h : freshen files in archive
m : move files to archive (files only)
d : delete files from archiver : recurse subfolders
Version 9 output…
p|P : store relative Pathnames|store full Pathnames
PP : store full Pathnames including drive
c[0,1,2,10,11,13,15,17,19,l,p,w,b,d,z] : set compression level
(0 - store; 1 - normal ; 2 - maximal)
(10 - store, 11 - super fast, 13 - fast, 15 - normal, 17 - max, 19 - ultra
(l - use LZMA, p - use PPMd, w - use WavPack, b - use BZIP2, d - use Deflate
(z - use optimized compression method based on file exstension)
g : create Solid archive (7Z format only)
Commands:a : add files to archive (default)
u : update files to archive
h : freshen files in archive
m : move files to archive (files only)
d : delete files from archiver : recurse subfolders
P : store full Pathnames
PP : store full Pathnames including drive
p : store relative Pathnames
c[0,1,2,10,11,12,13,14,15,16,17,18,19,u,l,p,w,b,d,z] : set compression level
(0 - store; 1 - normal ; 2 - maximal)
(10 - store, 11 - super fast, 13 - fast, 15 - normal, 17 - max, 19 - ultra
(l - use LZMA, p - use PPMd, w - use WavPack, b - use BZIP2, d - use Deflate
(o - use LZMA2
(u - use pLZMA4, f - use ZSTD, k - use PPMd_sh, e - use Deflate64
(z - use optimized strong compression method based on file exstension)
(x - use optimized fast compression method based on file exstension)
(m<filters|methods> - use custom set of filters and methods for .PA archive
y[r|b|d|x|p|d] - filters reflate, bcj2, x64flt, rep, delta
ypc<size> - custom rep c size
ypm<size> - custom rep mem size
yrx<size> - custom reflate zlib level (1-9)
yt{x} - number of threads
ya - debug mode
mt : set multithreading on
g : create Solid archive (7Z format only)
PowerArchiver Toolbox 2016 [16.00.46] => right-click crashes of Explorer.exe etc.
-
Hi,
I bought the PowerArchiver Toolbox 2016 [16.00.46] via here: Click
When I right-click a file / folder / shortcut etc.pp. via Desktop, File-Explorer, Total Commander Ultima Prime etc.pp., then I get pretty much every 2nd time a “blabla had to be closed” - Error and the Explorer.exe restarts itself or closes the File-Explorer / Total Commander Ultima Prime if I’m lucky or completely takes off me the ability to right-click.
Faulting application name: explorer.exe, version: 10.0.11099.1000, time stamp: 0x56918bfb
Faulting module name: PASHLEXT64.DLL, version: 16.0.6.1, time stamp: 0x567a6bc2
Exception code: 0xc0000005
Fault offset: 0x00000000000306f1
Faulting process ID: 0x4ea4
Faulting application start time: 0x01d1526a75a9c9d4
Faulting application path: C:\WINDOWS\explorer.exe
Faulting module path: C:\Program Files (x86)\PowerArchiver\PASHLEXT64.DLL
Report ID: b1dfdd24-4949-4562-ac65-29f83f5b9cec
Faulting package full name:
Faulting package-relative application ID:-
System
-
Provider
[ Name] Application Error
- EventID 1000
[ Qualifiers] 0
Level 2
Task 100
Keywords 0x80000000000000
- TimeCreated
[ SystemTime] 2016-01-19T03:55:54.964936700Z
EventRecordID 2671
Channel Application
Computer MOTHER-PC
Security
- EventData
explorer.exe
10.0.11099.1000
56918bfb
PASHLEXT64.DLL
16.0.6.1
567a6bc2
c0000005
00000000000306f1
4ea4
01d1526a75a9c9d4
C:\WINDOWS\explorer.exe
C:\Program Files (x86)\PowerArchiver\PASHLEXT64.DLL
b1dfdd24-4949-4562-ac65-29f83f5b9cecDXDIAG: Click
I have no issues with other stuff.
:confused:
-
-
Please try build 53 - http://www.powerarchiver.com/forums/showpost.php?p=34606&postcount=62
-
Please try build 53 - http://www.powerarchiver.com/forums/showpost.php?p=34606&postcount=62
Thanks for your help, but it didn’t solve the issue unfortunately.
Here are the errors for the different tries:
Total Commander v8.52a / Total Commander Ultima Prime v7.0:
Faulting application name: TOTALCMD64.EXE, version: 8.5.2.1, time stamp: 0x00000000
Faulting module name: PASHLEXT64.DLL, version: 16.0.8.1, time stamp: 0x568fd3b0
Exception code: 0xc0000005
Fault offset: 0x00000000000306f1
Faulting process ID: 0x2be0
Faulting application start time: 0x01d152af85c0558f
Faulting application path: C:\Program Files (x86)\TC UP\TOTALCMD64.EXE
Faulting module path: C:\Program Files (x86)\PowerArchiver\PASHLEXT64.DLL
Report ID: 227c0e69-6aca-483a-9f5e-2ec2a3574484
Faulting package full name:
Faulting package-relative application ID:-
System
-
Provider
[ Name] Application Error
- EventID 1000
[ Qualifiers] 0
Level 2
Task 100
Keywords 0x80000000000000
- TimeCreated
[ SystemTime] 2016-01-19T12:39:27.093038300Z
EventRecordID 3024
Channel Application
Computer MOTHER-PC
Security
- EventData
TOTALCMD64.EXE
8.5.2.1
00000000
PASHLEXT64.DLL
16.0.8.1
568fd3b0
c0000005
00000000000306f1
2be0
01d152af85c0558f
C:\Program Files (x86)\TC UP\TOTALCMD64.EXE
C:\Program Files (x86)\PowerArchiver\PASHLEXT64.DLL
227c0e69-6aca-483a-9f5e-2ec2a3574484File Explorer:
Faulting application name: Explorer.EXE, version: 10.0.11099.1000, time stamp: 0x56918bfb
Faulting module name: PASHLEXT64.DLL, version: 16.0.8.1, time stamp: 0x568fd3b0
Exception code: 0xc0000005
Fault offset: 0x00000000000306f1
Faulting process ID: 0x249c
Faulting application start time: 0x01d152af7632a073
Faulting application path: C:\WINDOWS\Explorer.EXE
Faulting module path: C:\Program Files (x86)\PowerArchiver\PASHLEXT64.DLL
Report ID: 0c4ecb2e-7165-4091-85c1-e5c0c29a2e42
Faulting package full name:
Faulting package-relative application ID:-
System
-
Provider
[ Name] Application Error
- EventID 1000
[ Qualifiers] 0
Level 2
Task 100
Keywords 0x80000000000000
- TimeCreated
[ SystemTime] 2016-01-19T12:40:38.221749200Z
EventRecordID 3026
Channel Application
Computer MOTHER-PC
Security
- EventData
Explorer.EXE
10.0.11099.1000
56918bfb
PASHLEXT64.DLL
16.0.8.1
568fd3b0
c0000005
00000000000306f1
249c
01d152af7632a073
C:\WINDOWS\Explorer.EXE
C:\Program Files (x86)\PowerArchiver\PASHLEXT64.DLL
0c4ecb2e-7165-4091-85c1-e5c0c29a2e42Desktop Shortcut:
Faulting application name: SystemSettingsBroker.exe, version: 10.0.11099.1000, time stamp: 0x56918de6
Faulting module name: SettingsHandlers_Notifications.dll, version: 10.0.11099.1000, time stamp: 0x56918ea0
Exception code: 0xc0000005
Fault offset: 0x000000000002a551
Faulting process ID: 0x2598
Faulting application start time: 0x01d152b3a5fc09b6
Faulting application path: C:\Windows\System32\SystemSettingsBroker.exe
Faulting module path: C:\Windows\System32\SettingsHandlers_Notifications.dll
Report ID: c4cdc306-4e6a-4608-9ae2-4efb595df3bf
Faulting package full name:
Faulting package-relative application ID:-
System
-
Provider
[ Name] Application Error
- EventID 1000
[ Qualifiers] 0
Level 2
Task 100
Keywords 0x80000000000000
- TimeCreated
[ SystemTime] 2016-01-19T12:40:55.901450000Z
EventRecordID 3029
Channel Application
Computer MOTHER-PC
Security
- EventData
SystemSettingsBroker.exe
10.0.11099.1000
56918de6
SettingsHandlers_Notifications.dll
10.0.11099.1000
56918ea0
c0000005
000000000002a551
2598
01d152b3a5fc09b6
C:\Windows\System32\SystemSettingsBroker.exe
C:\Windows\System32\SettingsHandlers_Notifications.dll
c4cdc306-4e6a-4608-9ae2-4efb595df3bfFaulting application name: explorer.exe, version: 10.0.11099.1000, time stamp: 0x56918bfb
Faulting module name: PASHLEXT64.DLL, version: 16.0.8.1, time stamp: 0x568fd3b0
Exception code: 0xc0000005
Fault offset: 0x00000000000306f1
Faulting process ID: 0x3714
Faulting application start time: 0x01d152b6a3945c51
Faulting application path: C:\WINDOWS\explorer.exe
Faulting module path: C:\Program Files (x86)\PowerArchiver\PASHLEXT64.DLL
Report ID: f2390bbd-b321-4e12-9997-355db62ff9c6
Faulting package full name:
Faulting package-relative application ID:-
System
-
Provider
[ Name] Application Error
- EventID 1000
[ Qualifiers] 0
Level 2
Task 100
Keywords 0x80000000000000
- TimeCreated
[ SystemTime] 2016-01-19T12:43:07.898766600Z
EventRecordID 3032
Channel Application
Computer MOTHER-PC
Security
- EventData
explorer.exe
10.0.11099.1000
56918bfb
PASHLEXT64.DLL
16.0.8.1
568fd3b0
c0000005
00000000000306f1
3714
01d152b6a3945c51
C:\WINDOWS\explorer.exe
C:\Program Files (x86)\PowerArchiver\PASHLEXT64.DLL
f2390bbd-b321-4e12-9997-355db62ff9c6All apps / tools are bought. No cracks etc.pp.
:confused:
-
-
Can you try uninstalling PA 2016, rebooting and then installing it again please?
Thank you!
-
As a fast workaround, can you please set language manually to English or other language you might be using. This is in Options> Language.
After that check it out, it should be working.
-
Please check this release:
http://dl.powerarchiver.com/2016/powarc160055.exeAnd let us know how it goes… should be fixed. Thank you.
-
Please check this release:
http://dl.powerarchiver.com/2016/powarc160055.exeAnd let us know how it goes… should be fixed. Thank you.
Thanks a lot for your help !
v16.00.55 doesn’t have the right-click issues anymore.
:)
-
Thanks a lot for your help !
v16.00.55 doesn’t have the right-click issues anymore.
:)
thanks, this was due to automatic language selection and we fixed it in one of the internal releases but it came back… since we already knew what it was and we noticed it day before, we were able to quickly fix.
-
thanks, this was due to automatic language selection and we fixed it in one of the internal releases but it came back… since we already knew what it was and we noticed it day before, we were able to quickly fix.
Awesome work !
:)
