If you are creating Windows Services you may run into this annoying little error from time to time,

Error 1001. The specified service has been marked for deletion

At first I used to restart my machine to get rid of it, but there is a (much) simpler way.  Simply closing the Services Manager (services.msc or the mmc.exe tool) will solve it :)

Tagged with:

78 Responses to Solving Error 1001 : The specified service has been marked for deletion

  1. Anonymous says:

    Thank you!

    Your tip just saved me from an anxious extra 30 mins at the end of a day :-)


  2. Anonymous says:

    Yes. it worked.



  3. Anonymous says:

    Unfortunatelly Mr. Laxdal this step to fix the issue doesn’t work everytime. It’s not always a true that admin has this MMC console opened when he is notified by a system that The specified service has been marked for deletion. Microsoft advice has to be followed in most of the other cases.

  4. Anonymous says:

    Solved my problem. Thanx!

  5. Anonymous says:

    Was stucked up !!! thnks a lot !!!


  6. Anonymous says:

     Thanks for the tip, Microsoft should fix this one.

  7. Anonymous says:


  8. Anonymous says:

    Muchas gracias señor.

  9. Anonymous says:


  10. Anonymous says:

     Thx. Saved my day.

  11. Anonymous says:

    also need to close any other tool acts like the service control manager (SQL Server Management Studio, Process Explorer, etc.)

  12. Anonymous says:

     Awesome, it worked, thanks! What the hell was that about? :)

  13. Anonymous says:

    Thank you very much, man!

    Close commgmt.msc on client machine and trouble on server is solved :)

  14. Anonymous says:

    Thank you very much.

  15. Anonymous says:

    Thanks a lot

  16. Anonymous says:

     Make sure you have the service stopped. You can delete the service with it still running. If you try to reinstall the service without explicitly stoppping it, you will get that error message

  17. Anonymous says:

     My thanks, too !

  18. Anonymous says:

     Thanks a Lot man! that worked!

  19. Anonymous says:

    A dozen sites later, and here is the answer.  Simple info, offered up without going into irrelevant information.





  20. Anonymous says:

     Sweet, thanks! Saved me having to restart a crucial web server!

  21. Anonymous says:

    Perfect :)


  22. Anonymous says:

    Thanks a lot!

  23. Anonymous says:

     Thanks, it works :)

  24. Anonymous says:

    Thanks mate, You same my time.

  25. JM says:

    THanks a lot !

  26. Anonymous says:

    Thank You Man!!!

  27. Daniel says:

    That did it. Thank you!

  28. Manjunath BE says:

    Thanks dude..

  29. Antony says:

    Thanks for the tip! You just saved me a paintstaking half-hour server reboot…phew.

  30. Anonymous says:

    Thank you!!!!

  31. eduardo says:

    awsome, it is exacletly what i was looking for! :)

  32. hamid says:

    tanx you saved my time 2

  33. Anonymous says:

    Ahhhhhh. Thanks

  34. Alex says:

    Genius. Thankyou so much

  35. Stranger says:

    Thanks for sharing… really helpful

  36. Anne Nonymous says:

    Bloody hell, the number of times I’ve restarted servers, when all I had to do was close the services MSC – thanks!

  37. Anonymous says:

    Thank you very much again, ißm happy now!

  38. […] the past, a simple restart of your machine would have solved the problem, however Jóhannes Laxdal has come up with a better solution – simply close your mmc console and re-open […]

  39. Anonymous says:

    Lov u!!! and your tie too!

  40. Anonymous says:

    Thank you!

  41. Romain says:

    Ouf! Thanks a lot :)

  42. Anonymous says:

    Wonderful, thanks mate.

  43. Anonymous says:

    Great tip. Thanks!

  44. Ant says:

    Not for me. Services.exe can’t be killed since I saw no Services Manager’s window running. :(

  45. vilas says:

    thanks it’s solve my problem

  46. Mite says:

    Thanks a lot man

  47. Anonymous says:


  48. Anonymous says:

    Thanks! For crying out loud Microsoft, can’t you do better than this?

  49. Anonymous says:

    Much help!

  50. Troy Sutton says:

    That was a great tip I was reading other sites that were telling me to reboot. Thank you kindly.

  51. Mike Dorough says:

    amazing, it worked!

  52. Sam says:

    Thanks, you saved me a lot of time.

  53. Sash says:

    Thanks DUDE !!! you’re awesome !

  54. Dimitri says:

    Thank you, I was sick of rebooting.

  55. Sergey says:


  56. Anonymouse says:

    Worked like a charm. 15 mins before end of the day so really didn’t want to reboot.

  57. Anonymous says:

    Nice – I sat here for 20 minutes waiting for an entry to disappear after deleting a service..just have to close the window? wtf windows!

  58. Llyr Jones says:

    Also, I discovered that if you run ProcessExplorer it also locks the service.

  59. Parag says:

    It worked like a charm!

  60. asd says:

    thanks a lot

  61. Eik says:

    It’s the little things in life … :)


  62. Povilas says:

    It worked! Thank you! :)

    There is no way we could restart server every time it happens.

  63. Granite26 says:


  64. worked for me. close services.msc and procexp.exe.

  65. Anonymous says:

    Thanks, it’s very easy and eficiently

  66. Anonymous says:

     Thanks bro!  Very helpful.

  67. Anonymous says:

    didn’t worked for me :(

    going to try the microsoft approach … restarting  

  68. Anonymous says:


  69. Anonymous says:

    Thanks! almost restarted my machine, whew!

  70. Anonymous says:

    Sos grande!

  71. Anonymous says:

    Saved my day! Thanks!

  72. Anonymous says:

     Chido carnal

  73. Anonymous says:

    Thanks, you’re a righteous dude. I abide.

  74. Anonymous says:

     Another thanks!

    I’ve got it when I uninstalled the service and tried to install it anew. Looks like Services Manager locks the service even if it has been uninstalled during Services Manager was open.

  75. Otto says:

    I can’t believe it was that easy. Thanks!