Fresh install of Fences3 causes Windows 10 Explorer to crash

from Stardock Forums

Hi,

I have used Fences in the past on previous Windows Version, so was looking forward to having this again on Windows 10.

However, on installation and every time I try to enable Fences Windows Explorers crashes, and fences is unusable.

I have Windows 10 version 1809, and Fences3 3.0.9.11.  

I do not have WebSense/ForcePoint installed (which appears to be a common cause for this behaviour).

Anybody else experiencing this - and how to fix? 

Thanks.

fences
23,999 views 19 replies
Reply #1 from Stardock Forums Top

Hello,

Sorry to hear you are having issues. Please try the purge and reinstall steps as follow https://forums.stardock.com/486084/fences-support-faq#reinstalling

Make sure to re-download the latest version from your account. Reboot after the purge. Reinstall Fences. Reboot again and retest. Report back here.

Thanks

Basj,

Stardock Community Assistant.

Reply #2 from Stardock Forums Top

Ok,

I have executed the following:

(1) Run the purge script - ran without any errors.

(2) Reboot

(3) Reinstalled Fences - first explorer crash when prompted to enter Activation key during installation.

Thanks,

Graham

Start11 - Customize the Start Menu and Taskbar in Windows 10/11.
Reply #3 from Stardock Forums Top

Please try the following:

-For Win 10 Users: Open the Start Screen, and type 'cmd'. Right-click on the search result and select 'Run as administrator' from below.

-Type: sfc /scannow

-Wait for the scan to complete (this can take several minutes)

Some help on how this looks should you need it:

https://support.microsoft.com/en-us/help/929833/use-the-system-file-checker-tool-to-repair-missing-or-corrupted-system

If the SFC finds errors, but cannot fix them, please also run the following command in the same command prompt window:

dism.exe /online /Cleanup-Image /RestoreHealth

Some help on how this looks should you need it:

https://www.windowscentral.com/how-use-dism-command-line-utility-repair-windows-10-image

The above command should assist with replacing any damaged or problematic system files. Please note, however, since it may require restoring certain files, this process can take some time and you will need to be patient until it has completed.

Please let me know whether this resolves your problem or if you have any additional questions.

Thank you,

 

 

Basj,

Stardock Community Assistant

Reply #4 from Stardock Forums Top

Hi Basj,

Unfortunately sfc did not find any issues:

PS C:\WINDOWS\system32> sfc /scannow

Beginning system scan.  This process will take some time.

Beginning verification phase of system scan.

Verification 100% complete.

Windows Resource Protection did not find any integrity violations.

I also ran dism with the /ScanHealth option - which also found no issues:

PS C:\WINDOWS\system32> dism.exe /online /Cleanup-Image /ScanHealth

Deployment Image Servicing and Management tool

Version: 10.0.17763.1

Image Version: 10.0.17763.503

[==========================100.0%==========================] No component store corruption detected.

 

The operation completed successfully.

So I am still unable to run Fences  >:(  .

 

Graham

Reply #5 from Stardock Forums Top

Are you using Windows slideshow? 

Thanks

Basj

Stardock Community Assistant.

Reply #6 from Stardock Forums Top

I cant get Fences 3 to work on Windows 10 1607. It keeps crashing over and over. I even updated it and it still crashes. 

Reply #7 from Stardock Forums Top

Hello,

Quoting cpeikert, reply 6

I cant get Fences 3 to work on Windows 10 1607. It keeps crashing over and over. I even updated it and it still crashes. 
End of cpeikert's quote

Sorry to hear you are having trouble.

Are you using Fences in a corp environment - one that uses WebSense or ForcePoint?

Sean Drohan
Stardock Support Manager

Reply #8 from Stardock Forums Top

Enterprise environment yes but no we are not using Websense or Forcepoint.  Also Fences is not compatible when using Remote Desktop. That will crash your computer every time. 

Reply #9 from Stardock Forums Top

Hello,

Sorry to hear you are having trouble.

Quoting cpeikert, reply 8

Enterprise environment yes but no we are not using Websense or Forcepoint. 
End of cpeikert's quote

Then I would suspect it is an (AV) app like them.  Doing a clean boot, if allowed, would go a ways to illustrating that:

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

Quoting cpeikert, reply 8

Also Fences is not compatible when using Remote Desktop. That will crash your computer every time. 
End of cpeikert's quote

There are no known issues with it - I suspect it is related to whatever app is causing the above.

Sean Drohan
Stardock Support Manager

Reply #10 from Stardock Forums Top

I have the same issue without an AV installed. First 2 things installed on Windows 10 before anything else is Start 10 and Fences. We use Bitdefender as our AV.  Crashing only occurs during logon and if you try to remote desktop into the pc.  If you let the computer sit for about 5 to 10 minutes and let it crash over and over then sometimes it may start working. 

What it looks like its doing is causing Explorer.exe to hang up. Im even getting event viewer messages of Application Hang

The program explorer.exe version 10.0.14393.3053 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: 1fe8
 Start Time: 01d553894b17f80b
 Termination Time: 0
 Application Path: C:\Windows\explorer.exe
 Report Id: 964bff69-bf7c-11e9-b84c-6045cba5da60
 Faulting package full name: 
 Faulting package-relative application ID: 

This only occurs when Fences is running. 

Reply #11 from Stardock Forums Top

Quoting cpeikert, reply 10

This only occurs when Fences is running. 
End of cpeikert's quote

I have tested this with the latest version of Fences (3.09.11) and it works without crashing:

https://cdn.stardock.us/support/uploads/2019-08-16_08-16-47.mp4

If you are doing anything to scale down graphic settings for the remote, I would suggest you have it to max resolution.

This is also a relevant question that was unanswered:

Quoting basj, reply 5

Are you using Windows slideshow [on the remote]? 
End of basj's quote

If so, try with a solid color background

Sean Drohan
Stardock Support Manager

Reply #12 from Stardock Forums Top

I dont use slideshow and I quit remoting into my pc because it wont work with Fences. I had to setup a RDP VM for remote access related work. 

I have another pc I tested Fences on and its running Win 10 1809 with the latest version of Fences and it tends to crash too.  

 

One common thing though is both computers have dual monitors. 

 

Reply #13 from Stardock Forums Top

Quoting cpeikert, reply 12

One common thing though is both computers have dual monitors. 
End of cpeikert's quote

That would not be an issue.  The PC you saw me remote to in my video also has two monitors.

Quoting cpeikert, reply 12

I have another pc I tested Fences on and its running Win 10 1809 with the latest version of Fences and it tends to crash too.  
End of cpeikert's quote

If said 2nd PC is in the same corp environment, I assume it has like apps, settings, and is under the same corp policies. 

Quoting cpeikert, reply 12

I had to setup a RDP VM for remote access related work. 
End of cpeikert's quote

I cant readily test on a VM but it should not make a difference.

Sean Drohan
Stardock Support Manager

Reply #14 from Stardock Forums Top

I dont use Fences on the VM's since I cant get it to work on desktops when RDP.  I also dont use APPS on my computers. All programs are executables. 

The other PC is on the same network but in a different OU. 

Reply #15 from Stardock Forums Top

Anyone get this working yet? I gave up and had to remove it. My computer wont stop crashing with it running. It wont even complete the boot up process with it enabled. 

Reply #16 from WinCustomize Forums Top

Quoting cpeikert, reply 14

I also dont use APPS on my computers. All programs are executables. 
End of cpeikert's quote

'Apps' is a generic term for 'applications' aka programs/executables...;)

Reply #17 from Stardock Forums Top

Quoting cpeikert, reply 15

Anyone get this working yet?
End of cpeikert's quote

It was never not working for us:

https://cdn.stardock.us/support/uploads/2019-08-16_08-16-47.mp4

Why it is not working for you is yet to be understood. 

Doing a clean boot, if allowed, would go a ways to help figure out what may be causing a conflict:

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

Sean Drohan
Stardock Support Manager

Reply #18 from Stardock Forums Top

Even disabling Fences didnt work. Computer still crashed and threw up a Fences error. Had to uninstall it to get the crashing to quit. This is what I get when Fences is installed.  I was incorrect to say it was Fences crashing but its Fences thats causing Explorer.exe to crash. I saw the same behavior with classicshell which caused me to move to Start 10. 

 

The program explorer.exe version 10.0.14393.3053 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: 1574

 Start Time: 01d558f5320bad73

 Termination Time: 0

 Application Path: C:\Windows\explorer.exe

 Report Id: 77a11761-c4e8-11e9-b84f-6045cba5da60

 Faulting package full name: 

 Faulting package-relative application ID: 

 

Reply #19 from Stardock Forums Top

Doing a clean boot, if allowed, would go a ways to help figure out what may be causing a conflict:

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

Sean Drohan
Stardock Support Manager