sc.exe description sets or changes the description string stored for a Windows service. It is the write-side partner to Windows Command #39 — sc qdescription. The previous command reads the current description; this command changes it.

Basic Syntax

sc.exe description ServiceName "Description text"

Microsoft’s current Sc.exe configuration documentation still lists description as a supported Service Control Manager command. The command expects the internal service name rather than assuming the friendly display name is identical.

sc.exe description ExampleService "Background service used by the lab application."

This changes service metadata. It does not start the service, stop it, alter its startup type, or replace its executable path. Those are separate operations handled by commands such as sc config, sc start, and sc stop.

Read Before You Write

A safe workflow is to inspect the existing description before changing it. Use sc.exe qdescription first, record the current value, make the approved change, and then query it again.

sc.exe qdescription ExampleService
sc.exe description ExampleService "Background service used by the lab application."
sc.exe qdescription ExampleService

This read-change-read pattern is useful because it gives you a baseline and immediate verification. It also makes documentation and rollback easier if the description needs to be restored later.

Service Name vs. Display Name

Windows services can have an internal service name and a friendlier display name. sc.exe expects the service name for commands such as description. If you are uncertain which identifier to use, inspect the service first with sc query or use the appropriate SC name-mapping command before making a configuration change.

A Common Deployment Pattern

Custom services are often created first and described second. A long-running Stack Overflow discussion on setting a Windows service description with sc.exe shows the same practical pattern: create the service, then run a separate sc description command to populate the description field.

sc.exe create ExampleService binPath= "C:\Services\ExampleService.exe"
sc.exe description ExampleService "Background service used by the lab application."
sc.exe qdescription ExampleService

Do this only with a real service executable and only on systems you are authorized to administer. Creating a service is a separate administrative action from changing its description.

Remote Computer Syntax

SC can target a remote Windows computer by placing the UNC server name immediately after sc.exe. Permissions, firewall policy, and remote service-management access still determine whether the command succeeds.

sc.exe \\SERVER01 description ExampleService "Updated service description"
sc.exe \\SERVER01 qdescription ExampleService

Remote configuration should be treated as a production change. Verify the target computer and service name before pressing Enter, especially when similar service names exist on multiple servers.

What are Windows Services ? (Part 2)
byu/boutnaru inwindows

Use sc.exe in PowerShell

In Windows PowerShell, write sc.exe explicitly. The short name sc can resolve to the PowerShell Set-Content alias instead of the Windows Service Control executable. Using the full executable name makes the command unambiguous in both Command Prompt and PowerShell documentation.

What This Command Does Not Change

• Running state: use sc query, sc start, or sc stop.
• Startup type: use sc config.
• Binary path and service account: inspect with sc qc and change only through an approved configuration workflow.
• Description readback: use sc qdescription.

Quick Lab

1. Use a Windows lab machine and a noncritical test service that you are authorized to modify.
2. Run sc.exe qdescription ServiceName and save the original description.
3. Run sc.exe description ServiceName "Temporary lab description".
4. Run sc.exe qdescription ServiceName again.
5. Open services.msc and confirm the description field matches the change.
6. Restore the original description when the lab is complete.

Knowledge Check + Answers

1. What does sc.exe description change? The stored description string for a Windows service.
2. Which command reads the description without changing it? sc.exe qdescription.
3. Does changing the description restart the service? No.
4. Which identifier should you normally use? The internal service name.
5. Why use sc.exe rather than only sc in PowerShell? To avoid ambiguity with the Set-Content alias.
6. What is the safest sequence? Query the old value, make the approved change, and query again to verify.

Previous Windows Commands

• #34 — sc query
• #35 — sc start
• #36 — sc stop
• #37 — sc config
• #38 — sc qc
• #39 — sc qdescription

Editor’s Note

The featured image and body image are separate. This lesson uses standard responsive Gutenberg headings, paragraphs, lists, images, embeds, and code blocks only for actual commands. No ordinary prose is placed inside decorative text boxes.

BitcoinVersus.Tech is not a financial advisor. Content is provided for informational and educational purposes.