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

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   

Quoting gabrielltrindade,

reply 5

No deal, it crashes too.

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.

And you are running 3.05, not any earlier version?

I'd like you to try this, please:

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

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.

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

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 exactly the same issue with Windows 10 Enterprise, is there a solution available ?

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 ?

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

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.