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 ?
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.
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.
Latest version: 1.00.32
Release 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!
New version: 20.10.02
Release Notes - PowerArchiver - Version 20.10.02
[PA-2892] – Improved Support for S3 Object Storage
[PA-2783] – TXT preview does not work in preview window when opening archive in explorer mode
[PA-2787] – Scroll bar stops working correctly in tab preview after specific use
[PA-2861] – Converting to Zip(Default) in converter converts to zipx instead of zip format
[PA-2862] – Downloaded Skin does not appear correctly when first applied, until restarting PA
[PA-2867] – About screen shows unregistered in Modern interface
[PA-2868] – shell extensions extract additional folders in specific archives
[PA-2869] – App skins do not update until 2nd restart of PowerArchiver
[PA-2871] – Portable: Ribbon interface skin does not appear correctly
[PA-2872] – Span options not working correctly for PA format in Main PA and Backup
[PA-2873] – Cannot test larger 7z archives – progress dialog freezes
[PA-2874] – EXE files inside specific tar.xz extract at 0 file size
[PA-2877] – Dark letters in About and File sections in Modern Dark interface
[PA-2881] – Cannot log out of google drive in Cloud component
[PA-2882] – Email log setup password visible
[PA-2883] – Amazon S3 Cloud login information not saved
[PA-2884] – Amazon s3 cloud account key is visible in cloud configuration menu
[PA-2885] – Modern Interface: help always show unregistered
[PA-2886] – Security Vulnerability addressed in PowerArchiver
[PA-2887] – Archive comment window cannot be closed in PA interface when set to appear when opening archives
[PA-2888] – PA does not report error when online registration can not reach server due to firewall in latest Windows Update
[PA-2890] – Force Unicode not working properly – file names in archives not appearing correctly
[PA-2891] – VSS extensions field not showing in backup
[PA-2893] – Toolbar not showing properly in FTP in Classic and Ribbon
[PA-2895] – Improved handling of drag and drop mechanics and folder display in Clouds appWhats New
Various fixes and improvements. More fixes and updates coming up! Thanks for everyone’s help!
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.
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.
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:
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.
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 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
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’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).
Scheduled backups in the 57th century
I just purchased a new machine and installed PowerArchiver and set up a scheduled backup using the .pbs file I brought over from my old machine. Oddly, it scheduled the backup to occur weekly starting sometime in the 57th century (if memory serves). I ignored that at first, since I was annoyed with the OEM crud installed on the machine. So, I erased the machine and installed Windows again from scratch using my own Win7 disc.
Much to my surprise, a second install of PowerArchiver resulted in scheduling the backup again sometime in the 57th century. I looked in the .pbs file and the only thing that looks like a timestamp is FTDate (with a value of 931201024, which would be July 5, 1999). Not sure what that is.
So I went into Windows Task Scheduler and fixed it there. I hope it works :-)
While I was in there, though, I found that there were about 10 or 12 PowerArchiver entries! I don’t know what they were for, but I deleted all of them, except for my backup script. (If they should be there, I can re-install.)
Anyway, have others seen this issue? Is it related to scheduling an already existing script?
I’m using Win7 64-bit and PowerArchiver Pro 12.11.02.
maybe if you attach the pbs here we can try to reproduce it… they were all probably backup entries for that pbs, we dont use scheduler for anything else.
Sure. I just did it again and got similar results.
I’ve attached the backup script.
Here’s what I did:
- Launch PowerArchiver
- Go to Backup
- Select this backup entry (it’s the only one)
- Deleted it
- Closed PowerArchiver
- Noted the backup was still in Task Scheduler, so I deleted it from Task Scheduler, too
- Started PowerArchiver again, go to backups
- Copy my PBS file back into place (u:\lib\config\…)
- Click “Edit” and select my PBS file
- Click “Next” until I get to “Scheduling Options”. I note I can select a time, but not a date.
- I click “Advanced Options”
- I click on “Schedule” – it only gives me 3:30 on 2/10/2012 as the only option (I wish I could select the exact day)
- Click OK
- Back to The “Scheduling Options” page, I just click Next
- I see the list of files
- Click “Close”
- Backup entry does not appear in the PowerArchiver window
- So, I close PowerArchiver
- I re-start PowerArchiver
- I click on “Backup”
- The back is now there, set to start at 3:30AM on 6/9/5518. (I’m not sure why it selected a new century this time, but perhaps I am mistaken and it was 55-something before.)
I looked in Task Scheduler and I see the same year: 5518. At least they are consistent, though not was appeared when setting up the schedule.
I hope this helps. I can live with the work-around of modifying the entry in Task Scheduler directly, but there appears to be a few bugs in the scheduling area. I’ll not dismiss that it might be my machine, but it certainly is odd that I saw it twice.
That said, I had a perfectly good working pair of USB headphones that refuse to work properly on this machine. Skype complains that it cannot grab the recording device when a call comes in. Swap out headphones with a different pair – both Plantronics USB headsets, but different models – and it works. Go figure. Computers. ;-)
(I tried everything software-wise I could do to make that headset work, BTW. It was actually the frustration with the headset not working properly that I re-installed, because I was convinced that Dell must have installed some kind of crap that interfered with the USB audio driver. You know how they pre-load the machines with all kinds of stuff you’d never use, which is why it’s pre-loaded with crap: they have to give it away. I was wrong about the pre-loaded crap being at fault, but who would have thought the headset was the issue when they worked on the Win7 64-bit machine I just replaced… I’m still puzzled with that one. Everything else on the machine appears to be working, though. After the headphone experience, which I am sure are still perfectly working headphones, I dare not suggest these PowerArchiver issues have nothing to do with my hardware. I’m convinced anything is possible now.)
it seems to me that importing pbs schedule from another computer could be at fault… we will check it out and thank you for the report.
try attaching pbs now btw :-)
Sorry about missing that. I did edit and attach it. I didn’t notice that it told me the attachment type was invalid. I clicked through to quickly. :)
Let me go create one from scratch and see what happens.
hm, seems to work for me here… can you try starting PA with administrator rights and then do the same thing with pbs? Maybe it is something weird with scheduling permissions…
I went through the steps of creating a backup. I left all of the options as default, except I selected the day for the weekly backup to start tomorrow at 3:30AM. When I got done, the PBS file was created, but did not appear in the PowerArchiver window. I exited and re-restarted PowerArchiver and it appears now, again with the date 6/9/5518. At least it’s consistent.
I then did it again, selecting the time and weekly backup. However, I did NOT push the “Advanced Options” button on the “Scheduling Options” page to select the day of the week. This time, it created the backup with the correct date of today and for weekly backup. So, the problem appears to be related to trying to select the particular day of the week.
i got it… when you go to advanced settings and save them, that appears… weird! should be fixed soon. thanks!
Great! I’m feeling good to know that I don’t have another mysterious USB headset-type issue… :-)
it is always a lot easier when we can reproduce it on our end :-)
Please Patchbeam the latest update and see how it works now… thanks!