Major problems with WB on Windows 10

Sounds to  me like a borked install. I'd reinstall right over top of it, if it was me. And if that didn't fix it, then I'd try the purge/reinstall. Some have success with it, I never did.

Don't use object desktop Manager to install.

Get WB from your downloads page.  ODM is known to cause installation issues.

Hello,
Sorry to hear you are having issues. Need to inform that some skin that work on Windows 7 might not work properly on Windows 10. Unless the original designer update their skin to work with Windows 10, it might not work in Windows 10 environment.

Seti Green last update 2002. https://www.wincustomize.com/explore/windowblinds/2333/

Can't find WoodXP but XPWood both was last update 2001 and 2006. https://www.wincustomize.com/explore/all/search/wood+xp

I have tested some of my very old skin like sonix.wba and it just trash my Windowblinds 10.

Basj,
Stardock Community Assistant.

Just checked that in the new Edge basj, no issues at all here.

Which issue are you talking about? Seti Green or WoodXP and what it got to do with Edge?

Thank you,

Basj
Stardock Community Assistant.

Hi all;

first, I'm not using Object Desktop at all, I'm only using Windowblinds

second, you are correct, @basj !  It is XPWood, not WoodXP... oops !!  I love *both* of the XPWood skins.

Okay, I just loaded another theme, Radio, which is a paid theme and is quite recent.  It shows the same problem with taskbar as the others do.

In fact, I can provide more details about what is going on at this point:

1. The only element which is drawing incorrectly is the taskbar/notification-bar area. 
New windows open and draw correctly.  Start menu is fine.

The issues with the taskbar are that it is just drawing solid white, not using the WB theme.
Taskbar icons (for not-opened apps) show white as well, until I hover the mouse over them, then they switch to the WB image.
Icons for opened apps show properly with the WB image.

notification area - everything is just flat white, even when I hover over them.
popup windows (including 'show hidden icons' window) use the WB theme.

Does this provide any useful info?  Would an image of the offending taskbar area be of any use?

//**************************************
There is also the second issue that when I changed Windows color scheme from Black to White, I completely crashed the machine (including WB) and had to power-cycle it.  However, this is *much* less important, because I won't do that again!!

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

Just make sure to re-download the latest version from your account. Reboot after the purge. Reinstall using the one you just download. Reboot again and test it out. Please test out with those default skin (Acrylic, Arsenic, Corporate etc etc) that come with WB first. If you still see an issue. Please make a screenshot of it and post it here.

Thank you,

Basj
Stardock Community Assistant.

Okay, running the WBPurge batch file as admin...

Got an error message:
'the module ...\WBCore.exe was loaded but the entry-point DLLUnregisterServer was not found'
and
'make sure ...\WBCore.exe is a valid DLL or OCX file and then try again.'
I got the same errors for another file, but didn't catch the name.
It has now completed, and I'm back to normal Windows.
Will continue with the instructions!

Interesting point... on 'My Downloads' page, the WB10 installer is listed as "WindowsBlinds 10 Upgrade" ...
I wonder if I should first install WB 8, then upgrade to WB 10 ??

For now, though, I will proceed as if the WB10 install is okay.

Okay, after following all those instructions, I loaded the 'Acrylic 7' theme, and it still behaves the same.
 Here is a screen capture of the taskbar.
hmmm... I don't see any 'attach image' option here, and drag-and-drop does not work... I'll try uploading to Flickr and linking...

https://www.flickr.com/photos/derelllicht/49464670752

Hello,

Please try the cleanboot steps to see if something is conflicting with WB. : https://forums.stardock.com/486023/windowblinds-support-faq#cleanboot

Try it and report back.

Thank you,

Basj
Stardock Community Assistant.

A good thing to remember with WB is, Uninstall, reboot, install {WB}, fill out the activation don't load any skins and reboot again. Where your at now try a reboot and see if it applies.

Well... that was interesting...

@almonty - I did that last reboot... no affect on the symptoms.

@basj - Okay, I did the cleanboot routine... and got a different result.  First, when I logged out after creating the Admin account, then logged back in with that account... Windows came up with the 'Acrylic 7' theme properly loaded !!  So far so good...

However, once I try to load any other theme, even one of the default themes, then I get a variant of my original problem - except that now the inactive/idle taskbar items are drawn as Acrylic 7, instead of Microsoft Standard White...  As before, any active apps have their icons drawn with the current theme, and hovering over an icon draws with the current theme...

Okay, this be resolved... dang it...
I was using a start-menu replacement program called Open Shell, which is a fork of the older Classic Shell (including Classic Start Menu).
I didn't think it was involved with this issue, because it does not affect the taskbar.  However, I went ahead and removed it, restarted Windows, and now WindowBlinds is working just fine.  New skins load fine, and are remembered across restarts.

Damn... I *love* Classic Start Menu, I hate losing it...

Yeah, I know... but Classic Shell was free, and highly configurable, and I've loved it for *years* ...
Trust Microsoft to break anything that we users actually value...

I've been using Open-Shell with WindowBlinds on several Windows 10 machines.  The only problem I've had so far is that some skins use a *ton* of CPU or GPU resources.  None of the skins (Acrylic 7, Corporate, Diamond) have resulted in the Taskbar problems that you've described.

Really ?!?!  That's interesting...
Are those all skins which came with WB?  Or are some of them user-developed skins?  All of the ones that I want are user skins...

I'll go back and try Open Shell again... I had tried it at first but had some issue with it.  I'll give it another try.

=======================================
Well, I just tried Open Shell 4.4.142, and it has exactly the same issue...
Windows version 6.3.18363 (build 18363)
WB version 10.84 (059 - Windows 190 Edition)

Everything works fine, except for the taskbar and notification area...
On the taskbar, any items which are currently open, are drawn using the WB skin.
However, inactive/idle items, and the rest of the taskbar, are just drawn with solid white background.

Yes, those are all skins that came with WB10.  There are apparently a lot more skins that come as part of WB10; I saw a *lot* more skins on a Windows 7 test machine (where I installed WB10).  So it seems like there are definitely differences between Win7 and Win10 that WB10 needs to know about.

My biggest problem has been that I'm running Win10 on several VM test machines, and certain skins consume *huge* amounts of CPU or GPU time.  The Diamond skin looks (visually) the best to me (and plays well with Open-Shell), but it makes the VM almost unusable due to GPU loading.  (This is on 3-year-old hardware, so maybe not an issue on newer machines?)  Corporate runs just fine on all the machines, but I really want the look of Diamond, so ...

I've been using SkinStudio to slowly modify the Corporate skin to look just like the Diamond skin.  It's slow and painstaking, but I'm learning a *lot* about how WB works.

Maybe that would be an option for you?  Take an existing Win10 skin that works, and start modifying it to look like the skin that you want?

Hope this helps,
-Jim 

Hi Jim;
I also went back and tried Acrylic 7, Corporate, Diamond, and they all have the same issue...

As far as trying to modify some of the skins, I'm confident that this is *way* beyond my artistic skills!! 
I really wish I could understand why this doesn't work for me, since it works for so many other people...

OTOH, I don't have *any* performance issues with WB10 on my Win10 machine.  It is a dual-core MS Surface Tablet, which is a sort of lower-midrange machine, but there are *no* bottlenecks or excess CPU usage with any programs.

Sorry to reopen an old topic but not sure if you noticed it but the taskbar issue seems to have been resolved finally. I'm using Open-shell now with the latest version & the taskbar is working fine. Personally I hated using Start10, complete garbage compared. (Sorry Stardock. I've been a fan since the early 2000s & Objectbar was a personal favorite back in those days but Start10 needs some major work.)

Hello,
Sorry to hear you are having issues. But, I don't issues on Start10 on my system. What issue were you talking about?

Thanks
Basj,
Stardock Community Assistant.

Not really an issue more than it's just a poorly designed piece of software. Bad interface & lack of customization (strange since this is all about customization). Look at Open-Shell, there are tons of areas that can be customized. I'd say the interface isn't a great option for "beginners" but in Start10s case it's just plain & lacking. If it's about "keeping it simple", that's fine, but adding an advanced area for advanced users would be a great step forward.

A great example is the start button. Open-Shell allows for overflow or whatever you want to call it, Start10 doesn't, which when used with WindowBlinds just doesn't even make sense. Also, start button sizing, I can't find anywhere in Start10 to change the size.

Yes!! I probably should have come back here and updated this thread.
The current version of Open-Shell has resolved this conflict, and now works pretty well with Windowblinds.
I was grateful that the (volunteer) maintainers of that program took the time to look into the issue.

It is worth noting the most recent WB update also addressed this with a workaround for the issue their side.

So you are covered both ends.