Do you mean that the update will fix the damage done by "fixing" the false positive (which is what I hope), or that it will fix/prevent future detections of the false positive?
Printable View
Fernando suggests the following fix herethat seems to work for me so far:
Thanks to Mickey Segal for pointing this out to me.Quote:
1 - create a text file (with notepad) with this text:
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\Notify\TabBtnWL]
@=""
"Disconnect"="OnDisconnectEvent"
"DllName"="TabBtnWL.dll"
"Logoff"="OnLogoffEvent"
"Logon"="OnLogonEvent"
"Reconnect"="OnReconnectEvent"
"Shutdown"="OnShutdownEvent"
"StartShell"="OnStartShellEvent"
"Startup"="OnStartupEvent"
2 - save it with any name you want and extension “reg”, like example.reg
3 - double click the file, and respond yes to the question “are you sure to add…”
4 - reboot and you should get everything functional
If anyone has insight on what the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\WinLogon\Notify\Sebring Registry key does, please reply! I'm wondering what else Spybot may have damaged in trying to fix this false positive.
Also, even though Spybot has caused a problem here, I still want to say that I appreciate their anti-spyware service, which all-in-all has been very helpful and generous.