Log Off didn't work. I had to kill them.

Wow.
Email support@stardock.com.  Reference this thread.  Make sure to give them your WB sysinfo.

Happens to me frequently too.. intermittently

Yep, happened here with my first download/install of WB6. Everytime I changed a skin/applied changes thru WBconfig - a new instance of Screen.exe. Desk.cpl access via Display properties/Appearance tab is also fubar when Windowblinds is unloaded (works fine if WB is running).

Followed Bichur's advice from another thread and now the multiple Screen.exe problem is gone. I haven't installed the latest build of Windowblinds for fear that something else will go wrong (still using WindowBlinds 6.0 (build 36 x86)). Desk.cpl still doesn't work - I could probably reinstall that via command line - but as long as I'm running WB it's not a problem.

Is screen.exe supposed to be running with WB applied. I checked my computers and I don't see it running. (2 XP and 1 Vista)

ALMonty: Only if you're using WB6 (and possiply only in Vista) - not sure though.

I have WB6 installed on my CPU's

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

WindowBlinds version : WindowBlinds 6.01 (build 57 x86 - Vista Edition)

WindowBlinds is installed correctly on this PC
WindowBlinds appears to be activated on this PC
(HP w2207 Wide LCD Monitor) 1 is attached to Radeon X1650 Series

Wblind.dll 2007/11/06 10:13:20
Wbsrv.dll 2007/09/24 18:08:26
Wbconfig.exe 2007/11/02 14:30:08
Wbload.exe 2007/09/27 16:47:44
Wbhelp.dll 2007/08/27 10:54:07
Tray.dll 2007/09/12 16:58:21
Wbload.dll 2007/09/12 16:58:28
Screen.exe 2007/11/02 18:37:51

I see it installed here. Not really worried about it, everything works perfect I was just curious.

As vStyler said, it does not occur all the time. Yesterday after a reboot, I applied different skins a few times and did not see a single instance of screen.exe running. I will report it to stardock support if I can consistently reproduce it. Not even an annoyance at this time.

as far as I can figure out, screen.exe is only suppossed to run while you are in the process of applying a skin. It is the program that actually applies it. I.E., when you click 'apply my changes' that's when 'screen.exe comes into play.....

That's right. That is why you will see this problem only if you apply skins many times. Another important factor I forgot to mention is that I am on XP 64. A few weird things happens on XP 64 anyway. I am just happy that I have WB6 on this platform despite the fact that there are not many customers (at least not enough to warrant a separate build) for it.

I thought Screen.exe was the blur while please waiting effect

Could be. It is just something that gets invoked when you apply a skin in WB6, AFAIK.