-
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! -
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,
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
-
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 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?
-
-
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)
An issue with 2010 Pro version
-
Hi guys
I love the new PA and I am using the beta 11.50.49
I have a Pentium Quad Core 2.4 GHz with 4 gb of ram and PA 2010 takes anywhere between 10 to 12 seconds to start.
I know it is a beta program but I am wondering whether this is an issue that other ppl are experiencing or if it is an issue that is gettign looked at.
Thank you very much
Mame
-
Try this version:
http://www.powerarchiver.com/test/alpha115/powarc1150rc5.exeLet us know if that helps.
-
if that above doesnt work, then it is definetly not reported before. What happens when you:
1. Options> Reset to defaults
2. delete HKCU\Software\PowerArchiver key (complete).does that change anything?
-
if it would be extra cool if you could check this out before night is at its peak :-).
-
:-O hint dropping!!!
-
k
update
Uninstalled the old version. Rebooted (as per uninstaller instructions).
Installed the version u linked. Rebooted
Ran again
Fist startup 5 seconds.
Subsequent startups ~3 seconds.Better.
A clarification for the problem before:
Only the first startup per windows session was really slow. Subsequent ones were about 5 seconds.
Currently, it still seems slow compared to the way 2009 ran but i know it’s beta and I can live with it.
Gonna try the registry trick now will reply in a few.
Mame
-
P.S. OS is Vista 64 bit SP1.
Might upgrade to SP2 soon.
Mame
-
I can’t find the registry key you mentioned.
Does the registry of Vista 64 bit store it in a different place? I tried to run a search in regedit and I am lost in a sea of stuff I am not sure I should be touching O_O
Mameluke
-
there will be nothing different in final version :-).
(another hint? :P)Not sure if it should be faster or slower than PA 2009, i think when it comes to that, they should be very similar with same settings.
But i do believe that shell extensions startup is now a lot faster than before, and of course, actual speed of compression is much better (dare I say 4x on your quad core? :P).
What you had in RC2 was issue with one of the most recently used archives being on network drive and PA waiting for network drive to respond, this was fixed in internal RC5.
-
I can’t find the registry key you mentioned.
Does the registry of Vista 64 bit store it in a different place? I tried to run a search in regedit and I am lost in a sea of stuff I am not sure I should be touching O_O
Mameluke
This is exact key:
HKEY_CURRENT_USER\Software\PowerArchiverjust right click on it and hit delete. Yikes!
-
K figured it out and deleted it.
PA opens in 2 seconds now :(
Annoying nag screen adding delays……or registered but slow to load.
Stuck between a rock and a hard place :(
Mame
-
K figured it out and deleted it.
PA opens in 2 seconds now :(
Annoying nag screen adding delays……or registered but slow to load.
Stuck between a rock and a hard place :(
Mame
register it again and see if it changes…. it becomes 3 seconds?
-
registration is the same as in PA 2009, nothing changed there.
What changed, and made PA 2010 slightly slower than PA 2009 was that compression engine is now loaded from the start up vs loading when used in PA 2009. So that adds slight delay at the start where that delay was previously there when you started adding or extracting from archives in PA 2009.
-
I re-registered and rebooted.
Back to 5 seconds and 2.5-3 seconds after that.
Keep in mind that I lost my custom button arrangement (not using any outside skin or anything just had my button setup in my own way in the configuration menu) when i deleted the registry key so that may be a factor.
I need to catch the Zzzz train so this will be my last post for the night.
Once more to recap:
2.4 Ghz Quad core
4 gig ram
Vista 64bit SP1
Got the latest updates for the OS (minus SP2).Cheers and I hope you guys can get to the bottom of this.
<3
Mame
-
I re-registered and rebooted.
Back to 5 seconds and 2.5-3 seconds after that.
Keep in mind that I lost my custom button arrangement (not using any outside skin or anything just had my button setup in my own way in the configuration menu) when i deleted the registry key so that may be a factor.
I need to catch the Zzzz train so this will be my last post for the night.
Once more to recap:
2.4 Ghz Quad core
4 gig ram
Vista 64bit SP1
Got the latest updates for the OS (minus SP2).Cheers and I hope you guys can get to the bottom of this.
<3
Mame
yeah, that obviously makes the difference (not having any options than default).
Its unclear to me if took 2 seconds first time and then 2 seconds afterwards so difference was between 5 and 2 seconds, or if difference was between 2 and 3 seconds :-).
Also, when you re-registered (no need to rebot) did you keep rest of the settings default or?
-
Once the registry entry was removed:
It took around 2 seconds for both first as well as subsequent starts.
Once registered with the new Rc5:
5 seconds first start 2.5-3 seconds subsequent starts
Seems to be something related to the registry for sure.
Mame
-
Update:
I never usually turn off my computer.
I ran PA just now to double check and first run was 12 seconds again. ~2 seconds for the subsequent runs.
I really dunno what is happening anymore. Am i the only one with this issue?
Mame
-
My startup times appear to be 3-5 seconds on my laptop, I haven’t timed it on my desktop.
-
Yes my settings were on default.
Now I have changed them and registered and it’s back to slooooooooow mode :(
Yuck :(
Mame
-
Yes my settings were on default.
Now I have changed them and registered and it’s back to slooooooooow mode :(
Yuck :(
Mame
12 seconds again or?
-
yes 12 seconds.
I leave my computer on as I mentioned and I guess after a while (number of hours) it “resets” back to 12 seconds on the first run and then a few seconds for the subsequent runs. This will repeat the next day when I come back from work so no way to know how many hour until the next "reset"back to 12 sec.
It’s something to do with the custom bars ( I use the classic buttons NOT the ribbon btw) and/or the registration. I do hope you guys get to the bottom of this.
As a comparison the latest Winrar beta fires up in under 1 second.
Good luck
Mame
-
you have explorer view on? It could be something like your hard drive coming out of sleep mode?
You can send us your registry settings (HKCU\Software\PowerArchiver), zipped, to support @ conexware . com.
-
I sent them in and I got some automated response. Hope you got them
Also: I disabled any type of power saving features. I have everythign on at all times. Monitor and HD.
Mame
-
Updates:
I have upgraded to Service Pack 2 (It was time)
A cold start is now 5 seconds and the subsequent one about 2 seconds.
Did the registry keys I sent reveal anything?
Mame
-
Updates:
I have upgraded to Service Pack 2 (It was time)
A cold start is now 5 seconds and the subsequent one about 2 seconds.
Did the registry keys I sent reveal anything?
Mame
nope, nothing interesting there. So you dont get that 12 seconds delay after you leave computer for several hours?
-
No but like I said I no longer have SP1 now I upgraded to Vista SP2. That may have somethign to do with it.
Mame
-
Weird.
Anyway, here is one of the last pre-release versions:
http://www.powerarchiver.com/test/release10/powarc1150final.exeWe worked hard to improved startup speed, it should be noticable in older computers, depending on settings used, this is now 30% faster at startup.
-
With the new version I got a 4 second first start and instant subsequent starts.
Mame
Edit: Spelling
-
With the new version I got a 4 second first start and instant subsequent starts.
Mame
Edit: Spelling
good…