My WindowBlinds ALWAYS reverts to Window Classic

Here is my system info

WindowBlinds version : WindowBlinds 6.02 (build 42 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.

(SyncMaster 932GW(Digital)) 1 is attached to NVIDIA GeForce 8800 GT

Wblind.dll 2007/12/22 18:38:20
Wbsrv.dll 2007/12/01 16:43:52
Wbconfig.exe 2007/12/22 18:38:09
Wbload.exe 2007/09/27 17:47:44
Wbhelp.dll 2007/08/27 11:54:07
Wbui.dll 2007/12/01 16:43:05
Tray.dll 2007/09/12 17:58:21
Screen.exe 2007/12/22 18:38:18

YES, I am installinng through SDC.

NO, I never had the trial version installed, so it was not installed the first time I installed WB6 through SDC

I have since uninstalled the WB6 and reinstalled several times to no avail. I have also uninstalled and installed WB5 with the same result.

I uninstalled and installed the trial version which worked.

I then uninstalled the trail and reinstalled WB6 through SDC and back to not working.
3,837 views 12 replies
Reply #1 Top
How many more of these are we going to see? Never a day goes by without a post similar to this. Is there a problem with the software for some people? This guy seems to have done everything possible and even found the trial version is functioning properly whereas the paid version is not.

Rob, hopefully one of the Stardocks guys will be along to look at this but I would suggest you start up a ticket with Stardock Support ASAP. They are pretty good and will hopefully get you up and running in no time.  :) 
Reply #2 Top
RobertRushAADA, some of your date are wrong, this might be a problem regarding your severals tests to install WB6 trial, WB6 or WB5.
What you should do is: uninstall all version of WB, Reboot (really important to do), reinstall WB6 trought SDC then Reboot again.
Then after you should repost your wb system informations here if that still don't work.

And be sure to have the last version of SDC. check the SDC version and copy past it here.

In an other hand if you have reach the limit of activation you should also send a mail to support to get a reset of your activation. So you really should contact support at
support@stardock.com and referring with a link to this post.

Reply #3 Top
Isn't there a 'clean all' tool available so this guy can hose his machine down of all stardock applications and install again?
Reply #4 Top
RobertRushAADA I would add to Quentin94's instructions to run a Register cleaning program also if you have one after the uninstall and before the reinstall.  ;) 
Reply #5 Top
Try Stardock's ODNT zapper LINK With this you can completely remove WindowBlinds and start again. Just remember to back-up your skins first ;)
Reply #6 Top

Make sure that when you install it you go up to the current beta of the software. Also before running anything restart the machine after the install. Those might have been "duh" things to say but it makes a big difference and even testing this stuff all the time I forget to do it.

Reply #7 Top
Ah! That's it........the component zapper. Thanks Fuzzy  :) 
Reply #8 Top
When this happens to a legitimate user and you happen to be that user, it's darn frustrating.

It happened to me with version 5.51. Turned out in my case it was the Windowblinds service not starting ater the 5.51 installation. I had to force the service to start manually by editing the registry.

I have great faith in SD and think their software is great, but never again will I install a new version of Windowblinds without first making a full backup/image. Version 5.51 is the only version I've had a problem.
Reply #10 Top
what was that registry key please?


You should look on the email you've received after bought the product.
Reply #11 Top

what was that registry key please?


You should look on the email you've received after bought the product.





Quentin... you're referring to the registration key (serial #)

DollyTheCow wants to know where in the registry to edit - in regards to:


It happened to me with version 5.51. Turned out in my case it was the Windowblinds service not starting ater the 5.51 installation. I had to force the service to start manually by editing the registry.


Reply #12 Top
Quentin... you're referring to the registration key (serial #)


 ;p



sorry