Worked like a charm, Thank you WvdV

@WvdV, thank you very very much!

Well done WvdV

The REVO un/re-install didn't work for me, and I did scan. Revo didn't catch everything, apparently, as all of my fences were still there.  I managed to get to Fences settings and reset the fences, which seemed to do the trick...until I moved This Computer out of the Programs fence, then it all went haywire again.  So, I reset it again, and it seems to working fine.  Scared to touch those program icons, but creating a new portal worked just fine.

UPDATE:  Doesn't really work insofar as Windows asks 'permission for Fences to make changes' every hour or so, twice.   Also, on a minor note, the roll out of one window somehow went beyond the limits of the screen, and I don't know how to close it.

Unfortunately after a day of working OK, fences started crashing again.

I had to do your procedure twice, after the secund time all is working as it should, I also have been rebooting several times just to check,but all seems ok -)   

Here is what I did to get it working:

• Disable Fences startup (task manager)
• Open Task scheduler
• Create a new task with the following options:
• Run with highest Privileges
• Triggered by user logon
• Starts Fences with /startup as its argument
• Do not start a new instance if one is already running
• Follow WvdV's advice
• Open Fences configuration utility and disable layout preservation and perform an automatic layout (don't create a backup), then close
• (Optional) Add as many "Sorting & Organizing" rules as possible to have fences auto-generate your layout every time you have to perform an automatic layout.
• delete backups and logs in %appdata%\Stardock\Fences folder
• You should also disable creating daily backups. This was a big issue for me.
• (optional - probably doesn't do anything, but try it when nothing else works)
• Take ownership of %ProgramData%\Stardock\Fences3 - Make sure to replace ownership on child objects - and hit ok
• Then add yourself and the administrators group (with full control for both) to the folder under advanced security settings
• Do this again to the %appdata%\Stardock\Fences folder
• Note: This is only because I saw several user comments talking about permission errors. I am an admin on my system and I was unable to view these files, so I assume Fences cant either.
• Restart your system
• Fences should be 99% working! You can now go into fences settings and enable layout preservation if you like.
• For some reason I cannot move icons onto my desktop via drag-and-drop (causes a crash). If you want to do that, you need to edit Stardock's registry settings (use the recycle bin as a template for your own icons)
• Fences registry settings: HKEY_CURRENT_USER\SOFTWARE\Stardock\Fences
• Recycle Bin's CLSID: ::{645ff040-5081-101b-9f08-00aa002f954e}
• Recycle Bin Example Value (from my registry - located on screen 1 in the top left corner - I dont know why "firefox.exe" is in there):
  -1|13|2|13|2|0|0|0|\\.\DISPLAY1`|9|0|0|firefox.exe|0|1577882896|30543274|
• This is pretty advanced, and will cause Fences to crash if configured incorrectly. If Fences does crash because of your edits, simply perform another auto layout.
• Pro Tip: edit one icon at a time and export your fences registry settings every time you have a stable desktop (do each key individually: Icons, Groups, etc... this way you can restore only what broke to avoid any other issues).

Let me know if this helps! Good luck everyone!

We hope to have a beta to resolve the issue this week.

Working fine on build 14926. 

I have been continuing to follow posts on this topic. On another computer 💻 that I own, that also is on the Fast Track for Preview releases of Windows 10, there has never been a crash of Fenses and it did not crash after being updated to the lastest Preview release. 

On my regularly used PC,  it crashed again today - prior to when I installed the latest Preview release.  What I never mentioned in any of my posts about this problem was that even though Fences crashed,  it left most of (but not all of)  the icon shortcuts where they would have been had Fences operated correctly! This time,  after using Revo Pro and deleting all leftover files following the built-in uninstall, I reinstalled Fences 3.1 and one at a time,  moved the appropriate icons to the Fences I then created. No sweat 💦. It worked. 

I updated Windows Preview and Fences continued to work. All in all,  a very strange acting bug 🐛, wouldn't you say? 

Well build 14926 is now released. Will it fix it or will it break it? Here goes.....

Good news Fences fans like myself! Fences has started working properly with Insider Build 14926! I didn't have to do anything regarding Fences just let the install do it's thing.

Just had to drag some icons around again!

So Stardock are off the hook this time! Maybe it was my negative rating for the last build to Microsoft "you broke Stardock Fences!" that got it fixed?

14926 fixed it for me too

Me likey

Well . . . it's good to know that it wasn't us.

And some code got optimized to "fix" this . . . so "Yay"?

14926.rs_prerelease.160910.1529 (Win10 Enterprise x64 on a domain with desktop folder redirection) working fine now.

I am unable to uninstall Fences 3. It is gone from add/remove programs, and several uninstallers do not find it. But it is in the start Menu, and starts, but does not work.

How do I uninstall Fences 3 manually?

just an FYI, fences 3.0.1 is working on the new build released on the 14/09/2016 

1. Start the uninstall process
2. Kill the Explorer task
3. Continue the uninstall

Or install the Start10 beta and then uninstall normally

Issues with Fences again.

Sorry - hit submit before I was done.

Windows Insider Build 14936 Fences is back to not working and this time I cant find a work around.

Anyone have any luck here, explorer crashes, fences gets disabled, same old issues but not of the solutions appear to work.

--Dave

Using the Fences 3.03 beta?

Where do we get the beta?

The latest Windows 10 update seems to work fine, but I'm still having to re-authorise Fences to make changes every hour.  I tried a quick un/re-install, but same thing.