May update 1903

Hello,

I have forwarded your problem to Stardock Support team for their assistance. Please keep an eye on this thread for any updates. We appreciate your feedback and patience.

Basj

Stardock Community Assistant.

Yes, same problem here. I hope this will get fixed. It looks awful. I know this problem have existed Before with earlier Windows versions and Stardock have later fixed it with upcoming WB updates. I hope they do fix it this time again.

I have tried looking into it with Skinstudio but it seems WB doesn't  apply it.

Please try the purge and reinstall steps : https://forums.stardock.com/486023/windowblinds-support-faq#reinstalling

Just make sure to re-download the installer again from your account. Reboot after the purge, reinstall WB and reboot again. Retest and report back here.

Thank you,

Basj,

Stardock Community Assistant

On 2 threads about this, everyone is having the same issue, and some are WB skinners.  I'd say it's not a reinstall thing. More likely a Windows 10 1903 thing.

Just my opinion.

Hello,

Sorry to hear you are having trouble.

We are aware of it and looking into a fix.

Thanks for the report.

----------------
Sean Drohan
Stardock Customer Service Manager

As an update the Tab Preview on the task bar also does not style. 

Just out of curiosity, is there a time frame when WB will be fixed? I haven't used WB because of all the little glitches.

Taskbar isn't getting skinned at all. MS have changed the taskbar buttons and put a line under the taskbar buttons and i hate that!

There's no way to get rid of that line. Seems it's the accent color. Can't stand looking at this. Hope SD can fix this, otherwise i will reinstall former version 1809 which worked just fine.

ALMonty Lord knows when an update will be out! I'm still using WB because that's just what I do! I get around the Date/Time being black on some skins by using Atomic Clock. The Taskbar buttons well I don't like but what are you going to do? 

It seems like forever to get an updated version of WB out there. Some of the responses from Stardock seem curious to me. Re-Install and Purge. These problems are well documented in the Forums and Re-Install and Purge isn't going to work in this situation. Then we hear that in a internal build the taskbar buttons are fixed but no update yet.

Suppose it'll get fixed sooner or later and in the meanwhile if we don't like it that's too bad for us. We are only customers.

Not that I am sticking up for a corporation, nor do I really know anything about their particular programming issue. BUT MS seems to have made a fair amount of changes to the taskbar and Stardock has a range of software tied to that bar. So i can understand some delay to get them all correct. Now a "but" to Stardock, BUT Stardock does not seem to have a alpha/beta program. With how much their customers like what they can do with their software I as a no-nothing none-corporate lackey would suggest they give a Beta testers program a try  to allow us loyal users to get test versions. Also to move ahead with these problems and feel like it is moving in a yeah yeah its coming direction.

Ok I will go back to knowing nothing. Thanks for listening.

P.S. Purge and reinstall doesn't go over very well as with Microsoft's reset your system answer to every single problem post. I know I have a LOT of custom software and settings and that routine (not to mention i have to rename ff.css every time to stop Windowblinds from removing a ton of customization) is not always just a simple thing for me.

They already do that. ObjectDesktop subscribers get beta versions as a perk for subscribing.

OK Thank you for letting me know.

I paid for my individual software(s) so that is a bit objectionable.

But I guess if both parties think its a "perk" to test buggy software then this corporations beta program is exactly where it belongs.  This day is not only educational but shining a light on reasons NOT to purchase. I will continue waiting till I am worthy enough for my software to work correctly. 

It's the middle of June.

No fixes for WB for 1903. The version that was released failed to resolve taskbar buttons and dark font coloring on certain skins.

My question to the Devs is when can we expect a fix? More and more people are migrating to the 1903 - May update. 

I'm not happy with the lack of a fix. Throw us a bone Stardock. At least give us a hint of when we can expect a fix. That's the least you can do.

Chas that's why I posted #7. I thought someone would leave a comment with an estimated time. I've heard number of times that they know, but nothing about if they're working on it.

Guys, everyone here knows I can be as impatient as anyone. I want this fix too, but I know they're working on it. Us bitching ain't gonna speed that up.  If they give us a date, imagine how much hell they'll catch if they miss the date.

I can see why they don't give us a timeline.

Now, if it were an isolated issue, I say bitch away. 

Whatever ( Wifey says when I say that it's passive aggressive behavior)

Hey Jim how's that Karma page working out for ya? I'd send you Karma, but you'd never see it.  

Hopefully they fix it soon. Otherwise it's back to 1809.  

It's MS to blame. They just keep changing Windows 10 as the never ending beta.

Thinking about go back to Win8/8.1. Tired of MS constant changing things.

I have a similar POV.  Unless there is some important feature in a Windows 10 update I just wait.  The big Windows 10 updates always have the potential to break other software, not just WindowBlinds.  I will continue running 1803 until all of the compatibility issues with 1903 are sorted out.

No buttons on taskbar and black text on black taskbar where time/date should be.

Another fine product from Microshit! LOL

Just thought I'd throw my hat in the ring and say the lack of thumbnail previews after applying a WindowsBlinds skin is really hurting my flow.  I never realized how much I relied on that.  I'm sure you all are working on a fix, but in the meantime I'm thinking of unloading WindowsBlinds until I hear word the issue is fixed.  I know Microsoft is to blame for switching things, but since we've bought a product that's supposed to skin, I have an expectation for the product to work.

From my experience, programmers at a company work with beta's of and release candidates of new Windows offerings, so they should have a heads up that something Microsoft has done broke their program; and in my opinion work should be done at that time to make sure when a big update occurs, their product works smoothly with Windows.  Of course there will be hiccups, but they should be rare, and when they come up they should be resolved quickly.  We're getting pretty deep into June after a May release; coupling that with my experiences that software companies test their products and develop them further as betas are released.  Even should of being part of Microsoft Developers Network, you can start having access to working with code they will be putting out a year later.  Even if you only go in six moths beforehand on their beta, you would have half a year to know what Microsoft is doing and prepare your software to work seamlessly with it.   Perhaps you do all this, I don't know.  I just find it dumbfounding that if you do, things could still not be working a month after the product is released.

Forgive me if I'm way off.  I'm just stating the reason for some of my frustration.  I paid for this software, and I need it to work.  So does everyone else who bought it.  

We're still waiting...

If your os theme is set to dark for the taskbar then your thumbnails work fine.

It is only if you use the new light mode that you have issues.  This was not caught in compatibility testing and nobody reported it prior to the release either.

I understand the update is due for release shortly.

Thank you Neil.