cpeikert

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

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.

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.

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.

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 Ap

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.

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.