IP Helper & HomeGroup

I'm unable to start the IP Helper service. This issue came up very recently when I did a system restore. When the computer booted up after restore, there was an error in event viewer stating that "the IP Helper Service terminated with the following error: The specified module could not be found." (Event ID 7023) It's the first time this computer has ever generated that error, and now it appears in EV each time the machine is booted. (I finally set it to manual startup instead of automatic just so I wouldn't get the error.) If I go into Services and try to start the IP Helper, I get an error 126 stating that windows can't find the module, although the iphelpsvc.dll is where it's supposed to be, and all relevant properties seem to be ok. Also, this same computer isn't visible in HomeGroups on the other 2 machines on my home network, although the network itself seems fine, we can all share files outside of the HomeGroup, and I can see the other computers from this one. Which would probably make someone wonder why I'm bothering trying to figure this out :) I'd just really like to find an answer and get this fixed. I've googled the IP Helper service and most of what I find is how to disable it. I think I have that covered

I understand there's some connection between HomeGroup and the IP Helper Service, but I'm not sure which is causing the problem and which is merely collateral damage. At this point, I've compared every setting I can think of to the settings on another of our computers, and they all match up, from Windows Firewall settings to HomeGroup password, network & workgroup names, network adapter settings, etc.

Basically, at this point, I'm looking for information on various scenarios that might cause IP Helper Service not to start. The dependencies all check out and are started. I'm not sure if the .dll file itself could be corrupted? Very hesitant to start digging any deeper in case I mess things up even more. At least now, the computer's humming for the most part.

Any input would be appreciated. I'm going in circles now with no new info. Thanks.

Is the file even there?

the IP Helper Service terminated with the following error: The specified module could not be found

jpierce said:

The iphlpsvc.dll is where it's supposed to be (in the system32 folder), as I said, but I'm not familiar with this service or what else I should be looking for. When windows complains that the module can't be located, is that what it's referring to or is there another file?

ok for the description and possible fixes go here. Event ID 7023

Thanks for the input. Much of what I found at the link related to info I already have, such as the error number when attempting to manually start IP Helper service (ERROR_MOD_NOT_FOUND 126 (0x7E)), Event ID# in Event Viewer (7023 - Service Control Manager reports when services terminate unexpectedly or fail to restart after it takes corrective action.)

I followed the instructions re: CMD prompt, and this was the result:

SERVICE_NAME: iphlpsvc
DISPLAY_NAME: IP Helper
TYPE : 20 WIN32_SHARE_PROCESS
STATE : 1 STOPPED
WIN32_EXIT_CODE : 126 (0x7e)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0

The logical conclusion I would draw would be the IP Helper Service module doesn't exist. From what I can tell, it does. I'm hoping someone reads this who understands how this works and might have an idea as to what could be putting up a roadblock or is keeping Windows from 'seeing' it. There's an iphlpsvc.dll in the system 32 folder and all file details are the same as on another of my computers running the same OS.

There are many search results when googling IP Helper Service providing instructions on how to disable IP Helper because it was causing problems. I've no idea how to get it working though.

Followed these instructions on the MS support site related to Error 126 and found the iphlpsvc.dll where it's supposed to be --

Error 126: The specified module could not be found when starting a service

1. Check the registry key:

HKLM\System\CurrentControlSet\Services\%ServiceName%\Parameters

2. Check the associated DLL file name value for ServiceDLL.

3. Physically check the location mentioned in the key ServiceDLL and make sure that the file is there.

4. If you do not find the file at the location mentioned in the key HKLM\System\CurrentControlSet\Services\%ServiceName%\Parameters\serviceDLL then copy the file from a working Server with the same OS and Service Pack Level.

5. Now try to start the service and the service should now start.

jpierce said:

Followed these instructions on the MS support site related to Error 126 and found the iphlpsvc.dll where it's supposed to be --

Error 126: The specified module could not be found when starting a service

1. Check the registry key:

HKLM\System\CurrentControlSet\Services\%ServiceName%\Parameters

2. Check the associated DLL file name value for ServiceDLL.

3. Physically check the location mentioned in the key ServiceDLL and make sure that the file is there.

4. If you do not find the file at the location mentioned in the key HKLM\System\CurrentControlSet\Services\%ServiceName%\Parameters\serviceDLL then copy the file from a working Server with the same OS and Service Pack Level.

5. Now try to start the service and the service should now start.

Sorry to have taken so long to reply, but I am in the middle of an ISP outage (storms) and working on a USB modem.

I dont know what else you can do besides a clean install, but am willing to help with whatever route you want to go


Ken

Not a problem, I'm very grateful to you for taking the time to help me.

I just tried re-registering the iphlpsvc.dll at the cmd prompt and got this pop-up message:

The module "iphlpsvc.dll" failed to load. Make sure the binary is stored at the specified path or debug it to check for problems with the binary or dependent .DLL files. The specified module could not be found.

This is definitely beyond my Windows 7 knowledge. I have no idea how to debug or even what the binary is.

The reason I performed the system restore is my computer had been crashing just about every morning for several days in a row, 4 to 6 minutes after booting. It was after I had installed SP1, so I did a system restore back to 6/19, well before the update. This problem with IP Helper Service reared its head the first time the computer booted after the restore, which was a headache in itself. I got a white screen and had to power down the machine and restart. After that scare with the screen going white, I was expecting the computer to be fried. Ironic that the only problem I seem to be having now is one I've never had in the past. Before the system restore, I didn't even know what IP Helper was. Now I'm getting very tired of the phrase.

Thanks for the offer to help with the clean install. The idea of starting fresh is tempting even though it means many hours of reinstallations and organizing of programs, but you can probably understand I'm leaving it as a last resort. I'm still hoping I can find an answer to this problem.

Good luck with the modem and those storms!

I just tried the sfc /scannow and it found corrupt files but couldn't fix them all. I ran it again in safe mode. It took its time like maybe it was accomplishing repairs it didn't before, but then resulted in the same message (found corrupt files, couldn't fix them all).

And after rebooting, I was able to start the IP Helper Service! I have no idea what was corrupt, what was repaired and what wasn't, but something obviously changed for the better. The computer is now showing up in the homegroup on the other computers as well.

I'm going to try to decipher the cbs log file, but it seems rather complex and about 10,000 pages long, give or take. :)

Just wanted to give you an update and thank you again for even taking the time to read about my problem, let alone offering to help. I will post again if the issue reappears.