updates

[Tyjen007]

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.

[Luxor]

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.

[Tyjen007]

@Tyjen007

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:

[spwolf]

@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!

[Luxor]

@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!

[spwolf]

@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?

[Luxor]

@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.

[spwolf]

@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.

[Luxor]

Three days of use with these changed options and no explorer crashes so far.

[spwolf]

@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!

[Tyjen007]

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.

[spwolf]

@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!

[Luxor]

@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?

[spwolf]

@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.

[Luxor]

@spwolf Thanks, it’s good to know these sort of things. :)

[Tyjen007]

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.

[spwolf]

@Tyjen007 did you check latest .55 release via patchbeam?

[spwolf]

17.09.0 is latest dll, lets see what happens with that one. Thanks!

[Tyjen007]

Thank you I’ll try that version.

[spwolf]

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.

[Tyjen007]

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.

[spwolf]

@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!

[Tyjen007]

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

[Luxor]

@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?

[spwolf]

@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.

[Luxor]

@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.

[spwolf]

@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!

[Tyjen007]

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.

[spwolf]

@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.

[Tyjen007]

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.

[Tyjen007]

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.

[spwolf]

@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.