Fences breaks on insider build 15002 on 3 of 4 machines

I did try reinstalling with no success, nothing to explain why 1 machine works -- all 4 machines had all the same stardock products installed.

If anyone finds a method of reinstalling that works, please chime in.

This insider build is buggy as hell.

Having said that, I'll poke Fences tomorrow

Understatement of the year unfortunately!

outside fences, im not seeing any other bugs with this build yet, though...it could just be that i dont use any of the bugged/buggy features other then fences making explorer bork....love fences, love win 10, the good thing about this kind of thing is, by the time the changes go to rtm/general release, fences and the like will have updated or ms will have fixed whatever they did to bork them up, thanks to preview build users..

i see people talk crap about ms even offering this kind of thing.......i love it......yes it saves them money hiring testers, but it also gives them a hugely larger base of test configs that can help them spot issues that paid testers very likely would miss due to lack of specific hardware/software configs....

if it was forced, i wouldnt be happy, but, as an opt in....i can deal...either stardock will patch fences, or a new fast ring build or leak will come out, and i will move to that, since i cant roll back because...for some reason it thinks i removed the rollback files...(they are there...it just dosnt see them or something...only real bug i have found..i know a workaround but...why bother when the only thing not working is fences.. and i can deal till its updated(fences or windows...)  

Yeah - 15002 broke fences. It will start, but the whole start up takes a long time since icons have to be re-arranged again (15002 changed desktop layout?) and I can't double click on anything on the desktop, just sits there does nothing, blinks the screen and that's all. I did get fences to crash and I was able run stuff from the desktop.

It certainly isn't 'crap'.  The problem with releasing public alphas or betas is the general public's perception they are more competent with OS tech than they really are.

Too many 'over confident' people end up crashing and burning in some form or other and actually forget they are guinea-pigs and/or lemmings and proceed to blame anyone and everyone for their own shortcomings.

Stardock has always only released beta software to Object Desktop subscribers for that very reason.

Once upon a time MS would essentially limit theirs to Technet and equivalents....same reason.

Now they don't...and even the general population Win 10 is a living Beta.

Also having big problems with 3.03 and 15007, desktop is really laggy, icons take an age to settle, often start off messed up and then slowly go back into place etc.

Also having problems with 5007. I realize Insider Builds are not to be complained about, but it is disappointing that it breaks with Windows Insider builds. I'm kind of curious what Microsoft is changing that really messes Fences up. 

After doing a complete uninstall (uninstall, delete reg entries, delete folders in user AppData) I found it's an issue with portals (at least for me anyway). After recreating everything except portals, I could work as normal.

For anyone that wants a solution for when fences goes down, write a widget to act as a portal till the next update. Install something like "8GadgetPack" and create a js-based solution till portals are working again.

I have already started on one, but i've only cloned the "Fences aesthetic" so far:

It shouldn't be too hard to list folder and file info. But I don't know if I can recreate context-menus the way Fences can. If anyone is interested in making this a github project, let me know. Otherwise i'll just keep it to myself.

I've got this affect as well on the 15xxx insider builds, but it happens on my Dell 5510 laptop and not my desktop.  The Dell has the built-in Intel 530 graphics controller with the Dell drivers.  The desktop uses an EVGA 960 GTX card with the latest Nvidia drivers if it's of any help.

I see this problem as well on the build 15007 and 15014 (and the one build prior to 15007). 

Using a Surface Pro 3 i7. 

BTW I am sure that this change in 15002 is the source of the problem. I wonder if you can turn this new feature off?

From https://blogs.windows.com/windowsexperience/2017/01/09/announcing-windows-10-insider-preview-build-15002-pc/#eeIzKboRJlmiRBBF.97

Desktop Icon Placement and Scaling Improvements: We’ve heard from you that sometimes desktop icons aren’t scaled or arranged as expected, particularly after docking/undocking your device, working with monitors that have different DPI, or projecting your monitor. We want users to feel that desktop icons are stable, scaled properly, and move predictably when changing monitor configurations, so we’ve made changes to how this logic works in order to address your feedback. Now when you change your multi-monitor configuration, dock/undock your device, project your display, add or remove monitors, or otherwise make changes that affect the icon scaling, you should see an improvement in how the system adjusts the layout of your desktop icons. Try it out and let us know how it goes!

We have contacted MS as there appears to be a bug with them . . we'll see what they come up with.

Still waiting for the app I paid for not to be worthless.

Yay another double post on here.

Please report the bug via MS insider feedback as the problem is with the operating system itself.

Seems to be fixed with 15031, when I double click an icon on my desktop it reacts appropriately and immediately