Keep getting the reboot prompt

Keep getting the reboot prompt

Have just installed windowblinds and it prompted me to reboot. So I rebooted and tried to start Windowblinds and it prompted me to reboot. So I rebooted and tried to start Windowblinds and it prompted me to reboot. So I rebooted and .... you get the picture! Windows is working fine but as soon as I start Windowblinds it pops up the prompt. As if it thinks windowblinds has only just been installed. Any clues?

I'm not a registered user I want to trial the latest version.
2,956 views 9 replies
Reply #1 Top

This usually means an antispyware app (or something similar) has helpfully deleted key WB registry entries, or simply prevented them from being written in the first place.

You need to disable those 'helpful' apps and reinstall WB (so it can make the keys again).

Reply #3 Top
Nope. Doesn't seem to be anyway. Only using Avast, Scotty and SpywareBlaster. These won't stop the registry being written to. Any other ideas?
Reply #4 Top

I still have this problem and have notice a few similar posts around recently. Any other suggestions?


I have uninstalled and re-installed a few times. I have checked the registry as I go and the WindowBlinds sections seem to disappear and re-appear at the right times.

Reply #5 Top

Update - Have fallen back to WB4 and all okay. Would like to purchase WB5 but can't unless I find a solution to this.



Am I posting in the right place? It's all a bit quiet out there.

Reply #6 Top
Hi Bascule,

I beat my head against a wall with the same issue for weeks and finally tried uninstalling, rather than simply disabling, my anti-spyware app (Tenebril's SpyCatcher, which I had as part of the GhostSurf 2005 Platinum suite - meaning that I had to uninstall the entire package) and THAT did the trick. Note that as soon as I tried to reinstall GhostSurf after getting WB5 installed properly, the problem you've outlined returned. Fortunately, I've licenses for a number of different anti-spyware apps so I shuffled my installations between machines and got on with it... I've installled WB5 with both SpywareBlaster and Winpatrol installed without problem, so I'd look to Avast as the culprit. If you're using the free version of Avast, I can report that AVG 7.1 and WB5 coexist happily (assuming Avast turns out to be responsible and that there are no rules that you can change to allow the two to run together).

Good luck,

Mike
Reply #7 Top
Mike,

Thanks for the help. I'll try taking Avast off and see if that does it. I don't think Avast blocks anything without telling you but it's definitely worth trying.

Thanks again,
Bascule
Reply #8 Top

Glad to help, and hope this is in fact helpful in solving the problem. It goes without saying that just because WinPatrol and SpywareBlaster "play nice" with WB5 for me, it doesn't mean that they will for you... If removing Avast doesn't work, try uninstalling those two as well. I'd go Avast then SpywareBlaster, then WinPatrol, as WinPatrol is the least likely to be blocking writes to your registry. On that note, SpywareBlaster is actually the most likely of the three to be blocking the WB5 the install.


Incidentally, do you have a firewall installed? I have ZoneAlarm Pro and it comes with an anti-spyware app that seems fine with WB5 but other firewalls that feature the similar functionality might not be so "cooperative"!


Best,


Mike

Reply #9 Top

Glad to help, and hope this is in fact helpful in solving the problem. It goes without saying that just because WinPatrol and SpywareBlaster "play nice" with WB5 for me, it doesn't mean that they will for you... If removing Avast doesn't work, try uninstalling those two as well. I'd go Avast then SpywareBlaster, then WinPatrol, as WinPatrol is the least likely to be blocking writes to your registry. On that note, SpywareBlaster is actually the most likely of the three to be blocking the WB5 the install.


Incidentally, do you have a firewall installed? I have ZoneAlarm Pro and it comes with an anti-spyware app that seems fine with WB5 but other firewalls that feature the similar functionality might not be so "cooperative"!


Best,


Mike