sc qc asks Windows for the stored configuration of a service. It is the natural read-only follow-up to Windows Command #37 — sc config. Where sc config changes settings, sc qc lets you inspect important settings such as the startup type, executable path, service account, display name, dependencies, and error-control behavior.

Basic Syntax

sc.exe qc ServiceName

Microsoft documents qc as one of the commands available through Sc.exe, the command-line interface to the Windows Service Control Manager. Use the internal service name rather than assuming the friendly display name is identical. If you do not know the service name yet, review Windows Command #34 — sc query.

What the Output Tells You

A typical sc.exe qc result exposes the service’s saved configuration rather than its moment-to-moment running state. That difference is important. sc query answers questions such as “Is it running?” while sc qc answers questions such as “What executable starts this service, under which account, and with which startup policy?”

sc.exe qc Spooler

• SERVICE_NAME — the internal Windows service name.
• TYPE — the kind of service or driver.
• START_TYPE — automatic, manual/on-demand, disabled, or another supported start mode.
• ERROR_CONTROL — how Windows treats a startup failure.
• BINARY_PATH_NAME — the executable path and, when present, command-line arguments used to launch the service.
• LOAD_ORDER_GROUP — the service’s load-order group when one is configured.
• DISPLAY_NAME — the human-friendly service name.
• DEPENDENCIES — services or groups that must be available first.
• SERVICE_START_NAME — the account under which the service is configured to run.

Why BINARY_PATH_NAME Matters

BINARY_PATH_NAME is one of the most useful fields during troubleshooting. It tells you what Windows is actually configured to launch for that service. If a service exists but fails to start, this path can help you check whether the executable still exists, whether the path is correct, whether expected arguments are present, and whether the installation points to the location you expected. A practical Super User example demonstrates using sc qc specifically to expose a service’s executable path.

START_TYPE Is Configuration, Not Status

If sc qc reports AUTO_START, that tells you the service is configured for automatic startup. It does not prove the service is running right now. A service can be configured for automatic startup and still be stopped because it failed, was manually stopped, or has not yet completed startup. Pair sc qc with sc query when you need both configuration and current state.

Inspect Before You Change

A safe Windows service workflow is query first, inspect configuration second, change only when necessary, then verify again. For example, before changing a startup type with sc config, record the original START_TYPE, executable path, service account, and dependencies with sc qc. That gives you a baseline and makes rollback much easier.

sc.exe query Spooler
sc.exe qc Spooler
sc.exe config Spooler start= demand
sc.exe qc Spooler
sc.exe query Spooler

Getting services status via SC command instead of powershell
byu/maxcoder88 inPowerShell

Use sc.exe in PowerShell

As covered earlier in the command series, classic Windows PowerShell can interpret sc as an alias for Set-Content. Writing sc.exe qc ServiceName removes that ambiguity and makes documentation easier to copy between Command Prompt and PowerShell.

Quick Lab

1. Open Command Prompt as Administrator on a Windows lab machine.
2. Choose a service you understand, such as a noncritical lab service.
3. Run sc.exe query ServiceName and note the current running state.
4. Run sc.exe qc ServiceName.
5. Identify the START_TYPE, BINARY_PATH_NAME, DISPLAY_NAME, DEPENDENCIES, and SERVICE_START_NAME.
6. Compare the configuration output with the current-state output from sc query.
7. Do not change anything unless the lab specifically requires it.

Knowledge Check + Answers

1. What does sc qc do? It queries the stored configuration of a Windows service.
2. Which field shows the executable used by the service? BINARY_PATH_NAME.
3. Which field shows the configured startup policy? START_TYPE.
4. Does AUTO_START prove the service is currently running? No.
5. Which field identifies the configured service account? SERVICE_START_NAME.
6. Why run sc qc before sc config? To capture the original configuration before making a change.

Previous Windows Commands

• #34 — sc query
• #35 — sc start
• #36 — sc stop
• #37 — sc config

Editor’s Note

The featured image follows the current art rule: approved realistic editorial photography, one clear subject, no UI/dashboard boxes, no fake infographic layout, and no poster-style headline composition. The body image is separate. The video and Reddit embeds are directly relevant to Windows service administration and sc configuration inspection.

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