I performed the search, quarantine and deletion of certain spyware files on both my computers, but afterwards I experienced some slow-down on my Cable connection, so I restarted. But when I restarted, my comp could no longer go on the net. We're on a network, so I told my bro to turn off his comp too just in case there was some kind of weird deal, but when we did that, my other computer couldn't go online either. Even my 56K was useless!!:'(

I called my Cox support technician, and he said my modem was fine and dandy, and that something was up with my computers, and that " C:\WINDOWS\INF " wasn't working or responding,and he said that was a bad sign:(

He told me to go and do a system restore with my system restoration disc, but even that didn't fix my problem(i did the restore from windows, but not from the CD itself.)

Is there anything I can do short of sending my computer to a repair shop to literaly replace my harddrive and reinstall Windows XP? Or maybe gain some of those lost files i probably lost in the Ad-Aware deletion from somewhere that I can get online?(I'll use someone else's comp for that.)

My dad just got Broadband, so he'll be real mad about this
:( Any help would be REAL REAL appreciated!

thanx a LOT in advance!!:cry:

And feel free to e-mail me about any special things i might need to have.

Dani AI

Generated

This is a classic case of the Winsock/LSP chain getting broken after spyware removal. was right to point at that, and @musemaker’s report shows one working—but fairly aggressive—repair path. The post replies leave a few important gaps: how to take safer first steps, how to restore core Windows network files without blind registry edits, and what to try if simple fixes fail. The suggestions below fill those gaps and prioritize safety.

Start with the non-destructive checks (run as Administrator). Boot Safe Mode with Networking and see if basic connectivity returns. From a command prompt gather diagnostics and try lightweight resets:

ipconfig /all
ipconfig /release
ipconfig /renew
ipconfig /flushdns
netsh winsock reset
netsh int ip reset resetlog.txt

Reboot after the netsh commands. If netsh winsock reset isn’t recognized (older installs), skip it and follow the LSPFix path that suggested or use a known repair tool copied from another PC.

Before editing the registry or deleting installed protocols: export a registry backup and create a System Restore point so you can roll back if something goes wrong. If system DLLs or INF files were removed, run sfc /scannow (Windows XP will ask for the installation CD) to restore protected system files. Also uninstall and reinstall the network adapter in Device Manager, then repair the connection from Network Connections (right‑click → Repair) or reinstall the TCP/IP protocol through the connection properties.

If none of the above works, collect tools (LSPFix, current network drivers, a clean copy of the OS install CD) on a USB from a working PC and try repairs offline. As a last resort, a repair/repair‑install of Windows or a trained technician is safer than more registry surgery. Editing winsock/LSP entries without backups can make an otherwise recoverable machine require a full reinstall.

Recommended Answers

All 2 Replies

also, it said my ISP couldn't be renewed, most likely due to the Spyware scan and deletion.

*would really like any help at all and is really desperate*

XD

also, it said my ISP couldn't be renewed, most likely due to the Spyware scan and deletion.

One of your likely bits of malware replaced part of your Winsock chain with its own stuff. When you removed it, you "broke the chain". Here is the link to LSPFix, which should help.

musemaker then responded with: It worked! And here's the process order:

* Run LSPfix.
* Delete all Dial-up adapters and network protcols.
* Delete all Winsock and Winsock2 registry keys.
* Under Add/Remove programs uncheck all of the listings under Communications.
* Reboot and then add back ALL the Communications items (although netmeeting and chat weren't necessary). It didn't work for me the first time as I have no need for a dial-up adapter, but it is the only way to get Windows to add back winsock2.
* Reinstall network protocol settings.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.