Win10 Insider 15002 breaks Windowblinds

We are poking at things.

Thanks for reporting

Just to add to this save starting a new thread, with preview build 15007 regardless of what skin I select the background of the "Show Hidden Items" popup from the system tray is always a manky dull grey/blueish colour and ignores any transparency settings. I've had to revert to default skin and stop windowsblinds running as that bit is just so out of place visually.

Good luck.

Edit... I've just downloaded the beta and will see if this makes any difference.

No difference, I selected a random theme for a screenshot.

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

Also, typing in Cortana or anywhere else does not work on any of the MS 150xx builds.  Hoping there is a fix soon.  I know there will be.  The Windowblinds team is awesome.

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.

i cant even get windowblind 10.5.1 to install on 15014...

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.

thats the weird thing; in the object desktop app, I download and install windows blinds, 10.5.1 beta, it installs, but then never shows up as an installed app anywhere..

very weird

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?

I'm sure Stardock is interested in WB problem reporting. 

However you expecting to have a problem fixed on insider builds is not realistic as soon as they are released. The 15019 was just released yesterday I believe. As long as you keep using every insider build that comes along you may never be problem free. 

Note: Just 2 days ago you reported on insider build 15014. Now 15019. Keep using insider builds and it may take a long time before you stop having problems.

Also you say you are up to date with all your software. Since you like beta builds so much which actually is what insider builds are try the WindowBlinds beta version 10.5.1.

10.51 beta doesnt  work either, so thats not the answer

This is all I can add. Have been here a long time and because of Microsoft with always changing thing have seen a lot of Stardock software being needed to be updated. They have done this for years with great success.

Best I can say to you is if you or anyone keeps installing insider builds don't be shocked when something doesn't work. Remember software like WB has to interact with the GUI and totally inside Windows 10. They aren't some program that just has to work along side of Windows.

My advice would be to not install insider builds and sooner or later you will have SD software catch up to the version you are using. By all means report specific problems or as I like to say situations. If you like to be a Microsoft tester by all means do it just don't expect all software to keep pace. The name insider build is nothing more the using the word "beta". Could have just as easy been called "bets build 15019".

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..

When you have started to use them, you can get out only when next stable one is released.

Also all insider build since last stable release of W10 have worked just fine. Only after 15002 there has been problems. Those problems should be reported to both SD and MS. I have done it and then gone back to the previous version I have had installed: 14986. So I think it's important to keep track if/when the bug in either side is fixed that caused this havoc. It's not possible if new builds aren't tested.

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

Davebax sai: Best I can say to you is if you or anyone keeps installing insider builds don't be shocked.....

As far as I am concerned I think I have posted very positively and certainly am not surprised at the problems. I am a very experienced user and know full well what being an Insider entails thank you very much.

I post merely to help Stardock get a handle on things and to reassure others. Davebax, did you not read my post where I explained why I was puzzled why the beta versions of Win 10 make problems for WB yet there haven't been any fundamental changes to the core? Do you understand programming at all?

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.

Didn't read the whole thread but, lots of bugs on IP Build 15019 as well.

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!

Its called adapting. You can't know what's coming ahead of time, you can only react when it happens. That's life.

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.