Windowblinds needs a reboot

from Stardock Forums
I can't seem to get past this, trying to install 5.50 from today. Using Vista Business, only thing I'm running is AVG and the built-in Windows Defender. I have disabled the Windows Defender service in an attempt to make sure that isn't causing a problem and unfortunately no luck. Any advice?

System Info:
Intel Pentium D 2.66GHz
1 GB Ram
ATI x600 with latest catalyst drivers (yeah, video needs an upgrade)

Not sure if you need anything else ... Dan
windowblinds
10,919 views 12 replies
Reply #1 from WinCustomize Forums Top
Don't have Vista so I'm guessing here, try disabling AVG or at least any script blocking.
Reply #2 from Stardock Forums Top
Hopped on irc after posting this, worked with GreenReaper and got things resolved. Upon uninstall I was having stuff still hanging around in the registry and files in C:\Program Files\Stardock\Object Desktop\Windowblinds. It wasn't deleting reg entries or removing folders (I said to delete all skins and such). Once I cleaned up all that stuff, rebooted, reinstalled and rebooted again everything is working properly ...

Thanks,
Dan
ObjectDock - Access shortcuts and frequently used applications from an animated dock.
Reply #3 from Stardock Forums Top
I am having the same problem.

I created a new Vista Business system, and successfully installed WB 5.50.023. However, because the skin I was using was quite old, and was creating problems with the graphics, I decided to temporarily disable WB, while getting on with the job of building my system. The only way I could find to disable WB was to uninstall it, which is what I did.

Now, I am trying to re-install it, and it is telling me, repeatedly, I need to reboot, and warning me about spyware tools. I have used MSCONFIG to disable all startups, and tried the uninstall/re-install procedure, several times, but WB is still telling me I need to reboot!

Right now SDC is telling me I have WB 5.50.023 installed, but if I try to start it, I get the 'you need to reboot' warning.

Please, can anyone help?
Reply #5 from WinCustomize Forums Top
Make sure the Stardock WindowBlinds service is started.
Reply #6 from Stardock Forums Top
Thanks for the suggestion, PurrBall...

I'm afraid fate has intervened.

I used Vista System Restore to attempt a rollback of the registry past the point at which the trouble started. Bad move!!!

My system could no longer log in to our domain, despite all endeavours. Result, I am half-way through a re-install/configuration of everything. The good news is that, of course, I have successfully installed WB 5.50.023.

I suppose it's an ill-wind...   

Regards...

Bernard
Reply #7 from WinCustomize Forums Top
In future, the way to "temporarily disable" WB is to switch to Windows Classic in WB Config. If you uninstalled WB without doing that first, there is a good chance that's what gave you the trouble after you re-installed it - WB needs to be unloaded ("temporarily disabled") to be properly uninstalled.  
Reply #8 from Stardock Forums Top
In future, the way to "temporarily disable" WB is to switch to Windows Classic in WB Config. If you uninstalled WB without doing that first, there is a good chance that's what gave you the trouble after you re-installed it - WB needs to be unloaded ("temporarily disabled") to be properly uninstalled.  


Thanks for the tip. I shall bear it in mind for the future, although I hope I'll not need it again.  

You are right. I did not do that, and WB left debris behind in the registry.

Regards...

Bernard
Reply #9 from WinCustomize Forums Top
Why Wb doesnt have an option to run \ not run @ start up I have NO idea.   
Reply #10 from Stardock Forums Top
Choosing a windows default skin causes WB to not run at start (no reason to run if no WB skin used)
Reply #11 from WinCustomize Forums Top
even though this post is old and i don't know if you have fixed the problem but, try disabling the UAC and try installing WB 5.5 again and see if that helps out any
Reply #12 from WinCustomize Forums Top

In future, the way to "temporarily disable" WB is to switch to Windows Classic in WB Config. If you uninstalled WB without doing that first, there is a good chance that's what gave you the trouble after you re-installed it - WB needs to be unloaded ("temporarily disabled") to be properly uninstalled.


you may also want to delete the registry settings after the reboot to make sure there is no traces left when going to re-install wb.make sure that the UAC is disabled before deleting the registry setting other wise the UAC will put those settings back into the registry