Window blinds only apply to start menu and taskbar

all other windows remain vista'ised

When I install a new windowblind I only see the effects on the start menu and the task bar.  All my other windows remain unchanged, in their usualy Aero Vista state.  Is there an option I've checked somewhere which is causing this override?  If someone could point me to a solution, I'd be ever-so grateful.

Michael

5,921 views 13 replies
Reply #1 Top

Open the WindowBlinds Configuration screen and click on "System info" then click the "Copy text" button. Paste that info here.

 

Reply #2 Top

If someone could point me to a solution, I'd be ever-so grateful.
End of quote

Do as Hankers has instructed you with also info as to what you are installing the program on...

such as OS and version info of the program with what firewall and /or anti-virus/spyware you are using.

Reply #3 Top

Thankyou.  I have a  slight  correction to my original post.  The skins are being appliedin other areas too,  such as various buttons and what-not.  From what I can see, they are mainly lacking on the window panes of individual windows, including the minimise and close buttons.

I'm running Vista Ultimate SP1 on a Dell XPS 1330 with 4Gb of ram.

I use AVG8 for my security suite.

I have Impulse installed and although I have theme manager also installed, I've been using windowblinds directly through Impulse.

Your computer has a Windows Experience Index base score of 4
Your Windows Graphics Experience score is 4

WindowBlinds version : WindowBlinds 6.3 (build 112 x86 - Vista Edition)

WindowBlinds is installed correctly on this PC
WindowBlinds appears to be activated on this PC
(Generic PnP Monitor) 1 is attached to NVIDIA GeForce 8400M GS

Wblind.dll      2008/11/03 19:07:20
Wbsrv.dll      2008/09/22 21:59:22
Wbconfig.exe      2008/11/18 20:02:54
Wbload.exe      2008/04/28 16:35:14
Wbhelp.dll      2008/04/28 16:35:07
Tray.dll           2008/04/28 16:35:21
Wbload.dll           2008/04/28 16:34:28
Screen.exe      2008/07/22 15:10:09

Reply #4 Top

Which WB are you applying? is it with all of them such as thos ethat are for vista in wb config - like diamond how does it apply and be sure you are applying the vista version...

GT B)

Reply #5 Top

It is happening with all of them, Vista version or not.  For example if I apply the diamond skin, the only changes that occur on the windowsblind configuration menu is the slider at the bottom, and possibly the highlight colour in the drop-down menu.

Reply #6 Top

Have you rebooted since you installed windowblinds?

If that doesnt work then reinstall windowblinds

If that doesnt work them im out of ideas... :D

Reply #7 Top

Yes I have rebooted since.  This is a problem I have been having for a while.  I'll try a reinstall and will report back.

Reply #8 Top

There's an option under 'Settings' > 'Advanced User Settings' which allows you to select Aero frames and keep the rest of the skin. Make sure that option is not selected.

Reply #9 Top

I've unistalled and reinstalled, rebooting along the way.  I have undone any vista tweaks which I had applied through SpeedUpMyPC 2009, and still WindowBlinds remain the same.  Applying any skin leaves the window panes, minimise, restore and close buttons unchanged.

Anything else I can try or is this something I should contact stardock about?

Reply #10 Top

you could try -

Try uninstalling WB using Impulse.

Then check for any WindowBlinds Registry Keys that may have been left over. If you find any of the following, delete them;

HKEY_CURRENT_USER\Software\Stardock\WindowBlinds

HKEY_LOCAL_MACHINE\SOFTWARE\Stardock\WindowBlinds

HKEY_LOCAL_MACHINE\SOFTWARE\Stardock\ObjectDesktop\WindowBlinds

Reboot your PC, and re-install WB.

If that doesn't resolve the issue, please email [email protected] and start a trouble ticket. They will be able to assist you.

Reply #11 Top

Tried the above with no difference.

Thanks all for the attempts at help.

I'll contact stardock support for a solution.

Reply #12 Top

Thankyou Fuzzy Logic.  I didn't see your post there.  I knew there was a setting somewhere that was causing it, and that was just the one.  Thankyou so so much!!