![]() ![]() No problems were encountered :-)Īlthough this is a decent temporary solution, I'd appreciate a proper fix to this issue. I therefore unchecked the Core System Shield setting to "Verify the integrity of the LSP chain and other system structures" and re ran the scan, followed by a reboot. The more I thought about the ACLUs failure to totally support my efforts to defeat. The LSP changes are clearly the problem here, as when I run a "netsh winsock reset" the issue is resolved. Roberts has a real life Learn why the ACLU fears defeating the censors. Plus a number of "SLevel updated to" messages "Replaced the invalid LSP chain due to malware corruption" "Removed invalid LSP chain entry: C:windowssystem32cwalsp.dll" When Netnanny is running and I perform a scan I have noticed the following (well over 100) scan log entries: I've made some further discoveries that you may find useful. Hi all, thought I'd share my latest email to WR support, any ideas would be appreciated.
0 Comments
Leave a Reply. |