I had the same problem, so I applied the uxtheme patch to Windows XP. This allows the OS to use unsigned 3rd Party themes. Given how many people have this problem, perhaps this is more to this answer, including a possible software bug?

If you are at the end of a 30 day trial, then WindowBlinds will not function. That it what it is designed to do - 30 days means 30 days... You will have to uninstal it. The either not use it, or purchase the full version.

Try selecting an XP type theme from desktop properties. Patching uxtheme.dll is not recommended.

Interesting, IceIsles joined us yesterday   

Is it not better to teach then ridicule as it is better to learn and gain wisdom?    

Damn that's good, got to write that one down.      

I gotcha. With me, it was a matter of necessity. I wanted to use WB6, and this was the only way to go about it. I generally agree about not altering system files, although MS has gotten a lot better about locking users out of critical services, etc.

For some reason, Windows wouldn't let me select a "modified theme" when I installed WB6. Subsequently, although WB6 was installed, everything was permanently stuck in "Classic" mode. I honestly don't know much about the uxtheme patch, but it did the trick for me. I figured I could always restore a backup if it torched my OS.   

i am using windows blinds 5.1 xp pro sp2 x64 i applied the uxtheme patch but when i rebooted it told me that it could not find uxtheme.dll so i had to resort back to the other one

WindowBlinds 5.1 System Information Report:

STATUS : WB+ SRV+ HLP+ UI+ TRAY+

WindowBlinds is installed correctly on this PC.

WindowBlinds appears to be activated on this PC

Your machine supports per pixel borders on WindowBlinds skins.

You have one monitor in total.

(Plug and Play Monitor) 1 is Radeon X300/X550/X1050 Series

Wblind.dll 2006/10/27 17:20:20
Wblind64.dll 2006/10/09 12:51:37
Wbsrv.dll 2006/10/09 13:25:43
Wbconfig.exe 2006/10/28 18:13:27
Wbload.exe 2005/12/21 01:04:47
Wbhelp.dll 2004/09/18 16:37:07
Wbui.dll 2005/12/06 22:29:06
Tray.dll 2006/04/28 19:27:49

How do you find the "correct" dates? Is it open to the public, or for SD and WB staff/mods only?

Bichur I think what Pugboy is asking how do you come up with current dates for all versions (trial, standalone, SDC).   

For the SDC
every time I upgrade...
I open WB, click system info and voila... there it be

The Trial/Standalone are basically the same, just one has activation
every once in a while some post their standalone info for reference

then i copy to a text doc for later reference

most of the times, with the dates it's not too hard to figure out there's incorrect files involved

for example:

a 5 version came out on 11/28/2005

LEGIT

Wblind.dll 2005/11/28 13:57:10
Wbsrv.dll 2005/11/28 15:52:00
Wbconfig.exe 2005/11/28 16:19:00
Wbload.exe 2005/11/25 19:30:58
Wbhelp.dll 2004/09/18 15:37:00
Wbui.dll 2005/11/20 12:23:40
Tray.dll 2005/11/02 13:28:26

the newest file date is 11/28

then you people looking for help posting:

Cracked

Wblind.dll 2005/11/28 13:57:10
Wbsrv.dll 2005/12/06 21:16:30
Wbconfig.exe 2005/12/03 03:03:36
Wbload.exe 2005/11/25 19:30:58
Wbhelp.dll 2004/09/18 15:37:00
Wbui.dll 2005/11/20 12:23:40
Tray.dll 2005/11/02 13:28:26


Wblind.dll 2005/11/28 13:57:10
Wbsrv.dll 2005/12/03 04:03:40
Wbconfig.exe 2005/12/03 04:03:36
Wbload.exe 2005/11/25 19:30:58
Wbhelp.dll 2004/09/18 15:37:00
Wbui.dll 2005/11/20 12:23:40
Tray.dll 2005/11/02 13:28:26

Wblind.dll 2005/11/28 13:57:10
Wbsrv.dll 2005/12/07 02:16:30
Wbconfig.exe 2005/12/03 08:03:36
Wbload.exe 2005/11/25 19:30:58
Wbhelp.dll 2004/09/18 15:37:00
Wbui.dll 2005/11/20 12:23:40
Tray.dll 2005/11/02 13:28:26

nope