The recent new insider build of Windows 10 (build 14251) has some pretty intense updates. There are also some known issues, but this is not one of them.
After updating to build 14251, if WindowFX is installed and enabled on the system explorer.exe will not be able to run and the user will be duped to their desktop with nothing but a black screen and a cursor.
If you are savvy enough like I was; You can open an elevated command prompt, navigate to "C:\Program Files (x86)\Stardock\WindowFX", run 'WindowFXConfig.exe' and turn off WindowFX. Then you will be able to start explorer.exe and have your desktop reappear.
I'm not asking for immediate updates, but for product stability and longevity, I thought it would be helpful to post my findings.
Thanks for reporting this.
I have taken a look and it seems to be caused by one bit of code so we should have an update out for it in the next few weeks.
faster.....
Same thing with windows 10 build 14267
Same thing with windows 10 build 14267 when upgrade boot with black screen and explorer no start
We have an update to resolve this pending testing.
Is there any update on this issue? Same thing happens to me, Explorer crashes and desktop goes all black and unresponsive. Windows 10 build 14267.
Hey Neil,
WTF, I'm suppose to wait weeks to use my computer because your crapware just ate my desktop?
I need it NOW! How do I disable this crap with a black screen where nothing works.
And, if you have a fix for it, where is it and why are you still allowing a bad version to be downloaded. Even if it could be downloaded with a black screen(NOT), how would one install it with a black screen.
It's pretty EFFing hard to do anything when all there is, is a black screen!
To get my system backup up and running normally I had to boot into safe mode and uninstall WindowFX.
instead of blaming stardocks crapware as u call t,blame windows ever changing os crapware that is microsoft.give the guy a break.it isnt easy trying to manuveur on microsofts craptastic windows 10.
most the time windows is blocking such programs cause they prefer you not to even customze.that happened to the 3rd party login bg changer developers util they finally found a workaroud,but util they did microsofts pull gave lockup/black screens of death too.
do some research before you try to point a blame.think ts so easy,you make these apps yourself.until then let the professionals handle it
keep up the work neil
ps:i appoligize for the typos.my keys have been sticking at times lately.Kudos
Disabling WindowFX would resolve the issue for now.
Be aware that you are using a BETA version of Windows 10. You chose to opt into getting potentially buggy builds from Microsoft and accepted the risk that not all software would be compatible with it. If you were using the released versions of Windows 10 you should not be having this issue.
I do apologise for the delay in releasing an update but unfortunately this needs QA time and this has been in use on other projects lately. I am pushing for an update to be put out ASAP though.
Also keep in mind that many Object Desktop programs like WindowFX and WindowBlinds manipulate Windows UI elements in unsupported ways, so compatibility issues can pop up at any time.
Windows 10 isn't craptastic; you might dislike it's differences, but in my opinion and in the opinion of millions of adopters it's a huge step in the right direction.
Also you don't ever have to use the lock screen picture replacing program because that feature is now part of windows 10: http://www.howtogeek.com/223875/how-to-change-the-login-screen-background-on-windows-10/
If Microsoft wants to prevent users from customizing something - which I doubt they do - they wouldn't trip a BSOD, rather they would just lock off the feature in the ui/ registry.
Be aware that you are using a BETA version of Windows 10. You chose to opt into getting potentially buggy builds from Microsoft and accepted the risk that not all software would be compatible with it. If you were using the released versions of Windows 10 you should not be having this issue.I do apologise for the delay in releasing an update but unfortunately this needs QA time and this has been in use on other projects lately. I am pushing for an update to be put out ASAP though.
Yeah, instead of complaining about updates causing compatibility issues with my favorite programs, I post my findings on related forums so the problems get solved quicker. That's what beta users should do.
Thanks for looking out for us.
Now that WindowBlinds 10 has been officially released, will more internal testing be able to be done on this issue? Hopefully another beta for WindowFX 6 can be released soon.
Update: This issue is still present with WindowFX 6 on Windows 10 build 14291.
yep, still cause a black screen and cursor on that build..
Since Neil is no longer responding to this thread, not sure if Stardock is still addressing this issue or not. Anyway, Windows 10 build 14295 released today still locks up the system when enabling WindowFX 6.
does window blinds still work on the latest windows release?
it works fine for me on 14291..
Yes, WindowBlinds 10 still works fine on build 14295.
hope that windowsfx gets fixed soon; its one of my favorites!
has anyone gotten winFX to work properly on the latest insider release, 14316?
thanks
I'll take a look on Friday, see what I can see.
were you able to get it to work?
thanks!
It's been almost 10 weeks; have there been any discoveries?
Since my initial post, all versions from 14251 all the way now to 14316 are incompatible.
I miss some great features from WindowsFX, but I took the trade-off to be a Windows Insider in the fast lane, submitting bug reports to microsoft and to creators of incompatible software.
There are many great features available to you once you register, including:
Sign in or Create Account
