Explorer.exe crashing when hitting Win + D

Helloooooo??? (echo sound...)

I am having the same problem with the Fences. I think it might has something to do with the virtual desktop. Everytime click Ctrl+D or Windows+Tab

What if you set your desktop background to a solid color (I know, sounds odd).  Does it change anything?

I have exactly the same issue at work. We have several thousand of machines waiting for a fix. 

We are using Windows 10 with websense, we have exclude all the fences files however we found out we have to exclude "explorer.exe" as well in order to fix it but this is impossible on security perspective. 

Any chance you have alpha version for us to test with ? 

Really desperate for a help   

No deal, it crashes too. =(

Quoting gabrielltrindade, reply 5

No deal, it crashes too.

End of gabrielltrindade's quote

Keep the desktop (all of them if you have multiple) as a solid color.

Start with this:

https://forums.stardock.com/486084/Fences-Support-FAQ#reinstalling

Stop short of restoring your Snapshot - select to use the default Fences organization on install.  See if it still happens.  If not, and if you had a folder portal in your last snapshot, add a new folder portal - try again.  If that works, try restoring your last snapshot.

Hi sdRohan, unfortunately this did not work either, after purging through the bat file and reinstalling Fences 3.0 as admin the issue persists.

And you are running 3.05, not any earlier version?

Yes, 3.0.5.12 according to the About section.

I'd like you to try this, please:

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

Tried it this morning.

Makes NO DIFFERENCE!  IT STILL FAILS

I have a company machine, don't have permissions to do so, but as you see from the comment above, issue seems to persist anyway.

Not for everyone, I have had good success for the very few people that have reported this.  Its almost always been that they have Windows Slideshow enabled for their desktop or have a third party app that causing a conflict.  The slideshow thing should not be a problem, and is not the case for everyone (works for me), but is.  It is being looked at.

Understood, unfortunately I cannot do make what you suggested anyway, so will need another way of troubleshooting.

sdROhan, any update on this? As mentioned, I cannot proceed with your suggestion.

Hi sdRohan, no news?

I will simply request a refund if we can find a solution to this. Below is the application log from Windows after the issue happens.

Log Name:      Application

Source:        Application Error

Date:          20-Dec-17 13:01:11

Event ID:      1000

Task Category: (100)

Level:         Error

Keywords:      Classic

User:          N/A

Description:

Faulting application name: Explorer.EXE, version: 10.0.15063.674, time stamp: 0xd8364343

Faulting module name: KERNELBASE.dll, version: 10.0.15063.726, time stamp: 0x1a9bbe0b

Exception code: 0xc0000005

Fault offset: 0x00000000000067ef

Faulting process id: 0x29a4

Faulting application start time: 0x01d379885bb0e38e

Faulting application path: C:\Windows\Explorer.EXE

Faulting module path: C:\Windows\System32\KERNELBASE.dll

Report Id: faf93e4e-9298-46e0-bfa9-401984f7c130

Faulting package full name: 

Faulting package-relative application ID: 

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

  <System>

    <Provider Name="Application Error" />

    <EventID Qualifiers="0">1000</EventID>

    <Level>2</Level>

    <Task>100</Task>

    <Keywords>0x80000000000000</Keywords>

    <TimeCreated SystemTime="2017-12-20T12:01:11.608231500Z" />

    <EventRecordID>24842</EventRecordID>

    <Channel>Application</Channel>

    <Security />

  </System>

  <EventData>

    <Data>Explorer.EXE</Data>

    <Data>10.0.15063.674</Data>

    <Data>d8364343</Data>

    <Data>KERNELBASE.dll</Data>

    <Data>10.0.15063.726</Data>

    <Data>1a9bbe0b</Data>

    <Data>c0000005</Data>

    <Data>00000000000067ef</Data>

    <Data>29a4</Data>

    <Data>01d379885bb0e38e</Data>

    <Data>C:\Windows\Explorer.EXE</Data>

    <Data>C:\Windows\System32\KERNELBASE.dll</Data>

    <Data>faf93e4e-9298-46e0-bfa9-401984f7c130</Data>

    <Data>

    </Data>

    <Data>

    </Data>

  </EventData>

</Event>

I have processed your refund.

I have exactly the same issue with Windows 10 Enterprise, is there a solution available ?

I'm also interested in a fix.  I have Websense on a corporate laptop and not permitted to remove it.  Need a fix to this problem pronto.  New laptop and I'm running into this multiple times a day and it stops me dead in my tracks every time while I'm in front of customers.  

K

Is anyone handling this issue ? it seems wide speared without any solution (the post opener got a refund).

Can we get any comment about the status of this bug ?

Stardock,

This issue is widespread.

It started after September Windows updates. 

Every time any method of "show desktop" is used, Explorer crashes.

Reinstalls and cleanups dont help - you have a bug

We dont need the refund, we need you to fix it.

Please update what is being done.

Update - Version 3.0.7.5 Beta - same result; Explorer crashed on Win-D or other "show desktop" methods

Its is not, at all actually, but that does not mean it is not being looked at. 

The ones we can't readily help (and at least two of the people in this thread) are the ones using WebSense.  Also, and as stated, we would like to know how many that have this issue are using Windows Slideshow.  While that should not be a problem, it would help us focus our efforts.

On a final note, ilyamalyar.  We help anyone that uses our products. Finding resolutions for any is not always easy - this issue is decent example of that.  Only a few (by comparison) can demonstrate it and it (seemingly) only started after the Win10 Fall creators update (now we have to hunt for what MS could have done).

When you post things like 'Stardock does not care' (since deleted), it's not only incorrect, it does not help in resolving the issue.  Please keep to the facts of the issue as they will help most with solving it.

Thanks.

I have the same issues and the last I heard from Stardock (Sean) was on Nov 20, 2017. 

I think that it crashes because I am also on a corporate computer and network. I don't know if my computer is running Websense or not. I did try the "create a new user" solution but that did not work.

I was hoping the latest Fences 3.0.7.6 update would fix it, but it does not.

I am living with it because I would rather have all my open folders crash and close than to not use Fences.  I do not want a refund.

Cheers from a not "Widespread" issue user.

GP.

Fair point, @garympeters, and thanks for sharing that the new version did not solve the problem for users like us, apparently. Once it does I will gladly upgrade again - for now I am back to Fences 2, no crashing issues but I don't have List Views saved in Folder Portals, the only downside.