WindowBlinds 10.8 Update is Now Available!

Adds improved skinning support and compatibility features for the upcoming Windows 10 update

Stardock releases WindowBlinds 10.8

Stardock has released a new version of its popular Windows customization app, WindowBlinds.

Version 10.8 adds improved skinning support as well as additional compatibility features for the upcoming Windows 10 update.

WindowBlinds lets you customize desktop interface themes called skins to personalize the look and feel of your desktop. WindowBlinds enables you to make your desktop interface uniquely yours by customizing the Start menu*, taskbar, window frames, and control buttons.

To download the new version, check your Stardock account.
If you don't have a Stardock account, click here.

WindowBlinds 10.8
WindowBlinds 10.8
WindowBlinds 10.8
WindowBlinds 10.8
WindowBlinds 10.8

Don't own WindowBlinds? Get it now.

*Start menu skinning on Windows 8 and Windows 10 requires Start8 or Start10.

64,896 views 39 replies
Reply #1 Top

Since it wasn't mentioned, this release fixes the white background issue in the explorer tree area on WIndows 10 v1809 and higher. However, skins designed for Windows 10 before SkinStudio had settings for those colors will still experience the issue. Any of my skins still having that issue will be updated over time.

Reply #2 Top

This update borked my browser, Opera. After upgrading to 10.8 I got a page crash every time I opened it. Also all my extensions were disabled and had to be manually reloaded, and this happened every time I opened the browser. Fonts were also changed and other features didn't display properly. When I rolled back to 10.6 all these problems went away and everything returned to normal functioning. I remember that there were similar problems with 10.6 and Firefox which were never fixed, I made a thread about that a few years ago.

Reply #3 Top

Quoting dxmc, reply 2

This update borked my browser, Opera. After upgrading to 10.8 I got a page crash every time I opened it. Also all my extensions were disabled and had to be manually reloaded, and this happened every time I opened the browser. Fonts were also changed and other features didn't display properly. When I rolled back to 10.6 all these problems went away and everything returned to normal functioning. I remember that there were similar problems with 10.6 and Firefox which were never fixed, I made a thread about that a few years ago.
End of dxmc's quote

I just checked Opera 60 and am not experiencing any crashes.  What version are you using?

Opera doesn't skin completely though as they have chosen to have their own hardcoded titlebar which is an irritating 'feature' copied from Chrome.

Reply #4 Top

I'm using 60.0.3255.84. I also found that the same problems showed up with Opera Beta, which is a separate installation. It looks like the extensions that were disabled were one that display icons in the toolbar, since that wasn't displaying properly those extensions wouldn't work. Also the address bar dropdown that shows you the mini- speed dial wouldn't display properly.

Reply #5 Top

Quoting dxmc, reply 4

I'm using 60.0.3255.84. I also found that the same problems showed up with Opera Beta, which is a separate installation. It looks like the extensions that were disabled were one that display icons in the toolbar, since that wasn't displaying properly those extensions wouldn't work. Also the address bar dropdown that shows you the mini- speed dial wouldn't display properly.
End of dxmc's quote

I to do not seen any crashing issues with Opera from a new install.  

If you disable all extensions, or open a new 'Private' Opera instance (presumably disabling them by default), do you see the same problems?  If you do not, I would wonder what one, when enabled, is causing the problem(s).

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

Reply #6 Top

The context menus in Windows 10 Explorer still not skinned...

Reply #7 Top

Quoting sdRohan, reply 5

I to do not seen any crashing issues with Opera from a new install.  


If you disable all extensions, or open a new 'Private' Opera instance (presumably disabling them by default), do you see the same problems?  If you do not, I would wonder what one, when enabled, is causing the problem(s).

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

End of sdRohan's quote

Some images showing exactly what I'm talking about.

Haven't tried disabling extensions, I could do that when I have a little more time.

Reply #8 Top

Quoting Vad_M, reply 6

The context menus in Windows 10 Explorer still not skinned...

Reduced 39%
Original 1680 x 1050


End of Vad_M's quote

There is a workaround for that Vad, just install this: https://techtalk.pcpitstop.com/2013/09/30/tweak-your-windows-context-menu/

Works great!

+1 Loading…
Reply #9 Top

Quoting dxmc, reply 7

Haven't tried disabling extensions, I could do that when I have a little more time.
End of dxmc's quote

Just knowing if a 'private' instance works would be helpful:

Thanks.

Sean Drohan
Stardock Support Manager

Reply #12 Top

Quoting LightStar, reply 8

There is a workaround for that Vad, just install this: https://techtalk.pcpitstop.com/2013/09/30/tweak-your-windows-context-menu/

Works great!
End of LightStar's quote

May be I'm stupid :pout: but I can't understand what I should download to apply texture to the context menu background (if the WindowBlinds option does not work)?

Reply #14 Top

Still no Taskbar thumbnail media player controls!?!?!?

Reply #15 Top

I had to see what the hoopla is all about with WB upgrade, and Opera, so, I downloaded it (I don't use it) set it up, and I have yet to find anything wrong, and I'm running version 60.0.3255.84 as well, all is working fine, even in "new private window", just an independent review, from someone who uses Google. :grin:  |-)  

 

Note: Granted, I don't have loads of extensions running either.

Reply #16 Top

Quoting don5318, reply 15

I had to see what the hoopla is all about with WB upgrade, and Opera, so, I downloaded it (I don't use it) set it up, and I have yet to find anything wrong, and I'm running version 60.0.3255.84 as well, all is working fine, even in "new private window", just an independent review, from someone who uses Google. :grin:  |-)  

 

Note: Granted, I don't have loads of extensions running either.
End of don5318's quote

And yet, as can be seen in the screenies I posted, there it is. And also in private browsing. There could be a number of reasons for it, I'm using Windows 7, I suspect others may be using Windows 10. Also, Opera has a lot of settings, particularly having to do with customization, the problem could be related to choice of font size, the type of theme, etc. And I wouldn't call 12 extensions, most of them minor stuff, "loads of extensions". And the problem is there even with all of them disabled and also in Opera Beta, which has less extensions. So there's definitely a compatibility problem there but what it is could take a while to sort out. I've been using WindowBlinds for almost 10 years and this isn't the first time I've seen problems like this. And my experience with Stardock is that they really don't put a lot of effort into tracking down and fixing bugs. Updates to the program have been fairly rare and don't really seem to add much. With Windows 10 market share passing Windows 7 five months ago I think that WindowBlinds is really becoming a kind of legacy program.

Reply #17 Top

Quoting dxmc, reply 16

And yet, as can be seen in the screenies I posted, there it is. And also in private browsing. There could be a number of reasons for it, I'm using Windows 7, I suspect others may be using Windows 10. Also, Opera has a lot of settings, particularly having to do with customization, the problem could be related to choice of font size, the type of theme, etc. And I wouldn't call 12 extensions, most of them minor stuff, "loads of extensions". And the problem is there even with all of them disabled and also in Opera Beta, which has less extensions. So there's definitely a compatibility problem there but what it is could take a while to sort out. I've been using WindowBlinds for almost 10 years and this isn't the first time I've seen problems like this. And my experience with Stardock is that they really don't put a lot of effort into tracking down and fixing bugs. Updates to the program have been fairly rare and don't really seem to add much. With Windows 10 market share passing Windows 7 five months ago I think that WindowBlinds is really becoming a kind of legacy program.
End of dxmc's quote

Well, I'll update my Win 7 to the new Windowblinds 10, and see if I can recreate what you are getting, cause it runs fine on my Win 8.1, and Win 10. |-)  

Reply #19 Top

Ok, I deleted the WB old, then installed the new version of WB (WindowBlinds 10.8 (055 - Windows 7 Edition) - 64 bit OS)
, on my Win 7 OS (Version 6.1 (Build 7601: Service Pack 1)), and installed the newest version of Opera, and it runs fine (even in "New Private Window"), just like on Win 8.1/10, like I said, I don't have any extensions added, for Opera is a new install for me.|-)   

However, I'm sorry you're having issues dxmc. :\  

Reply #20 Top

Here a screen capture of Opera on my Windows 7 system. Not a problem for me except that overshoot tabs covering half of the titlebar. That why I always exclude Opera from WB.

Thank you,

 

Basj,

Stardock Community Assistant

Reply #21 Top

Also Basj, that and it doesn't have a "home" button on the menu bar...what's with that, maybe there is, I  just can't find it in settings. |-)  

Reply #22 Top

I'm going to try restoring Opera to it's default settings when I have the time and see what happens. That's kind of a hassle as it involves switching profiles. Since it works fine with the old WindowBlinds there really isn't a pressing need to fix this. Also, Basj, I notice that WindowBlinds has skinned the window frame in your screenshot, it never skins Opera on my system even though it's not excluded, as you can see below.Also, I have two dozen speed dial elements, including 9 folders full of links, and over 30 bookmarks in the bookmarks bar. And animated wallpaper on the speed dial page. And other customized settings, so you can't really compare it to a fresh install with no bookmarks, speed dials,extensions, etc. But I'll try a fresh profile and see what happens.

Reply #23 Top

dxmc.

Yes that opera you saw on my system is without any add on. I noticed just now when I close opera. Exclude opera from my WB. Reopen Opera. I get almost the same as what your s/shot above (except those dark add on). This problem goes away after I reboot. I guess when opera close it don't really closed. So excluding it and reopen it up again messed thing up. Need to reboot to really see the change if any. So use that as a reminder and most probably you will need to reboot too to see it.

Thank you,

 

Basj,

Stardock Community Assistant

Reply #24 Top

Quoting dxmc, reply 16

There could be a number of reasons for it, I'm using Windows 7, I suspect others may be using Windows 10.
End of dxmc's quote

The irony there is that, when I tested it, WB 10.8 and Win7 runs beautifully together - better than Win10 which has the adopted Chrome title bar skinning issue:

https://cdn.stardock.us/support/uploads/2019-05-14_15-08-13.mp4

Quoting dxmc, reply 16

And my experience with Stardock is that they really don't put a lot of effort into tracking down and fixing bugs.
End of dxmc's quote

While I can understand (and share) your frustration with this (any) issue, I do take some exception to that.  This example should be proof enough of how we respond to issues - community managers, myself, and the lead dev for WB have all responded to your post.  As soon as it was seen, multiple tests were performed in house to see if we could reproduce your issue - we could not.  Also, and as can be seen above, there are dedicated WB users that have lent a hand with trying to see where your issue could be.  All of this can be seen in every forum thread we have today - the participation from Stardock, users, staff and even the owner of the company, in our forums to resolve client issues.

Right now, it does not look like a 'bug' in WB 10.8- rather, a compatibility with an extension or setting you have with Opera.  If it can be found, we would always be open to a WB modification if said issue could be considered commonly reproducible (seen by others) and not overly costly to implement.

Again, your frustration is shared but so to is the desire to see if resolved to your satisfaction.  Please keep us informed on what you find.

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

Reply #25 Top

One of the reasons that I switched to Opera some time ago was that there were compatibility problems with 10.6 and Firefox. Of course the program generally works well with Win7, it's essentially a Win 7 program, it hasn't changed much over the years and my experience has been that it works fine unless you use your browser a lot. That's not all that surprising when you consider how much browsers like FFox and Opera have changed in recent years.

Also, as far as support goes, there are far fewer free skins available now than there were when I bought the program 10 years ago, and 10 skins costs roughly as much as Assassin's Creed: Origins. If that wasn't working properly I would certainly have certain expectations of Ubisoft support, I didn't always have the same sort of expectations of Stardock but that's changed in recent years. While I wouldn't go to the trouble of opening a ticket over something like this I would expect that a visit to the forum would be useful in determining if others are having the problem, or if anybody has any useful suggestions. But as is so often the case, others say they can't reproduce the problem so I must be trolling, computer incompetent, or have hardware problems. The attitude that has characterized some responses here is unnecessary since my purpose here is reasonable and typical of how you approach a problem like this.

In any event, I tired a fresh install of Opera but ran into similar problems, like this;

I also discovered that  Vivaldi and Chrome both work normally, as does FFox. So the problem is specifically with Opera, both Stable and Beta, not with Chrome or Chromium based browsers in general. Unfortunately, Opera crash logs cannot be accessed so pinning down the exact problem is difficult. I do know that Chrome was recently changed and Opera was changed accordingly, among other things the speed dial interface was changed so that speed dial extensions no longer work. But if others are downloading fresh installations of Opera on Win 7 and not getting these crashes then the problem would be with Win 7 settings, not Opera in and of itself. It could, for example, relate to graphics card settings, resolution, that sort of thing. I will do some further looking into it when I have a little more time.