Skip to content

ServiceController.WaitForStatus could use NotifyServiceStatusChange WinAPI to avoid polling #45049

Open
Open
ServiceController.WaitForStatus could use NotifyServiceStatusChange WinAPI to avoid polling#45049
Labels
area-System.ServiceProcesshelp wanted[up-for-grabs] Good issue for external contributors
Milestone
Future

Description

@Fs00
Fs00
opened on Nov 21, 2020

Currently, ServiceController WaitForStatus method polls every 250ms to check if the service has reached the desired status.
This is not optimal and also not very performant, particularly if the service takes less than 250ms to reach that status.
Apparently lost in the mists of time, there was a plan to use the WinAPI function NotifyServiceStatusChange to avoid polling and get instantly notified when the service reaches a specific status.

I'm opening this issue to prevent this potential improvement from getting lost again.

Props to @KalleOlaviNiemitalo for finding this.

Activity

  1. Dotnet-GitSync-Bot
    added
    area-System.ServiceProcess
    untriagedNew issue has not been triaged by the area owner
    on Nov 21, 2020
  2. Anipik
    added this to the Future milestone on Nov 24, 2020
  3. ghost added
    in-prThere is an active PR which will close this issue when it is merged
    on Jan 13, 2021
  4. ghost removed
    in-prThere is an active PR which will close this issue when it is merged
    on Mar 31, 2021
  5. jeffschwMSFT
    removed
    untriagedNew issue has not been triaged by the area owner
    on Jul 8, 2021
  6. danmoseley
    added
    help wanted[up-for-grabs] Good issue for external contributors
    on Apr 10, 2022

  7. dotnet-policy-service commented on Oct 19, 2026

    @dotnet-policy-service
    dotnet-policy-serviceBot
    on Oct 19, 2026 – with Dotnet Policy Service
    Contributor

    Due to lack of recent activity, this issue has been marked as a candidate for backlog cleanup. It will be closed if no further activity occurs within 14 more days. Any new comment (by anyone, not necessarily the author) will undo this process.

    This process is part of our issue cleanup automation.

  8. dotnet-policy-service commented on Oct 19, 2026

    @dotnet-policy-service
    dotnet-policy-serviceBot
    on Oct 19, 2026 – with Dotnet Policy Service
    Contributor

    Due to lack of recent activity, this issue has been marked as a candidate for backlog cleanup. It will be closed if no further activity occurs within 14 more days. Any new comment (by anyone, not necessarily the author) will undo this process.

    This process is part of our issue cleanup automation.

  9. dotnet-policy-service
    added
    backlog-cleanup-candidateAn inactive issue that has been marked for automated closure.
    no-recent-activity
    on Oct 19, 2026

  10. Fs00 commented on Oct 25, 2026

    @Fs00
    Fs00
    on Oct 25, 2026
    ContributorAuthor

    This issue is still relevant.

  11. dotnet-policy-service
    removed
    no-recent-activity
    backlog-cleanup-candidateAn inactive issue that has been marked for automated closure.
    on Oct 25, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    area-System.ServiceProcesshelp wanted[up-for-grabs] Good issue for external contributors

    Type

    No type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions