We are poking at things.

Thanks for reporting

Jaknet, do you have the same problem as me though?

Build 15014 hasn't made any difference to WB unfortunately so it may be something fundamental that WB need to look at, which I'm sure they are doing. Build 15014 has introduced transparency and more color tweaking options so this may be a clue.

What error are you getting?

It should install, but the modern apps do not skin correctly.  This is fixed in our latest internal WB build that's not released yet.

I've just downloaded and tested the latest WB 10.50 on my new build 15019 pc desktop.

The same problems I'm afraid.

It is only minor, apart from Chrome refusing to launch. The window controls on top right don't seem to work. Actually they do, but are displaced, so to maximise, don't click on the maximise icon but just to the right of it. Clicking the maximise icon minimises the window!

I am puzzled though by the difficulty Stardock are having with Win 10. A stable retail version of Win 10 has been out for a year and first there was a beta WB 10 then a retail WB 10.50 and supposedly this meant WB developers had cracked it.

But I can't see that once the retail Win 10 was released that Microsoft would make any fundamental changes to the code that would subsequently break WB??

The latest insider builds do have more changes in their graphics, such as transparency, so is it this that foils WB? If so it means that WB must be digging deep into the Windows code Are they using MS approved hooks? I remember the fuss when Symantec Norton were discovered to have been given exclusive access to code areas for their AV. Does Stardock have a good relationship with Microsoft?

10.51 beta doesnt  work either, so thats not the answer

agreed; im surprized at how ofter window blinds has worked in the last y ear or so of using it on insider builds...hopefully it get straightened out soon

its weird how I can install it, but it doesnt show as installed in object desktop, and I have all the files in programfilesx86 when I check in file explorer..

If you really don't understand how beta / insider builds work, then I'd suggest not using them as this is complete BS. You can leave the insider builds whenever you wish and revert to the current live build

Regarding WB and the insider build, Microsoft do indeed make large changes in those and sometimes they introduce bugs, or partially implemented new features.

WB has been updated internally to handle this, but this is not publically released yet as it is linked to some other tweaks we have been making to WB recently.  Generally WB should continue to work on insider builds, but there are exceptions where significant changes have been made. 

It is worth pointing out there is no such thing as Windows 10 anymore, there is retail Win10, November Win10, Anniversary update Win10 and now the insider builds of the Creators update.  In the past these would not have all been called the same operating system.

It is also work pointing out that if you use an insider build of Windows 10 we will not offer you formal support as you chose to use unreliable beta OS updates.

Yes 15019 has introduced a few quirks that weren't present before unfortunately. Nevermind a new build is due soon. What bothers me is that Win 10 is now a service and will never be "finished" in the sense of in the past we'd have Win10.1 and so on. So how will WB developers cope with this? I suppose they will say they can only support the bi-annual public retail releases such as the up coming Redstone or whatever it is called in April? This means they will always be playing catchup. Because of the deep hooks WB needs to pull off its fancy tricks, WB have a bigger problem than most software companies I think.

An informative comment from WB would be of interest to us geeks!

Well thank you for your information and mocking me. I rather believe MS than you though. https://support.microsoft.com/en-us/help/10584/windows-10-stop-receiving-insider-builds

Meaning the MS recommended way is to wait your machine is updated to release version and then opt out from insider builds. Bus as the anniversary update hasn't been released opting out isn't an option. It's possible to go back to previous build if needed, which I have done as I mentioned.