Insider Build 14316 (Redstone) & Various Stardock Issues

Updating Windows 10 Insider Preview 14316 Creates Havoc

from Stardock Forums

Is anyone else having issues in compatibility between Windowblinds, WindowsFX and or Start10 in conjunction with the Tuesday 06-April-2016 Insider Preview release?  Upon install of this update, after logging on to the PC for me there was basically no UI at all.  Eventually I launched Task Manager using <CTL><ALT><DEL> and immediately noticed Windows Explorer wasn't running.  Hmmm.  I tried launching Explorer and momentarily saw it appear on the list of tasks, but then *poof* it was gone again. 

 

One by one I started killing running services and after disabling the three listed above, I was able to launch Windows Explorer with the desired result.  

 

I just wanted to check in here before I start investigating further into the issue, in case anyone else has already isolated, eliminated or overcome the issue.

 

Thanks!

windowblinds
7,245 views 5 replies
Reply #1 from WinCustomize Forums Top

SD products don't fare well with the insider builds, unlike the release version of W10 where WindowBlinds and certain other apps are stable. Not all SD apps are compatible however. You should expect difficulties with the insider builds as they are different.

Reply #2 from WinCustomize Forums Top

SD products are geared for RTM products only.

 

Galactic Civilizations IV
Reply #3 from Stardock Forums Top

The issue is WindowFX.  Disable that and you should be fine.

We have an update and I am unsure why it has not been released.

Reply #4 from Stardock Forums Top

I noticed this problem too.. but in all fairness running things like Windowblinds and related software on Developer Previews is just asking for trouble. 

 

I have to admit however with the Eset problem and Windows building in a Dark theme.. my need for my DesktopX subscription is starting to diminish. 

 

:(

 

Reply #5 from Stardock Forums Top

Thanks for the input guys--I'm well aware of the increased chances one takes on when using software such as this on any preview-version platform; I have to say, however that testing this things (and figuring out the post-crash forensics) is kind of the whole point of using preview-version software in the first place.   

I just wanted to do my due diligence, as it were, and see if anyone else was experiencing the issues to more easily rule out the obvious things like the role my own hardware and its configurations and/or other software in the mix that one might not immediately consider.

I'd also have to agree with darekmeridian202's comment in that there seems to be a lesser need for some of these applications as MS adapts to the tastes of its user base. (Considering it's only been an issue of most of us since back to the days of XP, they've certainly had a lot of time to consider this new approach!)

Thanks again all..