that is very odd as ive had no issues with windowblinds and 14372 and I do fresh installs.

however on a fresh install of 14376 whitch is now latest build,im now seeing this black screen of death.it kills everything

keep in mind though that experimental builds of windows may be shortly behind until a fix is made.windows stop severely changing the os it seems for awhile now so wb10 was stable until recently.

I have faith tho that stardock will be working on a fix.if not for these builds perhaps the anniversary build that's coming out in a month

Unfortunately it is an absolute nightmare for us to keep in track with insider builds as Microsoft do not offer them to download as ISOs and the insider preview updating seems to break itself regularly.

I have no idea what Microsoft are thinking in not offering downloads for developers!

Can you both please file a bug with Microsoft too so they are aware of the issue as clearly a break so close to a major update seems like a bit of an opps moment for them!

I'm going to test a theory course I'm unsure how itll work out lol

I do know I'm prolly going to need another reset for my stuff as I do clean installs after uninstalling but seems stardock still wants to count me as if I'm using multiple computers.there needs to be a better reset option for those of us workin on the fast bug releases.we clean wipe a lot so we can know whats what

I need to file one already for cursorfx plus as its reached its limit.

as for letting Microsoft know whats what eh.ive seen how those posts go.they use automated manual fixes all of whitch hardly work

kudos tho to stardock.you guys are real troopers.ive been a supporter for years.i never lose faith.

BTW when the issue occurred, did Ctrl-Alt-Del show the usual start taskmanager, log out etc options?

If so I would be curious what happened if you picked TaskManager.

actually the funny thing is it crashes the entire system even that with an error message stating that.

sorry for late reply.i had to redo my windows.

I'm downloading the build that's been turned into an aio installer for 14372 now since that's the last one I remember it working in.once I'm on this ima disable my insider for a bit until this issues resolved as I have pro I can delay updates if need be or just keep on the slow build since this is only seeming to happen on the fast build for me atm

I do know if Microsoft keeps up with errors a lot of people will feel like doing this

I was able to reproduce the problem and I believe know whats up.  If I am right then it is an easy fix and I will push for this to be out ASAP.

If anyone else encounters this issue, holding down ctrl when you login will stop WB from loading and thus allow you to get past this problem.

Probably the best way to describe the situation with MS "insider builds" is that the OS itself is the thing that needs bug reporting, not any proggy attempted to run on it/them.

Microsoft is the entity to post issues/concerns/complaints....so that they can improve their game and only provide actual STABLE releases to the public that WON'T break Third Party Programs.

Meanwhile, everyone else keeps chasing 'issues' with the Public Releases and their software.

In an ideal world an OS would NOT 'evolve' and break already-compatible/working programs.

....but you're going to need to petition MS for that one...

It's a nightmare, Jafo.

My biggest worry these days as a developer is that Microsoft will eventually break compatibility in a way that cannot be easily fixed or worked around.

Just a note - yes, it was 14376 that broke me and confirmed that I cannot use CTRL-ALT-DEL or get to task manager.

We've just released a beta that should resolve the issue for Microsofts's beta: http://sd.stardock.com/zubaz/WindowBlinds_10.0.7_beta_setup.exe

Please let us know if you have any issues.

You guys rock. I will try this shortly and report back.

Fixed! Thank you!

The .7 beta did not fix my blank screen problem with the latest Windows Preview build, 14376.  Am I missing something?  Was I supposed to uninstall and reinstall?