Fences with Insider Build 15031 -- Almost Working??

from Stardock Forums

Hi all,

I have had Fences disabled for a while because Insider Builds broke them. There's been at least 3-4 builds since then and I'm trying again. 

Now, it seems to work OK, except for missing icons on items inside of folder portals. Icons in desktop fences seem OK, but if I create a folder portal, they have no icons. 

I've uninstalled Fences, deleted the Stardock folder in AppData. Deleted any registry entries I could find, and rebooted, then re-installed. Same thing.

 

I'm sure I'm going to get a bunch of crap about Insider builds being unsupported, but I don't expect Fences to suddenly work when the Creator's Update is gold and out..

BTW - I also tried using a freeware utility to clear and rebuild icon cache. Didn't work. 

 

Any fix for this particular issue?

fences
11,633 views 4 replies
Reply #1 from Stardock Forums Top

I am still having some instability issues with Build 15931.rs2_release,170204-1546 as well.  Normal icons in fences seem to work OK now but my desktop is spontaneously rebooting (was stable before reloading Fences 3.03).  Just an FYI.

Reply #2 from WinCustomize Forums Top

Like all insider builds there will be instabilities due to their very nature, as betas. Some programs will work, others won't. Those who run these preview builds are actually the beta testers. Your feedback helps create more stable versions. These stable versions are what developers look at when updating their software. How the software reacts to different environments within the OS determines their usefulness. So expect problems to occur.

WindowBlinds - Free yourself of the default settings, customize your desktop.
Reply #4 from WinCustomize Forums Top

Quoting MarkDavis, reply 3

Hey guys, are you aware of and/or addressing this issue: https://forums.stardock.com/480242/page/1/

It's not a W10 beta issue; it's a pervasive sluggishness / lag that's affecting tons of W10 users and for many (including me) render Fences completely unusable...
End of MarkDavis's quote

Comment has been addressed.  BTW, 'tons of W10 users' is incorrect.