carternjohn

I uninstalled 3.03, rebooted and installed the beta. It seems to have fixed the issue. I will keep monitoring it and wiil report back. No news is good news.

I have had this error for a while, see earlier posts. I have an up-to-date copy of Windows 10 and three monitors I’ve just tried to gain some insight into the error. I saved a restore point #1 <p sty

Back after a week away, and no change ... I've reinstalled 3.03 from 2017 and it does all I want. I look forward to seeing how things progress. I had the error on latest versions of 3 and 4. I use 3 monitors and display fusion, groupy with open-shell

I just rebooted my computer and the error reapeared. I've forgotten which version I started with but if this problem doesnt get resolved soon, I'll move on. I forgot to mention that I use three monitors. John

I've just gone through a frustrating few day with this error. I've ended up with a completely fresh fences 4.0.0.3 on top of a recent update of Windows 10. It appears to work. I've tried restoring a snapshot which predates the fault appearing. Fences only and no icons. The problem reapers. Uninstalling and reinstalling works, Placing all my desktop icons in one new fence works. I can provide extra information on request. How