Error Starting IPHLPAPI.DLL

Config:
Windows Me
New Install
Athlon XP 1G
Broadband Internet
AOL 9.0

Problem: Intermittant startup error cannot start IPHLPAPI.DLL. I tried a
couple different dlls without correction. Then I tried the version included
with AOL 9 and now its just intermittant. This was a new install and I
didn't get the error until I did a MS Update.
Any suggestions are appreciated.

Mike
Tue Jun 01 10:36:07 CDT 2004

The clue here is probably AOL 9.0

When did this problem start? What changes did you make to your system just
prior to this problem starting?

For many users this problem is caused by installing AOL9 since AOL 9 uses a
different version of iphlpapi.dll than is included with Win Me and fails to
install it correctly. You can check this for yourself where you will find
that AOL have put a version of iphlpapi.dll in the Program Files\Common
Files\AOL\ACS\winme folder which differs from that in the windows\system
folder.

Since the copy of iphlpapi.dll in the windows\system folder is protected from
alteration or deletion by Win Me's System File Protection (SFP) it cannot
simply be replaced by the copy in the AOL folder. Whilst there are ways of
defeating SFP so that AOL's file can be added to the system folder I
personally feel this is a problem that needs to be remedied by AOL.

If your problem is a result of installing AOL 9 you may want to consider using
System Restore to solve this problem by rolling back your system to before the
problem started and dumping AOL 9 until AOL can get things working correctly
(just don't hold your breath) provided that that was not more than a few days
ago.
--
Mike Maltby MS-MVP
mcmaltby@hotmail.com


Netboy <netboy@darkstar.net> wrote:

> Config:
> Windows Me
> New Install
> Athlon XP 1G
> Broadband Internet
> AOL 9.0
>
> Problem: Intermittant startup error cannot start IPHLPAPI.DLL. I tried a
> couple different dlls without correction. Then I tried the version
> included with AOL 9 and now its just intermittant. This was a new install
> and I didn't get the error until I did a MS Update.
> Any suggestions are appreciated.

Netboy
Tue Jun 01 11:52:29 CDT 2004

I had AOL 9 installed for a couple days and running without the error
showing. Then after updating the following from Windows update the error
started showing:
IED Hard Drive Cache Package
Root Cert Update
and Auto Updating
Currently since I manually placed the AOL iphlpapi.dll file in the win/sys
dir the system has been running good except for an occaisonal subject error.
I will check the AOL 9 groups for insght as well.
Thanks.





"Mike M" <No_Spam@Corned_Beef.Only> wrote in message
news:OQe1$4%23REHA.2200@TK2MSFTNGP12.phx.gbl...
> The clue here is probably AOL 9.0
>
> When did this problem start? What changes did you make to your system
just
> prior to this problem starting?
>
> For many users this problem is caused by installing AOL9 since AOL 9 uses
a
> different version of iphlpapi.dll than is included with Win Me and fails
to
> install it correctly. You can check this for yourself where you will find
> that AOL have put a version of iphlpapi.dll in the Program Files\Common
> Files\AOL\ACS\winme folder which differs from that in the windows\system
> folder.
>
> Since the copy of iphlpapi.dll in the windows\system folder is protected
from
> alteration or deletion by Win Me's System File Protection (SFP) it cannot
> simply be replaced by the copy in the AOL folder. Whilst there are ways
of
> defeating SFP so that AOL's file can be added to the system folder I
> personally feel this is a problem that needs to be remedied by AOL.
>
> If your problem is a result of installing AOL 9 you may want to consider
using
> System Restore to solve this problem by rolling back your system to before
the
> problem started and dumping AOL 9 until AOL can get things working
correctly
> (just don't hold your breath) provided that that was not more than a few
days
> ago.
> --
> Mike Maltby MS-MVP
> mcmaltby@hotmail.com
>
>
> Netboy <netboy@darkstar.net> wrote:
>
> > Config:
> > Windows Me
> > New Install
> > Athlon XP 1G
> > Broadband Internet
> > AOL 9.0
> >
> > Problem: Intermittant startup error cannot start IPHLPAPI.DLL. I tried a
> > couple different dlls without correction. Then I tried the version
> > included with AOL 9 and now its just intermittant. This was a new
install
> > and I didn't get the error until I did a MS Update.
> > Any suggestions are appreciated.
>
>

Mike
Tue Jun 01 12:22:29 CDT 2004

How did you manually place AOL's version of iphlpapi.dll in the windows\system
folder? Doing so would have meant over-riding Win Me's system file protection
after which you would be on your own support wise. Are you surprised
therefore that you sometimes see the error you report if you have chosen to
override SFP - it's there for a purpose although clearly over four years later
AOL have yet to learn how to deal with it which says a lot for the competency
level of their programmers
--
Mike Maltby MS-MVP
mcmaltby@hotmail.com


Netboy <Netboy@darkstar.net> wrote:

> I had AOL 9 installed for a couple days and running without the error
> showing. Then after updating the following from Windows update the error
> started showing:
> IED Hard Drive Cache Package
> Root Cert Update
> and Auto Updating
> Currently since I manually placed the AOL iphlpapi.dll file in the win/sys
> dir the system has been running good except for an occaisonal subject
> error. I will check the AOL 9 groups for insght as well.

Netboy
Tue Jun 01 16:45:37 CDT 2004

I didn't over right the original it was backed up. I did it in safe mode,
one of a couple ways to replace system files. There are a number of helps
described on the net for this 'fix'. Which didn't work I must say. Thus I
decided to try the group to see if I missed a valid fix. I don't need to be
berated here for my actions, just looking for some help. If you don't have
any more help then no need to reply. It appears the problem went away or its
just taking longer to re-appear.
Thanks.


"Mike M" <No_Spam@Corned_Beef.Only> wrote in message
news:eokik0$REHA.2876@TK2MSFTNGP09.phx.gbl...
> How did you manually place AOL's version of iphlpapi.dll in the
windows\system
> folder? Doing so would have meant over-riding Win Me's system file
protection
> after which you would be on your own support wise. Are you surprised
> therefore that you sometimes see the error you report if you have chosen
to
> override SFP - it's there for a purpose although clearly over four years
later
> AOL have yet to learn how to deal with it which says a lot for the
competency
> level of their programmers
> --
> Mike Maltby MS-MVP
> mcmaltby@hotmail.com
>
>
> Netboy <Netboy@darkstar.net> wrote:
>
> > I had AOL 9 installed for a couple days and running without the error
> > showing. Then after updating the following from Windows update the error
> > started showing:
> > IED Hard Drive Cache Package
> > Root Cert Update
> > and Auto Updating
> > Currently since I manually placed the AOL iphlpapi.dll file in the
win/sys
> > dir the system has been running good except for an occaisonal subject
> > error. I will check the AOL 9 groups for insght as well.
>
>

Mike
Tue Jun 01 17:11:25 CDT 2004

No one was berating you, all I was doing was pointing out as that if you
voluntarily chose to over ride the protection offered by Win Me's System File
Protection you are on your own when it comes to problems resulting from that
action. Let's put it another way, AOL 9,0 is incompatible with Win Me. Your
choice entirely as to which version of iphlpapi.dll you choose to use but for
as long as you are using AOL 9.0 and Win Me you are going to experience
problems with iphlpapi.dll regardless of the version you choose to use. That
is until AOL get their act together which isn't likely to occur in either of
our life times.
--
Mike Maltby MS-MVP
mcmaltby@hotmail.com


Netboy <Netboy@darkstar.net> wrote:

> I didn't over right the original it was backed up. I did it in safe mode,
> one of a couple ways to replace system files. There are a number of helps
> described on the net for this 'fix'. Which didn't work I must say. Thus I
> decided to try the group to see if I missed a valid fix. I don't need to
> be berated here for my actions, just looking for some help. If you don't
> have any more help then no need to reply. It appears the problem went
> away or its just taking longer to re-appear.

Netboy
Tue Jun 01 17:59:55 CDT 2004

Well it seems AOL offers no technical support on the matter (no surprise).
So we are on our own. Personally, I don't use AOL I'm just setting up a PC
for someone who does. Since I copied the file from AOL dir to the sys dir I
have only gotten the error a couple times at first. For several reboots and
turnons now I haven't seen the error repeat. So all seems normal now. I hope
it stays that way. When I did get the error I just shutdown the computer
hard and restarted because you can't clear the error. Then the computer
restarted ok after scandisk. So hopefully I'm in the clear. I will recommend
an upgrade to XP to my friend but does this issue occur in XP with AOL 9? I
didn't see any ref to that.
Thanks Mike, for the thread.
Netboy




"Mike M" <No_Spam@Corned_Beef.Only> wrote in message
news:OkRq0WCSEHA.628@TK2MSFTNGP11.phx.gbl...
> No one was berating you, all I was doing was pointing out as that if you
> voluntarily chose to over ride the protection offered by Win Me's System
File
> Protection you are on your own when it comes to problems resulting from
that
> action. Let's put it another way, AOL 9,0 is incompatible with Win Me.
Your
> choice entirely as to which version of iphlpapi.dll you choose to use but
for
> as long as you are using AOL 9.0 and Win Me you are going to experience
> problems with iphlpapi.dll regardless of the version you choose to use.
That
> is until AOL get their act together which isn't likely to occur in either
of
> our life times.
> --
> Mike Maltby MS-MVP
> mcmaltby@hotmail.com
>
>
> Netboy <Netboy@darkstar.net> wrote:
>
> > I didn't over right the original it was backed up. I did it in safe
mode,
> > one of a couple ways to replace system files. There are a number of
helps
> > described on the net for this 'fix'. Which didn't work I must say. Thus
I
> > decided to try the group to see if I missed a valid fix. I don't need to
> > be berated here for my actions, just looking for some help. If you don't
> > have any more help then no need to reply. It appears the problem went
> > away or its just taking longer to re-appear.
>
>

Mike
Tue Jun 01 18:26:21 CDT 2004

Netboy,

I'm not aware of this being a problem with XP, in fact I'm pretty sure that it
isn't. Could you do me a favour please and post back the version details and
size of the AOL copy of iphlpapi.dll in Win Me (not the Win Me version which
is 4.90.3000.0 [internally actually 4.90.3000.2])? I seem to recall its the
version from XP (5.1.2600.2, same version in XP SP1 although different in
size) but to be honest simply can't remember and can't find my notes at the
moment.

Please Note I wasn't trying to criticise you for what you did. Again being
frank I know I'd have done exactly the same myself. :-) Noel Paton is also
running AOL 9 but am not sure whether he has AOL 9 on Win Me or just on his XP
partitions and is sticking with AOL 8 on Win Me. With luck he might read this
thread in the morning (like me he's in the UK and its gone midnight here) and
perhaps be able to make some other constructive suggestion as to how to
proceed, however, it looks as if you've managed to tame the problem for now.
As long as you can get AOL 9 to connect OK then you should be OK.

Oh, BTW there is a later version of iphlpapi.dll (v4.90.3001) that can be
downloaded for use with Win Me (see KB 279866 - "Iphlpapi.dll Error Message
with a 16-Bit Windows Sockets-Based Program"
(http://support.microsoft.com/?kbid=279866). ) but this doesn't seem to help
with AOL 9.0. :-(

Regards,
--
MIke M


Netboy <Netboy@darkstar.net> wrote:

> Well it seems AOL offers no technical support on the matter (no surprise).
> So we are on our own. Personally, I don't use AOL I'm just setting up a PC
> for someone who does. Since I copied the file from AOL dir to the sys dir
> I have only gotten the error a couple times at first. For several reboots
> and turnons now I haven't seen the error repeat. So all seems normal now.
> I hope it stays that way. When I did get the error I just shutdown the
> computer hard and restarted because you can't clear the error. Then the
> computer restarted ok after scandisk. So hopefully I'm in the clear. I
> will recommend an upgrade to XP to my friend but does this issue occur in
> XP with AOL 9? I didn't see any ref to that.
> Thanks Mike, for the thread.
> Netboy
>
>
>
>
> "Mike M" <No_Spam@Corned_Beef.Only> wrote in message
> news:OkRq0WCSEHA.628@TK2MSFTNGP11.phx.gbl...
>> No one was berating you, all I was doing was pointing out as that if you
>> voluntarily chose to over ride the protection offered by Win Me's System
>> File Protection you are on your own when it comes to problems resulting
>> from that action. Let's put it another way, AOL 9,0 is incompatible
>> with Win Me. Your choice entirely as to which version of iphlpapi.dll
>> you choose to use but for as long as you are using AOL 9.0 and Win Me
>> you are going to experience problems with iphlpapi.dll regardless of the
>> version you choose to use. That is until AOL get their act together
>> which isn't likely to occur in either of our life times.
>> --
>> Mike Maltby MS-MVP
>> mcmaltby@hotmail.com
>>
>>
>> Netboy <Netboy@darkstar.net> wrote:
>>
>>> I didn't over right the original it was backed up. I did it in safe
>>> mode, one of a couple ways to replace system files. There are a number
>>> of helps described on the net for this 'fix'. Which didn't work I must
>>> say. Thus I decided to try the group to see if I missed a valid fix. I
>>> don't need to be berated here for my actions, just looking for some
>>> help. If you don't have any more help then no need to reply. It appears
>>> the problem went away or its just taking longer to re-appear.

Noel
Wed Jun 02 00:52:43 CDT 2004

No IPHLPAPI problem here in AOL9 (UK version) on XP, folks - AOL9 (and all
its versions and addons) are disgustingly stable<g>

--
Noel Paton (MS-MVP 2002-2004, Win9x)

Nil Carborundum Illegitemi
http://www.btinternet.com/~winnoel/millsrpch.htm

Please read http://dts-l.org/goodpost.htm on how to post messages to NG's
or
http://www.microsoft.com/presspass/features/2001/Mar01/Mar27pmvp.asp
"Mike M" <No_Spam@Corned_Beef.Only> wrote in message
news:OX4BaADSEHA.1448@TK2MSFTNGP11.phx.gbl...
> Netboy,
>
> I'm not aware of this being a problem with XP, in fact I'm pretty sure
that it
> isn't. Could you do me a favour please and post back the version details
and
> size of the AOL copy of iphlpapi.dll in Win Me (not the Win Me version
which
> is 4.90.3000.0 [internally actually 4.90.3000.2])? I seem to recall its
the
> version from XP (5.1.2600.2, same version in XP SP1 although different in
> size) but to be honest simply can't remember and can't find my notes at
the
> moment.
>
> Please Note I wasn't trying to criticise you for what you did. Again
being
> frank I know I'd have done exactly the same myself. :-) Noel Paton is
also
> running AOL 9 but am not sure whether he has AOL 9 on Win Me or just on
his XP
> partitions and is sticking with AOL 8 on Win Me. With luck he might read
this
> thread in the morning (like me he's in the UK and its gone midnight here)
and
> perhaps be able to make some other constructive suggestion as to how to
> proceed, however, it looks as if you've managed to tame the problem for
now.
> As long as you can get AOL 9 to connect OK then you should be OK.
>
> Oh, BTW there is a later version of iphlpapi.dll (v4.90.3001) that can be
> downloaded for use with Win Me (see KB 279866 - "Iphlpapi.dll Error
Message
> with a 16-Bit Windows Sockets-Based Program"
> (http://support.microsoft.com/?kbid=279866). ) but this doesn't seem to
help
> with AOL 9.0. :-(
>
> Regards,
> --
> MIke M
>
>
> Netboy <Netboy@darkstar.net> wrote:
>
> > Well it seems AOL offers no technical support on the matter (no
surprise).
> > So we are on our own. Personally, I don't use AOL I'm just setting up a
PC
> > for someone who does. Since I copied the file from AOL dir to the sys
dir
> > I have only gotten the error a couple times at first. For several
reboots
> > and turnons now I haven't seen the error repeat. So all seems normal
now.
> > I hope it stays that way. When I did get the error I just shutdown the
> > computer hard and restarted because you can't clear the error. Then the
> > computer restarted ok after scandisk. So hopefully I'm in the clear. I
> > will recommend an upgrade to XP to my friend but does this issue occur
in
> > XP with AOL 9? I didn't see any ref to that.
> > Thanks Mike, for the thread.
> > Netboy
> >
> >
> >
> >
> > "Mike M" <No_Spam@Corned_Beef.Only> wrote in message
> > news:OkRq0WCSEHA.628@TK2MSFTNGP11.phx.gbl...
> >> No one was berating you, all I was doing was pointing out as that if
you
> >> voluntarily chose to over ride the protection offered by Win Me's
System
> >> File Protection you are on your own when it comes to problems resulting
> >> from that action. Let's put it another way, AOL 9,0 is incompatible
> >> with Win Me. Your choice entirely as to which version of iphlpapi.dll
> >> you choose to use but for as long as you are using AOL 9.0 and Win Me
> >> you are going to experience problems with iphlpapi.dll regardless of
the
> >> version you choose to use. That is until AOL get their act together
> >> which isn't likely to occur in either of our life times.
> >> --
> >> Mike Maltby MS-MVP
> >> mcmaltby@hotmail.com
> >>
> >>
> >> Netboy <Netboy@darkstar.net> wrote:
> >>
> >>> I didn't over right the original it was backed up. I did it in safe
> >>> mode, one of a couple ways to replace system files. There are a number
> >>> of helps described on the net for this 'fix'. Which didn't work I must
> >>> say. Thus I decided to try the group to see if I missed a valid fix. I
> >>> don't need to be berated here for my actions, just looking for some
> >>> help. If you don't have any more help then no need to reply. It
appears
> >>> the problem went away or its just taking longer to re-appear.
>
>

Netboy
Thu Jun 03 05:41:51 CDT 2004

The size of the file is 47k from what I recall. I sent the PC off to its
owner yesterday. I'll let you know if there are any issues next week. I
suspect the system blocked installation of that file but I was able to find
it under an AOL dir and relocated it to the win/sys dir. After backing up
the orig. Performed the transfer in safe mode. after that it ran for a while
without faulting. I did try the MS fix one time before but it didn't
correct the fault.

Netboy

"Mike M" <No_Spam@Corned_Beef.Only> wrote in message
news:OX4BaADSEHA.1448@TK2MSFTNGP11.phx.gbl...
> Netboy,
>
> I'm not aware of this being a problem with XP, in fact I'm pretty sure
that it
> isn't. Could you do me a favour please and post back the version details
and
> size of the AOL copy of iphlpapi.dll in Win Me (not the Win Me version
which
> is 4.90.3000.0 [internally actually 4.90.3000.2])? I seem to recall its
the
> version from XP (5.1.2600.2, same version in XP SP1 although different in
> size) but to be honest simply can't remember and can't find my notes at
the
> moment.
>
> Please Note I wasn't trying to criticise you for what you did. Again
being
> frank I know I'd have done exactly the same myself. :-) Noel Paton is
also
> running AOL 9 but am not sure whether he has AOL 9 on Win Me or just on
his XP
> partitions and is sticking with AOL 8 on Win Me. With luck he might read
this
> thread in the morning (like me he's in the UK and its gone midnight here)
and
> perhaps be able to make some other constructive suggestion as to how to
> proceed, however, it looks as if you've managed to tame the problem for
now.
> As long as you can get AOL 9 to connect OK then you should be OK.
>
> Oh, BTW there is a later version of iphlpapi.dll (v4.90.3001) that can be
> downloaded for use with Win Me (see KB 279866 - "Iphlpapi.dll Error
Message
> with a 16-Bit Windows Sockets-Based Program"
> (http://support.microsoft.com/?kbid=279866). ) but this doesn't seem to
help
> with AOL 9.0. :-(
>
> Regards,
> --
> MIke M
>
>
> Netboy <Netboy@darkstar.net> wrote:
>
> > Well it seems AOL offers no technical support on the matter (no
surprise).
> > So we are on our own. Personally, I don't use AOL I'm just setting up a
PC
> > for someone who does. Since I copied the file from AOL dir to the sys
dir
> > I have only gotten the error a couple times at first. For several
reboots
> > and turnons now I haven't seen the error repeat. So all seems normal
now.
> > I hope it stays that way. When I did get the error I just shutdown the
> > computer hard and restarted because you can't clear the error. Then the
> > computer restarted ok after scandisk. So hopefully I'm in the clear. I
> > will recommend an upgrade to XP to my friend but does this issue occur
in
> > XP with AOL 9? I didn't see any ref to that.
> > Thanks Mike, for the thread.
> > Netboy
> >
> >
> >
> >
> > "Mike M" <No_Spam@Corned_Beef.Only> wrote in message
> > news:OkRq0WCSEHA.628@TK2MSFTNGP11.phx.gbl...
> >> No one was berating you, all I was doing was pointing out as that if
you
> >> voluntarily chose to over ride the protection offered by Win Me's
System
> >> File Protection you are on your own when it comes to problems resulting
> >> from that action. Let's put it another way, AOL 9,0 is incompatible
> >> with Win Me. Your choice entirely as to which version of iphlpapi.dll
> >> you choose to use but for as long as you are using AOL 9.0 and Win Me
> >> you are going to experience problems with iphlpapi.dll regardless of
the
> >> version you choose to use. That is until AOL get their act together
> >> which isn't likely to occur in either of our life times.
> >> --
> >> Mike Maltby MS-MVP
> >> mcmaltby@hotmail.com
> >>
> >>
> >> Netboy <Netboy@darkstar.net> wrote:
> >>
> >>> I didn't over right the original it was backed up. I did it in safe
> >>> mode, one of a couple ways to replace system files. There are a number
> >>> of helps described on the net for this 'fix'. Which didn't work I must
> >>> say. Thus I decided to try the group to see if I missed a valid fix. I
> >>> don't need to be berated here for my actions, just looking for some
> >>> help. If you don't have any more help then no need to reply. It
appears
> >>> the problem went away or its just taking longer to re-appear.
>
>