LightStar LightStar

Microsoft Once Again Ruins Windowblinds - HELLO???!!!!!

▼

Microsoft Once Again Ruins Windowblinds - HELLO???!!!!!

I wish they would stop doing things like this!

from WinCustomize Forums

Well, lets all thank Microsoft again for screwing up Windowblinds. The Windows 10 update to version 1809 has messed up the explorer background color in the treeview area on the left. It is being forced to white, and the only way to fixed it is to set the Windows color in SkinStudio or WB itself in the Modify Style, Change System Colors area to match the rest of the explorer area. But doing so screws up many applications that need to have a white background in order to remain functional. Microsoft Office, NotePad and many other dialogs and applications that use a white background get ruined.

I sure hope this can be fixed somehow, as it has totally screwed up every single WB skin that uses an explorer color other than white. :-(

1809 Bug

windowblinds
63,982 views 36 replies
Reply #26 from WinCustomize Forums Top

OK, this is now getting ridiculous, it been almost 4 months now! Does anybody even work at Stardock that doesn't do just games any more???

Please fix this issue, or people might as well just quit skinning entirely if Stardock isn't going to support their own products. :-(

Reply #27 from WinCustomize Forums Top

I don't mean to hijack Tom.

BUT

Also how in Win 10 for skins with transparency of the start panel like Naked Noir all you get is a blurring. I know that vStyler intended there to be true transparency of the start panel. The task bar is fine. Start Panel is fine in Win 7 but not 10. There are others skins like that as well.

Other people have confirmed this issue.

I don't like buying something that is advertised to look a certain way but is not that way. From what I can see this is a Stardock problem and should be at least commented on. I complained about it in prior posts but so far nothing at all being said or done about the problem.

Sins of a Solar Empire II
Reply #28 from WinCustomize Forums Top

Reply #29 from WinCustomize Forums Top

BUMP!

Reply #30 from WinCustomize Forums Top

As with most things Windows 10 ....it's probably apt to reread the thread title just once more....;p

Reply #31 from WinCustomize Forums Top

Quoting Jafo, reply 31

As with most things Windows 10 ....it's probably apt to reread the thread title just once more....

Yes Paul, but it was reported almost 4 months ago and the only reply from support was over 2 months ago. 

Reply #32 from WinCustomize Forums Top

With every windows 'update' aka beta release if they only called it as they should....we'd be up to something like Windows 10.6 Second Edition and people might accept that Microsoft is moving deck chairs on the Titanic.

Instead they call it '10' and just 'hope' they haven't broken their own OS.

+1 Loading…
Reply #33 from Stardock Forums Top

We are working on an update for the May 2019 release of Windows, so if the white area is fixable (and I note that if the OS hardcoded white then that wouldn't be something we could resolve easily) then we will aim to fix it with that release.

Regarding blur, check the theme doesn't actually ask for blur vs plain transparency.  The blur on Windows 10 with WB is stronger than it was on Windows 7 so it will be more obvious.

Reply #34 from WinCustomize Forums Top

Quoting Neil, reply 34

We are working on an update for the May 2019 release of Windows, so if the white area is fixable (and I note that if the OS hardcoded white then that wouldn't be something we could resolve easily) then we will aim to fix it with that release.

Regarding blur, check the theme doesn't actually ask for blur vs plain transparency.  The blur on Windows 10 with WB is stronger than it was on Windows 7 so it will be more obvious.

Thank you Neil, all I was looking for was for someone to finally respond. Hope to see a fix next month. :-)

+1 Loading…
Reply #35 from WinCustomize Forums Top

Problem fixed with the release of Windowblinds 10.8, thanks Stardock! :-)