Problem With WindowBlinds

Just got the new version of WindowBlinds. Also tried the new Desktop X. This was the first ever try with Desktop X, and I decided I did not want it so I uninstalled it. Now when I restart my computer, WindowBlinds will not load on startup. When I check the Display settings it shows the skin I was using as being selected, but I have to reselect the skin then apply it again for it to work. But then when I restart my computer, it's back to the plain Windows Classic skin, but it still shows the WindowBlinds skin as being selected. Why is WindowBlinds no longer loading?
1,845 views 7 replies
Reply #1 Top
Have you tried uninstalling and reinstalling WindowBlinds? I'm pretty sure no files are shared between WB and DesktopX, but it's possible something's been removed in the process.
Reply #3 Top
What version of Windows are you using? Is WindowBlinds set to load on startup?
Reply #4 Top
I hope this works its a bit longish:
Restart Windows then in the Display Properties window under appearance select windows classic style. Apply
Then restart Windows again then in the Display Properties window under appearance select Windows XP style. Apply
Finally restart Windows then in the Display Properties window under appearance select the skin you wish to use. Apply



Powered by SkinBrowser!
Reply #5 Top
I am using the latest version. The one that was just released a few days ago. I thought maybe the problem was that it was not set to load on startup, but I could not find where to change that option. I also tried the suggestion by risblaque and it did not work.
Reply #6 Top
I also just read "Select the Windows Classic skin (at the top of the list) or check the checkbox on the Skins tab to not load on startup. Note: this checkbox is not present on Windows XP."
I got that on the WindowBlinds help page at Stardock. I am running Windows XP.
Reply #7 Top
I wanted to Thank You both for trying to help me. I have fixed my WindowBlinds problem finally. I uninstalled, again, but this time through Add/Remove programs instead of the Component Manager. Then reinstalled using the Component Manager. I don't know what the confict was, but it appears to be working now. Thanks Again!!!