-
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?
-
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)
SOLVED Windows 10 pro - Explorer crashing
-
I started having Windows explorer crash for no obvious reason, I even did a re-install of the OS. I could not replicate the exact action, that made explorer crash, it seems random. I have over time updated versions and today having check event logs I found “PASHLEXT64.DLL” to be at fault. I have uninstalled powarc170048 and are now trying powarc170050. below is copy of event log relating to crash.
Faulting application name: explorer.exe, version: 10.0.14393.479, time stamp: 0x58258a90
Faulting module name: PASHLEXT64.DLL_unloaded, version: 17.0.8.1, time stamp: 0x588786cc
Exception code: 0xc0000005
Fault offset: 0x00000000000f3970
Faulting process id: 0x2fac
Faulting application start time: 0x01d287e476cc7480
Faulting application path: C:\WINDOWS\explorer.exe
Faulting module path: PASHLEXT64.DLL
Report Id: d1e246b4-12e2-4de3-8e78-b45b3c4035e2
Faulting package full name:
Faulting package-relative application ID:I hope this helps.
-
I’ve seen instances of Windows Explorer restarting lately, noticeable by icons disappearing from notification area.
I didn’t even think that PA may have been the cause of it, but yes looking in the events log I see the same report as you.
Good catch. -
Add more crashes, running windows 10 pro 1607 build 14939.693.
Faulting application name: explorer.exe, version: 10.0.14393.479, time stamp: 0x58258a90
Faulting module name: PASHLEXT64.DLL_unloaded, version: 17.0.8.1, time stamp: 0x588786cc
Exception code: 0xc000041d
Fault offset: 0x00000000000f3970
Faulting process id: 0x1624
Faulting application start time: 0x01d28928b6e20165
Faulting application path: C:\WINDOWS\explorer.exe
Faulting module path: PASHLEXT64.DLL
Report Id: 6f828dcc-1190-4b7a-bf66-ae79ee30646c
Faulting package full name:
Faulting package-relative application ID:Faulting application name: explorer.exe, version: 10.0.14393.479, time stamp: 0x58258a90
Faulting module name: PASHLEXT64.DLL_unloaded, version: 17.0.8.1, time stamp: 0x588786cc
Exception code: 0xc0000005
Fault offset: 0x00000000000f3970
Faulting process id: 0x1624
Faulting application start time: 0x01d28928b6e20165
Faulting application path: C:\WINDOWS\explorer.exe
Faulting module path: PASHLEXT64.DLL
Report Id: 95f19e94-9eab-4890-99ef-2698208f5070
Faulting package full name:
Faulting package-relative application ID: -
@Tyjen007 @Luxor We have been playing with this lately, it should be a focus for one of the future builds. Until then, please check Shell options, and uncheck Enable Archive Hints and Enable Archive Property Sheets. That seems to be causing it, but it is hard to catch for now.
Please uncheck those and lets see what happens. Thank you!
-
@spwolf said in Windows 10 pro - Explorer crashing:
We have been playing with this lately, it should be a focus for one of the future builds. Until then, please check Shell options, and uncheck Enable Archive Hints and Enable Archive Property Sheets. That seems to be causing it, but it is hard to catch for now.
Not helped by being so random I would imagine.
I think I’ve mostly noticed it happening after I have been using PA and my external usb drive at the same time. When I click on the usb icon in the notification area to remove the drive, that’s when it occurs.
@spwolf said in Windows 10 pro - Explorer crashing:
Please uncheck those and lets see what happens. Thank you!
Done!
-
@Luxor said in Windows 10 pro - Explorer crashing:
@spwolf said in Windows 10 pro - Explorer crashing:
We have been playing with this lately, it should be a focus for one of the future builds. Until then, please check Shell options, and uncheck Enable Archive Hints and Enable Archive Property Sheets. That seems to be causing it, but it is hard to catch for now.
Not helped by being so random I would imagine.
I think I’ve mostly noticed it happening after I have been using PA and my external usb drive at the same time. When I click on the usb icon in the notification area to remove the drive, that’s when it occurs.
@spwolf said in Windows 10 pro - Explorer crashing:
Please uncheck those and lets see what happens. Thank you!
Done!
yeah, it happens only sometimes. Did you have any occurance since you changed those options?
-
@spwolf said in Windows 10 pro - Explorer crashing:
Did you have any occurance since you changed those options?
Not so far, will probably have a better idea if it helps after a few days of use.
-
@Luxor said in Windows 10 pro - Explorer crashing:
@spwolf said in Windows 10 pro - Explorer crashing:
Did you have any occurance since you changed those options?
Not so far, will probably have a better idea if it helps after a few days of use.
thanks, we will likely have a special debug for dll by end of next week.
-
Three days of use with these changed options and no explorer crashes so far.
-
@Luxor said in Windows 10 pro - Explorer crashing:
Three days of use with these changed options and no explorer crashes so far.
good to know… next update will have these disabled in the code + soon enough I expect us to have debug dlls that give us hopefully enough information. Thanks!
-
Just applied the directions will reboot and give it a few days testing before further comments. random crashing has been ongoing, hopefully this fix is the answer. Also of note in my case, “enable archive hints” was enabled so I disabled it. “enable archive property sheets” was already unchecked. So at present only “use explorer shell extensions” and enable explorer preview" are left enabled.
-
@Tyjen007 please check patchbeam, fast ring update and you will get latest release - .55. It has these disabled internally, and lets see what happens. Thank s a lot!
-
@spwolf said in Windows 10 pro - Explorer crashing:
It has these disabled internally
Does that mean if we selected them that they would do nothing, or does it mean that if you have them selected it will deselect them?
-
@Luxor said in Windows 10 pro - Explorer crashing:
@spwolf said in Windows 10 pro - Explorer crashing:
It has these disabled internally
Does that mean if we selected them that they would do nothing, or does it mean that if you have them selected it will deselect them?
It won’t do anything… Sometimes when you uncheck it, parts of code are still working since it is part of same dll. So this is truer off.
-
@spwolf Thanks, it’s good to know these sort of things. :)
-
2-25-2017 11.44.47am crash…
Faulting application name: explorer.exe, version: 10.0.14393.479, time stamp: 0x58258a90
Faulting module name: PASHLEXT64.DLL_unloaded, version: 17.0.8.1, time stamp: 0x588786cc
Exception code: 0xc000041d
Fault offset: 0x00000000000f3970
Faulting process id: 0x2ac4
Faulting application start time: 0x01d28f8399fd117c
Faulting application path: C:\WINDOWS\explorer.exe
Faulting module path: PASHLEXT64.DLL
Report Id: e8f0bc40-6357-4c3b-a096-daabe711d702
Faulting package full name:
Faulting package-relative application ID:Just checked shell extension options in PowerArchiver:
check = use explorer shell extensions
check = enable explorer preview
uncheck = enable archive hints
uncheck = enable archive property sheets.I don’t use the preview pane in windows explorer at, I only use the details pane.
I’m going to turn off the "enable explorer preview option in PowerArchiver and see if that stops the crashes. Will update. -
@Tyjen007 did you check latest .55 release via patchbeam?
-
17.09.0 is latest dll, lets see what happens with that one. Thanks!
-
Thank you I’ll try that version.
-
we had report from @keith via email that we could be reproduced and could be similar to this… hopefully it is. Spent whole day troubleshooting it, we are getting closer but still not fixed. Maybe new build with fix tomorrow? We will see. Thanks for reports.
-
Looking forward to new update.
Still running latest built powarc170055
Side note:
I now run windows explorer option “launch folder windows in a separate process”, this helps, since the fault is random. Now it does not crash all “windows explorer” windows that are open, just the process “window” that it does crash in.
Also I went for and are now using Windows 10 pro 15048.rs2_release. 170228-1522, mainly to see if PowerArchiver behaved with no issue in newer build. As it stands I have had few crashes but not as many as running the existing version in general use.I’ll post crash info if it starts being too regular again.
-
@Tyjen007 said in Windows 10 pro - Explorer crashing:
Looking forward to new update.
Still running latest built powarc170055
Side note:
I now run windows explorer option “launch folder windows in a separate process”, this helps, since the fault is random. Now it does not crash all “windows explorer” windows that are open, just the process “window” that it does crash in.
Also I went for and are now using Windows 10 pro 15048.rs2_release. 170228-1522, mainly to see if PowerArchiver behaved with no issue in newer build. As it stands I have had few crashes but not as many as running the existing version in general use.I’ll post crash info if it starts being too regular again.
we managed to reproduce one issue even with latest build. So we have made some changes and they will be available in next build. Lets see if it crashes ever again. We are waiting for few other things to come in and it will be published then. Thanks!
-
these crashes noted below are when doing a right click (copy and then paste) before competing operation, crash occured…
Faulting application name: explorer.exe, version: 10.0.15048.0, time stamp: 0xa6dd583e
Faulting module name: PASHLEXT64.DLL_unloaded, version: 17.0.9.0, time stamp: 0x58a6fb56
Exception code: 0xc0000005
Fault offset: 0x00000000000f38e0
Faulting process id: 0x3378
Faulting application start time: 0x01d296a3856ca7d2
Faulting application path: C:\WINDOWS\explorer.exe
Faulting module path: PASHLEXT64.DLL
Report Id: 8328a8ee-76cc-4c9a-a960-2871661fff0b
Faulting package full name:
Faulting package-relative application ID:Faulting application name: explorer.exe, version: 10.0.15048.0, time stamp: 0xa6dd583e
Faulting module name: PASHLEXT64.DLL_unloaded, version: 17.0.9.0, time stamp: 0x58a6fb56
Exception code: 0xc0000005
Fault offset: 0x00000000000f38e0
Faulting process id: 0x3378
Faulting application start time: 0x01d296a3856ca7d2
Faulting application path: C:\WINDOWS\explorer.exe
Faulting module path: PASHLEXT64.DLL
Report Id: 8328a8ee-76cc-4c9a-a960-2871661fff0b
Faulting package full name:
Faulting package-relative application ID:times are 2 seconds apart
-
@spwolf said in Windows 10 pro - Explorer crashing:
We are waiting for few other things to come in and it will be published then.
Shall we enable them now in build 17.00.57 or is it too soon?
-
@Luxor said in Windows 10 pro - Explorer crashing:
@spwolf said in Windows 10 pro - Explorer crashing:
We are waiting for few other things to come in and it will be published then.
Shall we enable them now in build 17.00.57 or is it too soon?
there is .59, now it is really completely disabled by default. It seems like loading our dll into shell for display of files with latest Win10 causes crash… just loading the dll without actually using it. So MS changed something in past 3 months, maybe it is a bug or maybe it is a security feature, we dont know right now. But there should be no crashing anymore.
-
@spwolf said in Windows 10 pro - Explorer crashing:
there is .59
Didn’t notice that, just got it on patchbeam.
@spwolf said in Windows 10 pro - Explorer crashing:
now it is really completely disabled by default. It seems like loading our dll into shell for display of files with latest Win10 causes crash… just loading the dll without actually using it. So MS changed something in past 3 months, maybe it is a bug or maybe it is a security feature, we dont know right now. But there should be no crashing anymore.
I’ve not had a single crash in explorer since it was disabled that’s for sure.
-
@Luxor said in Windows 10 pro - Explorer crashing:
@spwolf said in Windows 10 pro - Explorer crashing:
there is .59
Didn’t notice that, just got it on patchbeam.
@spwolf said in Windows 10 pro - Explorer crashing:
now it is really completely disabled by default. It seems like loading our dll into shell for display of files with latest Win10 causes crash… just loading the dll without actually using it. So MS changed something in past 3 months, maybe it is a bug or maybe it is a security feature, we dont know right now. But there should be no crashing anymore.
I’ve not had a single crash in explorer since it was disabled that’s for sure.
We found some way to reproduce it when just right clicking on .pa file which just loads the dll. And some other users reported it happening with zip and 7z files too. All this worked fine for years in Win7, 8 and 10. And on our main build computer, with final Win 10.1 build, it never crashes either. So it is one of the builds afterwards that changed something.
Since .59 release disabled it in .zip/.7z and all other formats, there are no more issues report by any of the users we sent it to. So definitely something on MS side.
Once PA 2017 is released in final form, we can spend some time investigating the issue. Thanks!
-
Looking forward to trying 59 version. I will say I have seen less crashes in the latest Insider preview Windows 10, that may also just be a side effect of using newer versions of the program. When I do get crashes I have verified that PASHLEXT64.DLL is the fault/reason. I wish it was it was as simple as saying while doing (insert action) that was the reason. And as spwolf states, this is a new bug that did not happen in prior versions of the app or OS. What is weird is you would expect the call for the DLL to be the issue when you right click on a file/ folder and the context menu would be calling the ddl for action to be offered. Yet windows explorer can crash with a open window and no active action taking taking place within the open window as your using an app. As noted above , I now run separate instances of explorer, so when one instance will crash, the other(s) will stay open. Which may mean, in the context cashing its’ is not always a system wide issue. Could that mean its how its called and held in memory for each instance? I have tried (completely disabled the context menu calls to the DLL), and had no crashes (as to be expected) but I want the functionality that is provided. rather than having to open the app and browse to the file/folder that I wish to complete a task. We’ll see what happens.
-
@Tyjen007 said in Windows 10 pro - Explorer crashing:
Looking forward to trying 59 version. I will say I have seen less crashes in the latest Insider preview Windows 10, that may also just be a side effect of using newer versions of the program. When I do get crashes I have verified that PASHLEXT64.DLL is the fault/reason. I wish it was it was as simple as saying while doing (insert action) that was the reason. And as spwolf states, this is a new bug that did not happen in prior versions of the app or OS. What is weird is you would expect the call for the DLL to be the issue when you right click on a file/ folder and the context menu would be calling the ddl for action to be offered. Yet windows explorer can crash with a open window and no active action taking taking place within the open window as your using an app. As noted above , I now run separate instances of explorer, so when one instance will crash, the other(s) will stay open. Which may mean, in the context cashing its’ is not always a system wide issue. Could that mean its how its called and held in memory for each instance? I have tried (completely disabled the context menu calls to the DLL), and had no crashes (as to be expected) but I want the functionality that is provided. rather than having to open the app and browse to the file/folder that I wish to complete a task. We’ll see what happens.
Yes, the compression dll is loaded for preview shell function only, but it is loaded first time you right click on shell. And new builds of Win10 dont like it. Same dll has been used for ever since we added that functionality.
.59 is on Patchbeam and you can try it to confirm thats it.
In one of the future builds, we will add preview functionality back in, but we will not use external dll anymore for these functions, but we will build it inside initial .dll, since even if Microsoft fixes the issue (which is possible), there will still be many preview builds out there with the issue.
However rest of shell functionality is unaffected. Thanks.
-
Since Creators update is coming out soon, I decided to keep going with newer versions of the Windows 10 Pro x64 OS, I’ve been running 15055.rs2_release.170307-1445 with PowerArchiver build 59. And I started to see fewer crashes. I have just updated to 15060.rs2_release.170314-1527 along with PowerArchiver version 61. I’ll clear my event logs and watch check for issues. and report back in a few days. Thanks spwolf for feedback and a great product.
-
I’ve been checking event viewer, and have seen no crashes related to PASHLEXT64.DLL for nearly a week. I’m running PowerArchiver version 17.00.63 (03/17) 64bit and have recently upgraded to windows 10 1703 (Build 15063.rs2_release.170317-1834). What ever work that was done by ConeXware, seems to have addressed the crashing issue. Unless anything changes I would say, we can assume the issue (as far as my situation) is resolved. Thank you spwolf for your prompt responses.
-
@Tyjen007 said in Windows 10 pro - Explorer crashing:
I’ve been checking event viewer, and have seen no crashes related to PASHLEXT64.DLL for nearly a week. I’m running PowerArchiver version 17.00.63 (03/17) 64bit and have recently upgraded to windows 10 1703 (Build 15063.rs2_release.170317-1834). What ever work that was done by ConeXware, seems to have addressed the crashing issue. Unless anything changes I would say, we can assume the issue (as far as my situation) is resolved. Thank you spwolf for your prompt responses.
thank you for the feedback.
