Windows 10 service in stopping state

Tibor Holešek 96 Reputation points
2021-02-23T14:04:20.88+00:00

Dear all,

Seems that i run into a pickle. It seems that for the love of my life cannot kill a service which is stuck in stopping status. The service in question is IP Helper service which is basicaly a svchost.exe with few parameters. To make long story short, i've tried everything, what http://support.moonpoint.com/os/windows/processes/unkillable/ has to offer to no avail. The process persist even after restart.

Any suggestions on what more can i do would be appriciated.

Kind regards, Tibor

Windows 10
Windows 10
A Microsoft operating system that runs on personal computers and tablets.
10,987 questions
0 comments No comments
{count} votes

Accepted answer
  1. Tibor Holešek 96 Reputation points
    2021-02-24T11:27:27.72+00:00

    Finalyy got it working. What i think happend is...User reported that prior to failure of the service had WiFi issues. During that, IPHelper got stuck somehow because of some unfinished I/O processes (usually the case with unkillable processes). Then i replaced the WiFi driver and reverted back to old one. This seems that it cleared everything, iphelper service then picked up the change and cleared the stopping status.

    Maybe this will help someone else.

    BR, Tibor

    0 comments No comments

5 additional answers

Sort by: Most helpful
  1. Dave Patrick 426.4K Reputation points MVP
    2021-02-23T14:09:30.063+00:00

    As a work around set it to Disabled and reboot.

    --please don't forget to Accept as answer if the reply is helpful--

    0 comments No comments

  2. Tibor Holešek 96 Reputation points
    2021-02-23T14:11:55.103+00:00

    Hi DSPatrick,

    Did that, still the same "stopping" status. Also we need this to run as we are running Direct Acces to access our internal network.

    BR, Tibor

    0 comments No comments

  3. Dave Patrick 426.4K Reputation points MVP
    2021-02-23T14:14:17.937+00:00

    Did that, still the same "stopping" status.

    Then it must not have rebooted.

    --please don't forget to Accept as answer if the reply is helpful--

    0 comments No comments

  4. Tibor Holešek 96 Reputation points
    2021-02-23T14:17:03.157+00:00

    It was rebooted, countless times. It even still persist under the same PID

    0 comments No comments