theme problem, please help!!!

recently i installed windowblinds and i download some skins, i couldnt find a skin i liked so while i looked for 1 i liked i out my skin back to the windows vista(my default) but when i do this it put something that looks like a blurry skin over the screen so it is impossible to read anything on the screen. i managed to uninstall windowblinds but with no success. so i managed to find my way around and set in themes to the classic windows theme. any ideas on what the problem is? i desperatly need to get this sorted?

thanks for any help!! :D
1,510 views 7 replies
Reply #1 Top
something that looks like a blurry skin over the screen
End of quote


was there also a box in the middle saying something like 'please wait'?

hard to sort since you uninstalled WB - what we need is your WB system info posted
Reply #2 Top
mcaulayj1 when you had WindowBlinds installed did you make any changes to settings? It sounds like even thought you applied you default theme that possibly transparency and blur may have been changed and not returned to default.

Also, when you change between WB skins, during the process you whole screen will go to a blur untill the new WB is loaded. I'm also taking it the you screen or desktop is okay other than being set to the classic windows theme.
Reply #3 Top
no i didnt change any transparency or blur settings just applied the vista theme. yeathe screen changes as usual when changing but when its complete there is this blur with lines across it diagonally blurring up the whole screen.
Reply #4 Top
Okay mcaulayj1 you need to post your system info as Bichur said. In order to do that you will have to reinstall WB. If you could post a screenshot of what your screen/desktop looks likes that will also help. Now since its Christmas weekend I don't expect any Stardock reps will show up, but the rest of us will try and help.
Reply #5 Top
Reply #6 Top
dont worry i have fixed the problem, dont know how but its fine now, thanks for help! :)
Reply #7 Top
mcaulayj1 well it's good to hear that the problem is fixed. Come back and post if you can back track things that you did that might have solved the problem.  ;)