Windows doesn't use theme-defined colors on startup

I have to reapply the theme every time to get the correct window colors

from Stardock Forums
I'm using the Arrow skin with WB6 on Windows XP SP2. It defines colors for buttons and window backgrounds and such as light gray. Every time I restart, the skin is applied, but those colors aren't, so I've got the transparent glass window borders and everything, but the colors of the windows themselves (seen in file property dialogs, etc.) is the default XP tan color instead of the silver/light gray it should be. If I open wbconfig and just hit the apply button without changing anything, it reloads the skin and then all the colors are correct. Any idea why it loses those settings every time I restart? Here's my system info:

WindowBlinds version : WindowBlinds 6.02 (build 43 x86)

WindowBlinds is installed correctly on this PC
WindowBlinds appears to be activated on this PC
Your machine supports per pixel borders on WindowBlinds skins.

(Default Monitor) 1 is attached to NVIDIA Quadro NVS 140M

Wblind.dll 2008/01/14 17:02:20
Wbsrv.dll 2008/01/14 17:02:10
Wbconfig.exe 2008/01/14 17:02:35
Wbload.exe 2007/09/27 17:47:44
Wbhelp.dll 2007/08/27 11:54:07
Wbui.dll 2007/11/06 10:13:05
Tray.dll 2007/09/12 17:58:21
Screen.exe 2008/01/14 17:02:18
windowblinds
7,457 views 5 replies
Reply #1 from WinCustomize Forums Top
Not an answer, but barring an actual answer here's a method I use that makes such a thing less annoying:

I have a similar problem with a few of my favorite skins, they frequently don't load properly at boot but will apply fine afterwards. I figure it's boot order, boot up load, or a side effect of hyperthreading/dual processing, or whatever. Anyway, when I want to use one of those skins, I create a shortcut to wbconfig.exe in my startup folder. The wb configuration screen then opens up at boot, and after the boot is complete I just click on the "Apply my changes" button to re-load the skin.

An couple of extra clicks and a few extra seconds at startup, but it mellows the annoyance factor.
Reply #2 from Stardock Forums Top

Still getting this problem.  DaveRI's solution works, but it's a pain in the ass.  Sometimes I even have to click apply twice to make it take.  No one from Stardock has anything to add to this?

The Political Machine 2024
Reply #3 from WinCustomize Forums Top

I would start by reposting your info,it's badly out of date now.You have updated windowblinds since Jan.21st I assume.

Current info would no doubt be helpful to troubleshoot your problem. :)

Reply #4 from Stardock Forums Top

I am having this same exact problem. I have attached my information, which is up-to-date, since I have downloaded and installed WindowBlinds this morning.

WindowBlinds version : WindowBlinds 6.2 (build 61 x86)

WindowBlinds is installed correctly on this PC
WindowBlinds appears to be activated on this PC
Your machine does not support per pixel borders on WindowBlinds skins.

This is because :

Your computer graphics hardware does not support acceleration of per pixel alpha.  WindowBlinds requires this for per pixel alphablended borders as without it performance would be poor.  Please see if you can obtain new drivers for your graphics hardware.  Recent ATI & NVIDIA boards should support this feature.  Onboard graphics tend not to.

It appears you have enabled limited per pixel mode, so WindowBlinds will support per pixel, but with no hardware support.

(Plug and Play Monitor) 1 is attached to ATI FireMV 2200 PCI
(Plug and Play Monitor) 2 is attached to ATI FireMV 2200 PCI Secondary

Wblind.dll         2008/07/22 10:53:20
Wbsrv.dll         2008/07/22 10:53:10
Wbconfig.exe         2008/07/22 10:53:32
Wbload.exe         2008/04/26 16:14:14
Wbhelp.dll         2008/04/26 16:14:07
Wbui.dll         2008/04/26 16:14:05
Tray.dll              2008/04/26 16:14:21
Screen.exe         2008/07/15 11:31:09

 

Reply #5 from Stardock Forums Top

Can anybody help? I am using DaveRI's suggestion, but would rather find a solution instead of a workaround.