Windows Explorer crashes when I attempt to use the 'Desktop Pages' feature of FENCES

Fences - Win10 Pro - HP Elitebook - 2 Docking stations at Home and work with dual monitors

I have an HP Elitebook with Windows 10 Professional running Fences.
I have the most current updated version of Fences.   

Windows Explorer crashes when I attempt to use the 'Desktop Pages' feature of FENCES

When my laptop is docked at my desk at work, I have no issues.
Both my docks have dual monitor set-ups

When I am using the laptop either un-docked or docked at my desk at home, if I try to "swipe" from either edge, Windows Explorer crashes and re-starts.

I have removed and re-installed Fences once. The problem continues.

 

 

11,579 views 5 replies
Reply #1 Top

Hello,

Sorry to hear you are having issues. When you said removed and re-installed Fences, did you do it with purge or just uninstall and re-install?

If you just uninstalled and re-installed. Please try the purge and reinstalled steps as follows : https://forums.stardock.com/486084/fences-support-faq#reinstalling

Reboot, retest and report back. Thanks.

Basj,

Stardock Community Assistant.

Reply #2 Top

Hello.

Thank-you for your response.  I will follow your instructions with in 8 hours from the time of this reply.

In the mean time, is there a way to back up my current Desktop 'Snapshots' so that I can restore them after I re-install Fences ??

Reply #4 Top

Hello.

I followed the instructions provided from the links you sent me to 'Purge' and re-install Fences exactly as stated.  I did not deviate from any of the steps, and the process was completed successfully; however, the issue is unresolved.

  • The event does NOT occur when my laptop is docked at my desk at work.  Fences functions perfectly.
  • The event DOES occur when I am using my laptop stand-alone without any physical connections
  • The event DOES occur when my laptop is docked at my desk at home.
  • I have uninstalled the 3 most recent software programs on my laptop as a precaution and rebooted.  The problem continues.

I went through and scanned my Windows Applications logs and found 3 events which all occur at around the same time as the actual crash.  I can not tell from reading the event descriptions whether they are related to this issue and I do NOT know for certain if any of them are the cause, but I have posted them below on the basis that they might contain some clues which would help provide insight into this problem.


Log Name:      Application

Source:        Application Error

Date:          6/27/2018 7:04:20 PM

Event ID:      1000

Task Category: (100)

Level:         Error

Keywords:      Classic

User:          N/A

Computer:      i1917.ica.com

Description:

Faulting application name: explorer.exe, version: 10.0.16299.492, time stamp: 0x721b1ba3

Faulting module name: Windows.CloudStore.dll, version: 10.0.16299.98, time stamp: 0xd9fb8a36

Exception code: 0xc0000409

Fault offset: 0x0000000000074dee

Faulting process id: 0x3a44

Faulting application start time: 0x01d40e6b2d56cff5

Faulting application path: C:\Windows\explorer.exe

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

Report Id: 99021e94-eaac-4bd3-b4c4-b356c4e2098d

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="2018-06-27T23:04:20.014279900Z" />

    <EventRecordID>23329</EventRecordID>

    <Channel>Application</Channel>

    <Computer>i1917.ica.com</Computer>

    <Security />

  </System>

  <EventData>

    <Data>explorer.exe</Data>

    <Data>10.0.16299.492</Data>

    <Data>721b1ba3</Data>

    <Data>Windows.CloudStore.dll</Data>

    <Data>10.0.16299.98</Data>

    <Data>d9fb8a36</Data>

    <Data>c0000409</Data>

    <Data>0000000000074dee</Data>

    <Data>3a44</Data>

    <Data>01d40e6b2d56cff5</Data>

    <Data>C:\Windows\explorer.exe</Data>

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

    <Data>99021e94-eaac-4bd3-b4c4-b356c4e2098d</Data>

    <Data>

    </Data>

    <Data>

    </Data>

  </EventData>

</Event>


Log Name:      Application

Source:        Application Hang

Date:          6/27/2018 7:04:18 PM

Event ID:      1002

Task Category: (101)

Level:         Error

Keywords:      Classic

User:          N/A

Computer:      i1917.ica.com

Description:

The program explorer.exe version 10.0.16299.492 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: 4b34

 Start Time: 01d40e6a9dc0146d

 Termination Time: 0

 Application Path: C:\Windows\explorer.exe

 Report Id: 2a69edb0-67df-4c56-ab11-4dcc593f37d3

 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 Hang" />

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

    <Level>2</Level>

    <Task>101</Task>

    <Keywords>0x80000000000000</Keywords>

    <TimeCreated SystemTime="2018-06-27T23:04:18.779774400Z" />

    <EventRecordID>23325</EventRecordID>

    <Channel>Application</Channel>

    <Computer>i1917.ica.com</Computer>

    <Security />

  </System>

  <EventData>

    <Data>explorer.exe</Data>

    <Data>10.0.16299.492</Data>

    <Data>4b34</Data>

    <Data>01d40e6a9dc0146d</Data>

    <Data>0</Data>

    <Data>C:\Windows\explorer.exe</Data>

    <Data>2a69edb0-67df-4c56-ab11-4dcc593f37d3</Data>

    <Data>

    </Data>

    <Data>

    </Data>

    <Binary>430072006F00730073002D0074006800720065006100640000000000</Binary>

  </EventData>

</Event>


Log Name:      Application

Source:        Application Error

Date:          6/27/2018 7:04:19 PM

Event ID:      1000

Task Category: (100)

Level:         Error

Keywords:      Classic

User:          N/A

Computer:      i1917.ica.com

Description:

Faulting application name: Microsoft.Notes.exe, version: 2.1.18.0, time stamp: 0x5aba81d8

Faulting module name: CoreUIComponents.dll, version: 10.0.16299.15, time stamp: 0x35d247d6

Exception code: 0xc0000005

Fault offset: 0x000000000008e1f4

Faulting process id: 0x34a0

Faulting application start time: 0x01d40e6a9e758f58

Faulting application path: C:\Program Files\WindowsApps\Microsoft.MicrosoftStickyNotes_2.1.18.0_x64__8wekyb3d8bbwe\Microsoft.Notes.exe

Faulting module path: C:\WINDOWS\SYSTEM32\CoreUIComponents.dll

Report Id: ce4a89c7-863a-4a61-9e7b-d0a9345cbec1

Faulting package full name: Microsoft.MicrosoftStickyNotes_2.1.18.0_x64__8wekyb3d8bbwe

Faulting package-relative application ID: App

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="2018-06-27T23:04:19.764253700Z" />

    <EventRecordID>23327</EventRecordID>

    <Channel>Application</Channel>

    <Computer>i1917.ica.com</Computer>

    <Security />

  </System>

  <EventData>

    <Data>Microsoft.Notes.exe</Data>

    <Data>2.1.18.0</Data>

    <Data>5aba81d8</Data>

    <Data>CoreUIComponents.dll</Data>

    <Data>10.0.16299.15</Data>

    <Data>35d247d6</Data>

    <Data>c0000005</Data>

    <Data>000000000008e1f4</Data>

    <Data>34a0</Data>

    <Data>01d40e6a9e758f58</Data>

    <Data>C:\Program Files\WindowsApps\Microsoft.MicrosoftStickyNotes_2.1.18.0_x64__8wekyb3d8bbwe\Microsoft.Notes.exe</Data>

    <Data>C:\WINDOWS\SYSTEM32\CoreUIComponents.dll</Data>

    <Data>ce4a89c7-863a-4a61-9e7b-d0a9345cbec1</Data>

    <Data>Microsoft.MicrosoftStickyNotes_2.1.18.0_x64__8wekyb3d8bbwe</Data>

    <Data>App</Data>

  </EventData>

</Event>

Reply #5 Top

Hello,

Sorry to hear you are having trouble.

Are you using Websense or Forcepoint (one and the same but with different names depending on version)?  This is something that perhaps your IT people have to answer.

If so, there are known issues with it that we have no control over.

If not, please try:

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