Computing.Net > Forums > Windows 95/98 > Windows Socket Error(10048)on API'bind'

Computer Problems? Computing.Net has over 1,000,000 posts about all things technology related! Over 90% answered within 24 hours! Click here to start participating now! Also, be sure to check out the New User Guide.

Windows Socket Error(10048)on API'bind'

Reply to Message Icon

Name: Pete
Date: March 30, 2002 at 13:29:10 Pacific
Comment:

I know this isn't a new problem and I know what is causing it. I need to know how to get rid of those annoying windows that keep saying windows socket error. They just won't stop. I'm a home user and I only have one computer, no server, no networking! Please help!(Using Windows 98' 2nd Edition.) Thanks! Pete



Sponsored Link
Ads by Google

Response Number 1
Name: newgrl
Date: March 31, 2002 at 08:30:46 Pacific
Reply:

Go to start>>run>>msconfig
Go to the startup tab

Look through the list.
Do you see: shellapi.exe?

If you do, you have a trojan that is causing your error. It's pretty easy to clean off, but take a look first.

If you have shellapi.exe in the list:

Go to start>>run>>regedit
Browse to:
HKEY_LOCAL_MACHINE\Softwar\Microsoft\Windows\CurrentVersion
Look down the list on the left.
You will see Run and RunServices
Open the Run folder by clicking on it once.
Look on the right.
Find shellapi.exe
Hightlight and delete it.

Now do the same for the RunServices key.
Delete shellapi.exe from it.

Close the registry editor.

Go to start>>shut down>>restart in MSDOS mode.
At the c:\windows prompt type:

cd system
del shellapi.exe

Completely shut down your computer to clear out memory.

Wait 30 seconds and boot back up.

Test. The APIBind error should be gone.

For Reference:
Avert writeup

Another messageboard with the same error you are getting

Yet another messageboard with the same APIBind error and shellapi.exe


0

Response Number 2
Name: Pete
Date: April 1, 2002 at 06:18:46 Pacific
Reply:

Thanks for your help! I'll try it, if this doesn't work, do you have any other suggestions?

Pete


0

Response Number 3
Name: Pete
Date: April 1, 2002 at 14:47:56 Pacific
Reply:

Thanks newgrl! That did the trick. Finally, those annoying windows are gone. Your the best. Take care.

Pete


0

Response Number 4
Name: vishwas
Date: May 21, 2002 at 11:50:31 Pacific
Reply:

Tooo cool man...It worked great


0

Response Number 5
Name: georeg
Date: June 15, 2002 at 19:33:59 Pacific
Reply:

How do I remove this error when nothing comes up on my NT Screen. It's just stays blank and the Socket error keeps coming up. The only way for me to start anything is to do a CTRL< ALT< DEL to get the Windows NT Task Manager. From here I have to go to FILE and run a NEW TASK RUN. Any other way to delete or look for the SHELLAPIl.EXC?


0

Related Posts

See More



Response Number 6
Name: Nidhi Jain
Date: June 17, 2002 at 12:34:34 Pacific
Reply:

I am also facing the same error, but
search yields no results for shellapi.exe!
I saw a file iphist.dat on the desktop when this problem started.
My OS is windows 2000.
Thanks!
Nidhi


0

Response Number 7
Name: Xandros
Date: June 19, 2002 at 20:09:55 Pacific
Reply:

dude, I've got the same problem as Nidhi. I'm running Win98.

Possibly unrelated, but my AIM periodicly sends IMs to the active buddy (I have an IM open, something sends to my buddy: "Neat" or cool or hey check this out, or whatever, then it sends an IP address. It seems to do this only when I send an IM (not if I'm just staring at the IM). But I'm not 100% on that.

Any clues, thanks!

-Alex


0

Response Number 8
Name: kinnari
Date: June 20, 2002 at 19:28:31 Pacific
Reply:

I am also facing the same error, but
search yields no results for shellapi.exe!
I saw a file iphist.dat on the desktop when this problem started.
My OS is windows 98.
Thanks!
kinnari


0

Sponsored Link
Ads by Google
Reply to Message Icon






Post Locked

This post is quite old and has been locked from receiving new replies. Please create a new posting instead.


Go to Windows 95/98 Forum Home


Sponsored links

Ads by Google


Results for: Windows Socket Error(10048)on API'bind'

Windows socket error: (10048) on API 'bind' www.computing.net/answers/windows-95/windows-socket-error-10048-on-api-bind/32154.html

windows socket error on api bind www.computing.net/answers/windows-95/windows-socket-error-on-api-bind/89495.html

windows socket error(11001),on API(async www.computing.net/answers/windows-95/windows-socket-error11001on-apiasync/98983.html