Yup you have a problem, WindowBlinds should not react that way.  Have you email support@stardock.com and started a ticket?

No I haven't but I will.

Ok I did the reset data which found an update for Impulse but still no update for WindowBlinds.

Ok did that and it saw the new update and installed it. Here's the new info from WB7

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

WindowBlinds version : WindowBlinds 7.01 (build 234 x86 - Vista Edition)

WindowBlinds is installed correctly on this PC
WindowBlinds appears to be activated on this PC
(HP f2105 Wide Flat Panel Monitor) 1 is attached to NVIDIA GeForce 9600 GT

Wblind.dll         2009/12/10 16:58:20
Wbsrv.dll         2009/12/03 13:44:30
SevenConfig.exe         2009/12/03 10:43:22
Wbload.exe         2009/12/03 10:43:12
Wbhelp.dll         2009/10/07 14:35:07
Tray.dll              2009/10/21 08:13:19
Wbload.dll              2009/09/25 07:41:28
Screen.exe         2009/12/03 13:43:26

Still doing the same thing though...problem not fixed. Also I found this in the Impulse error log:

-- [12/17/2009 10:44:52 AM] ----------------------------------------------------

Context:     UpdateApplicationFileList: impulse, impulse_images,PublicProduction

Message:     Problem deserializing the XML or saving it.

Build #:     1309

Exception:   Root element is missing.

Stack Trace:

   at System.Xml.XmlTextReaderImpl.Throw(Exception e)

   at System.Xml.XmlTextReaderImpl.ThrowWithoutLineInfo(String res)

   at System.Xml.XmlTextReaderImpl.ParseDocumentContent()

   at System.Xml.XmlTextReaderImpl.Read()

   at System.Xml.XmlLoader.Load(XmlDocument doc, XmlReader reader, Boolean preserveWhitespace)

   at System.Xml.XmlDocument.Load(XmlReader reader)

   at System.Xml.XmlDocument.Load(TextReader txtReader)

   at a1.c(UpdateParams A_0)

I then tried it again tonight and uninstalled WB7 and then before reinstalling this time I went through and removed all the WB7 stuff in Program Files and Programdata directories in case there was a bunged up file. I then had Impulse reinstall WB7 and when it was done I found this in the Impulse error log:

-- [12/17/2009 10:45:00 AM] ----------------------------------------------------

Context:     Updating ApplicationList XML: wc

Message:     Updated network xml did not have expected revision (retrieved 88 / expected 89)

Build #:     1309

-- [12/18/2009 12:51:59 AM] ----------------------------------------------------

Context:     Program Error

Message:    

Build #:     1309

Exception:   Requested registry access is not allowed.

Stack Trace:

   at System.ThrowHelper.ThrowSecurityException(ExceptionResource resource)

   at Microsoft.Win32.RegistryKey.InternalOpenSubKey(String name, RegistryKeyPermissionCheck permissionCheck, Int32 rights)

   at Microsoft.Win32.RegistryKey.OpenSubKey(String name, RegistryKeyPermissionCheck permissionCheck)

   at Stardock.Central.Common.Utils.SettingsHelp.GetKey(RegistryKey BaseKey, String SubKey, Boolean CreateIfMissing, Boolean WriteAccessNeeded)

   at Stardock.Central.Common.Utils.SettingsHelp.Load(String SubKey, String ValueName, Object DefaultValue, RegistryKey BaseKey)

   at Stardock.Central.Common.Utils.SettingsHelp.LoadCU(String SubKey, String ValueName, Boolean DefaultValue)

   at Stardock.Central.Common.Settings.get_UsePrivate()

   at Stardock.Central.Client.Program.ReadSettingsFromRegistry()

   at Stardock.Central.Client.Program.MainReal(String[] args)

   at Stardock.Central.Client.Program.MainSmall(String[] args)

   at Stardock.Central.Client.Program.Main(String[] args)

Don't know if these errors have anything to do with my problem but they don't look good.

Are you running WindowBlinds and Impulse on an account with admin privileges?  Admin access is required to run these applications.

You'll see this when Impulse updates XML. It's normal.

This would be specific to Impulse. If you continue to see this, try uninstalling Impulse, rebooting, and reinstalling.

Well, glad to hear that worked, but I don't thin it would be a boot order issue.  Most likely some startup app was preventing access and now that it is removed the block no longer is there.