Can it be that WB5 is quite buggy?

I installed WB5 and it seems quite buggy.
When I apply a skin the colors are sometimes wrong and when I unload WB the computer sometimes freezes.
I also wonder if there is a way NOT to start WB when Windows starts (like it was possible in previous versions).

7,629 views 14 replies
Reply #1 Top
if you set to the default skin (all the way to the left in the list) does it not stop WB from running at startup?...it used to
Reply #2 Top
Ok, thx.
At least this works (in previous version you had the option to "prevent windowblinds loading at startup" in the display properties window).

But this doesn't fix the other problems (wrong colors, wrong font sizes).

I also found another problem that's really annoying: My older 3rd party skins that worked before cannot be applied when WB5 is installed.
Reply #3 Top
Strange, as WB5 works perfectly fine on my computer. Proper colors, correct font sizes and when I have unloaded WindowBlinds my computer has never frozen. So, for this user I would not agree with the title of your post "Can it be that WB5 is quite buggy?"
Reply #4 Top
Not buggy for me either. Your access says 'current customer' so i'm assuming you're using a legal copy.. update your vid drivers, try uninstalling wb4 if you still have it, put 5 on by itself, and if you've still got trouble might wunna email stardock about it
Reply #5 Top
Prevent WindowBlinds from loading on startup was a 9x/2000 option only in WB4.  WB on XP has never provided such an option.
Reply #7 Top
Happy to say that all versions of WB I have ever had never had any bugs. WB5 Rocks!
Reply #8 Top
Ok, thx for your answers.

I have a NVIDIA Geforce4 420 Go graphics card

Prevent WindowBlinds from loading on startup was a 9x/2000 option only in WB4. WB on XP has never provided such an option.
Ok, this could be possible, but at least WB wasn't loaded automatically when it was unloaded before the computer was shut down.

But choosing the first "skin", like someone posted above, seems to fix this problem.


try uninstalling wb4 if you still have it,
WB4 was never before installed on this partition, but what I did was to copy the patched uxtheme.dll to this partition in order to apply the 3rd party skins (not *.wbas but normal *.themes). This uxtheme.dll was most likely patched by WB4.
So I could try to find an original uxtheme.dll and let WB5 patch the original one...

Reply #9 Top
WB5 doesnt 'patch' anything, certainly not the uxtheme.dll.
Reply #10 Top
Windowblinds REPLACES uxtheme.dll, when you use WB...instead of XP using uxtheme.dll, it uses wblind.dll.
Reply #11 Top
Well it must have patched the uxtheme.dll (or replaced it, whatever...) because after I installed WB4 I was able to use other skins as well. This was still possible even after I uninstalled WB4.

Now that I uninstalled WB5 and replaced the uxtheme.dll with the original one from the WinXP CD and re-installed WB5 I still experience the same problems as before.
Reply #12 Top
WB4 and WB5 should not be installed at the same time on the same machine. Instead of hacking the directories, try installing the product in the appropriate manner.

Posted via WinCustomize Browser/Stardock Central
Reply #13 Top
> WB4 and WB5 should not be installed at the same time on the same machine.<

This never happened.