sdRohan sdRohan

Error: 'Fences has detected that Explorer was not closed properly'

▼

Error: 'Fences has detected that Explorer was not closed properly'

from Stardock Forums

EDIT 08/02/2022
Seeing that all known crash issues have been addressed within Fences 4, we are closing this thread.  If you are still using Fences 3 and experiencing crashes, please install the trial for Fences 4 to see if you still see them:

https://www.stardock.com/products/fences/download-trial

Should your issues be resolved, there is a substantial discount to upgrade to Fences 4:

https://www.stardock.com/products/fences/download

EDIT 05/19/2022

We think we might have a fix for one crash that is possible with Fences and folder portals.  Please see if the just-released beta does indeed resolve it for you and report back here either way, please.

https://forums.stardock.com/512519/fences-4059-beta-feedback-thead

Special thanks to k3nny5 for working with us in Teams to help resolve it.

EDIT 05/12/2020
Changed the process for collecting data \ crash dumps in the instructions below.

EDIT 12/23/2021
Thanks to help from user altae here, we have confirmed that if DisplayFusion is running, this can cause the issue.  If you have DisplayFusion installed, or other 3rd party multimonitor software (Actual Multiple Monitors, UltraMon, etc), please try uninstalling and a reboot. 

EDIT 12/21/2021
If you are seeing this issue on Windows 11, and have WindowBlinds installed as well, it will very likely crash.  Please uninstall WindowBlinds to see if you still have the issue.

EDIT 11/01/2021
Any post that does not directly contribute to finding the cause will likely be removed.  Also, to find said cause, the data asked for above is crucial.  If it is absent, the post will likely be removed. 

EDIT 10/25/2021
We are seeing that many PC \ OS related issues are clouding the data \ feedback received on this issue.

Prior to doing any of the below, we ask that you have 1st don't the following.

If nothing is resolved from it, please proceed with the below.

For some, when enabling Fences, they are seeing:

'Fences has detected that Explorer was not closed properly'

Specifically for them, we need more data to find the cause. 

Manually Collecting Crash Dump

We are now asking for the manual collection of crash dumps.  instructions on how to do this has been posted here:

https://forums.stardock.com/486084/fences-support-faq#CrashDumps

To help see if Fences is the cause of any crash, Fences has the capability to capture more data when there are crashes.  To enable it, the Fences registry needs to be changed.  One can do so by downloading and running this registry edit file:

https://cdn.stardock.us/support/uploads/FencesAllCrashesNew.zip

We are continuing to look into the crashing reports but we believe the number of users impacted is small at this time. That said, we take this very seriously and want to try and triage specific cases to see if there is a common denominator. 

MS Teams Collaboration

As one would suspect, this cant be done in the forums for a variety of reasons, not the least of which is we need data (startups, running services, sysinfo, etc).  To best accomplish this, we are going to set up a Microsoft Teams 'Team' \ Channel and invite clients having this issue to it.  The requirements for participation would be:

  • English speaking and preferably in the Western Hemisphere (for real-time chat)
  • Able to reproduce crashes at will with the latest version of Fences 4 (not Fences 3)
  • Are ok to submit data (startups, running services, sysinfo, etc) upon request
  • Are willing to stick with the troubleshooting process for (potentially) weeks.

If you can meet these requirements, please post as much here and I will send out invitations and instructions to you directly.

We thank you very much for your feedback and patience.

Sean Drohan
Stardock Support Manager

fences
660,730 views 284 replies
Reply #226 from Stardock Forums Top

Sean:

I had this problem on my old HP laptop and now on my brand new Alienware X17.  Have done the SFC scan and turned on extended crash reporting.

I get this error 80% or so of the time when I hit Windows-P and turn on my multimonitor setup (shared with my work computer, so I need to toggle regularly).

Other two monitors are connected via a USB-C Anker hub with 2xHDMI on it.

Please provide next steps to share my logs.

Reply #227 from Stardock Forums Top

I need a teams invite,  windows explorer keeps crashing 

 

Windows version 20h2 os build 19042.1586

Fences 3.1.3.3

Full Reinstall

Tried Fences 4 (same issue)

Ran SFC /scannow & DISM /online /cleanup-image /restorehealth

No third party apps are installed that would be causing this problem. 

ObjectDock - Access shortcuts and frequently used applications from an animated dock.
Reply #229 from Stardock Forums Top

On the assumption that perhaps a number of Windows updates might have sorted a few issues related to Fences, I ensured no Stardock entries were in the registry, and installed Fences again and accepting the default for creating fences. So far so good. No looping or errors. I did see that in the registry,

HKEY_CURRENT_USER\SOFTWARE\Stardock\Fences\Groups
 
that the 'default' groups had the word 'default' in the Data entry as well as the display number. Not sure why this would make any difference, but I created new groups on the desktop and deleted all the fences that were first created and had had 'default' in this registry key. So far I have not had any more 'looping' . I'll keep you updated if any other challenges arise using Fences!
Reply #230 from Stardock Forums Top

This has been an issue for over a year now. I wouldn't mind so much but this is a piece of software I paid for.

+1 Loading…
Reply #233 from Stardock Forums Top

Quoting AustinReed, reply 227

I need a teams invite,  windows explorer keeps crashing  

Windows version 20h2 os build 19042.1586

Fences 3.1.3.3

Full Reinstall

Tried Fences 4 (same issue)

Ran SFC /scannow & DISM /online /cleanup-image /restorehealth

No third party apps are installed that would be causing this problem. 

Getting a dump when it happens would be helpful.  While posted in the Start11 FAQ, the same applies here:

https://forums.stardock.com/505872/start11-support-faq#CrashDumps

Sean Drohan
Stardock Product Lifecycle Manager

Reply #234 from Stardock Forums Top

I have added instructions on how to collect crash dumps manually to the support FAQ:

https://forums.stardock.com/486084/fences-support-faq#CrashDumps

I will also edit the beginning of this thread.

What is important is that if you can reproduce the issue reliably, you will want to do that, get the dump, upload it to the cloud service of your choice, and reply with a link here with details about how it was achieved - what you did to produce the crash.

What very well may come of it is that Fences was not the cause at all - then again - it may show that it is.  Either way, this will help find out.

Sean Drohan
Stardock Product Lifecycle Manager

Reply #235 from Stardock Forums Top

I have had this error for a while, see earlier posts.

 

I have an up-to-date copy of Windows 10 and three monitors

 

I’ve just tried to gain some insight into the error.

 

 

I saved a restore point #1

 

Uninstalled fences.

 

Saved another restore point #2

 

Reset to #1 to check my settings were preserved, they were.

 

Reset to #2

 

Uninstalled Display Fusion and open-shell.

 

Saved #3 and rebooted.

Now I had a ‘clean’ system.

 

I installed Fences 4.

 

The error came back immediately before I could test anything

 

I went back to #1 and have spent a happy afternoon getting my environment back. With Fences 3.01.

 

I hope this helps. I can provide configuration details if requested by e-mail from stardock

 

 

J

 

 

 

 

Reply #236 from Stardock Forums Top

I just removed all my Fences and recreated them and the problem seems to have vanished...I'd suggest that anyone having the problem try that.  I still have logging on in case the issue resurfaces.

Reply #237 from Stardock Forums Top

Quoting sdRohan, reply 234

I have added instructions on how to collect crash dumps manually to the support FAQ:

https://forums.stardock.com/486084/fences-support-faq#CrashDumps

I will also edit the beginning of this thread.

What is important is that if you can reproduce the issue reliably, you will want to do that, get the dump, upload it to the cloud service of your choice, and reply with a link here with details about how it was achieved - what you did to produce the crash.

What very well may come of it is that Fences was not the cause at all - then again - it may show that it is.  Either way, this will help find out.

Sean Drohan
Stardock Product Lifecycle Manager

 

I'll send the link in the teams chat. 

 

This crash always happens whenever I turn on/off my USB portable monitor, which is configured to duplicate my primary monitor.  I have a registry file that explicitly removes the two SortMode keys (one for each folder portal), which I run before every time I turn on/off my USB portable monitor.

Reply #238 from Stardock Forums Top

All,

We think we might have a fix for one crash that is possible with Fences and folder portals.  Please see if the just-released beta does indeed resolve it for you and report back here either way, please.

https://forums.stardock.com/512519/fences-4059-beta-feedback-thead

Special thanks to k3nny5 for working with us in Teams to help resolve it.

Sean Drohan
Stardock Product Lifecycle Manager

Reply #239 from Stardock Forums Top

I uninstalled 3.03, rebooted and installed the beta. It seems to have fixed the issue. I will keep monitoring it and wiil report back. No news is good news.

Reply #241 from Stardock Forums Top

Quoting carternjohn, reply 239

I uninstalled 3.03, rebooted and installed the beta. It seems to have fixed the issue. I will keep monitoring it and wiil report back. No news is good news.

Quoting ymj1992, reply 240

It is working so far until now.

Thanks.

VERY pleased to hear that - thanks for the update.

Sean Drohan
Stardock Product Lifecycle Manager

Reply #242 from Stardock Forums Top

Received the below 3 times with in minutes of installing the Beta, fresh install on a brand new PC, windows 11, 2 monitors. Clicked on desktop and screen went white and explorer crashed, exactly the same issues I have been having through several versions

 

The program explorer.exe version 10.0.22000.593 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Security and Maintenance control panel.

 Process ID: 3964

 Start Time: 01d86cd73c445b4a

 Termination Time: 0

 Application Path: C:\Windows\explorer.exe

 Report Id: ba3a8e16-bc37-4aef-ac1b-a220fdab06fb

 Faulting package full name: 

 Faulting package-relative application ID: 

 Hang type: Cross-thread

 

 

 

Reply #243 from Stardock Forums Top

Stardock must be losing a lot of subs because I know I won't be renewing Object Desktop or any of the apps as they are simply not compatible with Windows 11 and they haven't been able to fix the problem in over a year.  I feel kind of bad for them as I've been using their products for like 20 years now (off and on), through moves all over the country and stages of life... I don't know why this time is different than others, I've never seen their software in such a sorry state and for so long. 

But I cannot use software like Windows Blinds and Fences if their impact is as catastrophic on my system as it has been this past year, because I use my computer to run a business. 

Good luck. 

 

~Jonathan

Reply #244 from Stardock Forums Top

Quoting JMBWITHCATS1, reply 243

Stardock must be losing a lot of subs because I know I won't be renewing Object Desktop or any of the apps as they are simply not compatible with Windows 11 and they haven't been able to fix the problem in over a year.  I feel kind of bad for them as I've been using their products for like 20 years now (off and on), through moves all over the country and stages of life... I don't know why this time is different than others, I've never seen their software in such a sorry state and for so long. 

But I cannot use software like Windows Blinds and Fences if their impact is as catastrophic on my system as it has been this past year, because I use my computer to run a business. 

Good luck.  

~Jonathan

Jon, did you try the beta?  If not, why not?

Sean Drohan
Stardock Support Manager

Reply #245 from Stardock Forums Top

Quoting WayneSuch, reply 242

Received the below 3 times with in minutes of installing the Beta, fresh install on a brand new PC, windows 11, 2 monitors. Clicked on desktop and screen went white and explorer crashed, exactly the same issues I have been having through several versions 

The program explorer.exe version 10.0.22000.593 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Security and Maintenance control panel.

 Process ID: 3964

 Start Time: 01d86cd73c445b4a

 Termination Time: 0

 Application Path: C:\Windows\explorer.exe

 Report Id: ba3a8e16-bc37-4aef-ac1b-a220fdab06fb

 Faulting package full name: 

 Faulting package-relative application ID: 

 Hang type: Cross-thread
 

1st, thanks for the post.

Next, can we get a screenshot of your winver.exe like so:

Next, I would like to verify the Fences version.  You have this, yes?

Next, and if you can do so without a crash, perform a snapshot save changing the name that is representative of this effort and easily identifiable like so:

After, perform an 'automatic layout' (the button next to it). Close the Fences UI and try again - do you still get the crash?

If not, something about that layout that you just saved is causing Fences trouble.  Please restore it and verify you still get the crash. 

If so, we REALLY want a full crash dump from it.  These are the directions to do so:

https://forums.stardock.com/486084/fences-support-faq#CrashDumps

It requires some effort from you, Wayne, but we will make it worth your while as we have with k3nny5 who was a tremendous help in finding the cause of a (seemingly) different crash issue.

Taking this even further, we would like to see if you were interested in participating on our internal Microsoft Teams channel - something k3nny5 did with us as well.  Doing so allows for a quick ask\answer turnaround and an environment to exchange data\files easily.  Were you unwilling, just say so and I'll send the invite.

Again, thanks for the feedback, Wayne.

Sean Drohan
Stardock Support Manager

 

Reply #246 from Stardock Forums Top

Quoting sdRohan, reply 244

Jon, did you try the beta?  If not, why not?

Why would I risk trying a beta when I have no idea if the catastrophic failure that causes me to have to hard shut down my computer and uninstall the software could happen.  If I got word that the problem was fixed, I might, but I'mnot just going to try betas and hope for the best.

Reply #247 from Stardock Forums Top

Quoting JMBWITHCATS1, reply 246

If I got word that the problem was fixed, I might, but I'mnot just going to try betas and hope for the best.

You did see these, yes..?

Quoting carternjohn, reply 239

I uninstalled 3.03, rebooted and installed the beta. It seems to have fixed the issue. I will keep monitoring it and wiil report back. No news is good news.
Quoting ymj1992, reply 240

It is working so far until now.

Thanks.

Sean Drohan
Stardock Support Manager

Reply #248 from Stardock Forums Top

Quoting sdRohan, reply 247

You did see these, yes..?

I did not!  Iiiiinteresting!  Thank you!  I will try out the beta and let you guys know how it goes.

 

 

Reply #249 from Stardock Forums Top

Damn, looks like my Object Desktop subscription expired in late April, basically a year I couldn't even use it. Any help for that?  lol