Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstalliTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Windows has no universal “restore this service to defaults” command. Service defaults vary by service, Windows release, and sometimes the installed application. The safe method is to identify the service’s internal name, record its current configuration, verify the intended values for the same Windows version, and change only the fields you can substantiate.
If the problem followed a recent system change, System Restore can roll back a wider set of changes. If Windows component files are damaged, run DISM followed by System File Checker (SFC). Reset this PC is a reinstall-level recovery option, not a normal first step for one misconfigured service.
What “default settings” means for a Windows service
A service can be wrong in several different ways. It may be stopped, disabled, assigned the wrong startup type, pointed at an incorrect executable, running under the wrong account, missing a dependency, or affected by changed permissions. A service that is merely stopped does not necessarily have damaged configuration.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Microsoft’s SC.exe configuration reference lists possible values for individual fields, but it does not define one startup type that is correct for every installed service. The command changes the selected entries in the registry and the Service Control Manager database; it is not a universal reset.
#1 Best Overall
In particular, the documentation’s description of demand as the default used when the start= option is omitted describes command syntax. It does not mean that every Windows service originally used Manual (the user-facing label for demand start). Do not set all services to Manual, Automatic, or Disabled as a shortcut.
For a Microsoft service, the correct reference is documentation for the same Windows release. For a third-party service, use the software publisher’s instructions for the exact product version. Copying a configuration from another computer, another Windows edition, or another application release can prevent the service or the feature that depends on it from starting.
Choose the least disruptive recovery path
| Path | Use it when | Scope and trade-off |
|---|---|---|
Correct a verified field with SC.exe |
One service field was changed and its intended value is known | Targeted; an incorrect value can stop the service or the Windows feature that relies on it. See Microsoft’s configuration syntax. |
| Undo a clean-boot change | Services were disabled in System Configuration during clean-boot troubleshooting | Reverses that troubleshooting setup only; it is not a general configuration reset. Follow Microsoft’s clean-boot recovery instructions. |
| System Restore | A suitable restore point predates the problem and a broader rollback is acceptable | Reverts system files, registry settings, and installed-program changes associated with the restore point while preserving personal files, according to Microsoft’s System Restore guidance. |
| DISM followed by SFC | Windows component or protected system-file corruption is suspected | Repairs the Windows image and protected system files; Microsoft does not describe these tools as a reset for arbitrary service settings. See the DISM and SFC procedure. |
| Reset this PC | Other recovery methods are unsuitable and reinstalling Windows is justified | Broadest impact: apps and settings are removed, and the effect on personal files depends on the option selected. Review Microsoft’s Reset your PC and recovery-options documentation first. |
Inspect the service before changing anything
1. Define the symptom
Write down what prompted the repair. “The service is stopped” is different from “the service fails with an executable-path error,” “the startup type changed to Disabled,” or “a dependent application cannot authenticate.” This distinction determines whether you need to start a service, correct one configuration field, or repair a wider Windows problem.
2. Find the internal service name
The name shown in the Services console can be a friendly display name. The command-line tools require the service name used by Windows. Microsoft’s SC.exe service-configuration guide documents querying and modifying the installed-services database. Use the service’s properties in the Services console to distinguish its service name from its display name, and do not substitute a guess.
3. Open an elevated terminal
Open Windows Terminal, Command Prompt, or PowerShell with administrator rights. Without elevation, a query may be incomplete and a configuration change can fail because the Service Control Manager or registry entries require administrative access.
4. Record the current state
Replace the placeholder with the internal name and run:
sc.exe qc <service-name>
sc.exe query <service-name>sc.exe qc queries the service configuration; sc.exe query reports its current state. Record the startup setting, executable path, logon account, dependencies, display name, and any error-control or other field that you plan to compare. Also note whether the service is running, stopped, or reporting an error. Keep this record so you can undo your change if the result is worse.
Verify the intended values instead of guessing
Use a same-version reference
Compare the captured values with documentation for the same Windows release and edition. Windows 10 and Windows 11 can differ, and Microsoft’s command documentation applies to several Windows versions without claiming that every service has the same original configuration. A service’s executable path, account, dependency list, and permissions can be as important as its startup type.
Check third-party documentation separately
For a service installed by an application, consult that application’s support instructions for the exact version. Do not copy the values from a similarly named service or from a different computer. A vendor may intentionally use a custom account, path, dependency, or delayed startup.
Separate a clean-boot change from corruption
If you recently performed a clean boot, the service may have been disabled deliberately for troubleshooting. That is a reversible test configuration, not evidence that its original settings are damaged. Use Microsoft’s instructions for returning Windows to normal startup and re-enable services that you intentionally disabled during the test.
Change one verified field with SC.exe
Microsoft’s syntax is field-specific. The general form is:
Free tools Windows power users keep installed
One-click scans. No signup required.
sc.exe config <service-name> <option>= <value>There must be a space between the equals sign and the value. For example:
sc.exe config <service-name> start= autoUse that example only when documentation for your service says that auto is the intended value. Other startup choices documented by Microsoft include boot, system, demand, disabled, and delayed-auto. Those are available values, not a universal default.
Options you may need to verify
| Configuration area | What to verify before changing it | Why a guess is risky |
|---|---|---|
start= |
The documented startup behavior for this service and Windows version | Starting too early, too late, or never can break dependencies or increase exposure to failures. |
type= |
Whether the service is a Win32 service, shared process, or another documented type | The service may no longer load in the way its executable expects. |
binpath= |
The complete, correctly quoted executable path supplied by the application or Microsoft | A typo or incorrect quoting can make the Service Control Manager unable to launch it. |
obj= |
The documented logon account | The account may lack required rights, or changing it may expose credentials or data. |
depend= |
The exact dependency list | Removing a required dependency can produce startup failures; adding a wrong one can create a cycle or unnecessary delay. |
error=, group=, tag=, or displayname= |
The value shown in authoritative documentation for that service | These fields affect failure handling, load ordering, identification, or grouping and are not interchangeable with startup settings. |
Only include the option you intend to change. Microsoft’s command changes the entries supplied on the command line; omitting an option does not restore it to an original value. Do not place an unverified executable path or a guessed account in the command. If a credential-related field must be changed, follow the application’s supported procedure rather than exposing a password in command history.
Verify after the command completes
- Run the same
sc.exe qc <service-name>query again and confirm that the intended field changed while unrelated fields remain as recorded. - Run
sc.exe query <service-name>to check the service state. - Test the Windows feature or application that depends on the service, not just the service entry itself.
- If the documented procedure requires a restart, restart Windows and test again. Do not repeatedly change fields when the evidence points to a different problem.
For details about which service parameters can be changed and how Windows stores them, see Microsoft’s Changing a Service’s Configuration documentation.
Return from a clean boot to normal startup
Use this path only when you disabled services as part of clean-boot troubleshooting. Open System Configuration by running msconfig, select Normal startup on the General tab, and follow Microsoft’s clean-boot instructions to re-enable the services you disabled for the test. Apply the changes and restart when prompted.
This restores the clean-boot experiment’s service-selection changes. It does not reconstruct an executable path, logon account, dependency list, permission, or other value that was changed independently.
Use System Restore when a suitable restore point exists
System Restore is appropriate when you can identify a restore point from before the service problem and you accept rolling back other system changes made after that point. Microsoft says it can revert system files, registry settings, and installed programs associated with the restore point while leaving personal files unaffected.
- Open System Restore from Windows, or launch it from Windows Recovery Environment if Windows cannot start normally.
- Select a restore point dated before the service configuration changed.
- Use the option to scan for affected programs, if offered, so you can see which applications and drivers may be removed or restored.
- Confirm the restore, allow Windows to restart, and test the affected service and application.
System Restore is deliberately broader than an SC.exe config change. It can undo unrelated registry or program changes made after the selected point, so use it only when that trade-off is acceptable.
Repair Windows files with DISM, then SFC
If symptoms suggest that Windows components or protected system files are corrupt, Microsoft’s order is DISM first and SFC second. Open an elevated Terminal or Command Prompt and run:
DISM.exe /Online /Cleanup-image /Restorehealth
sfc /scannowWait for each command to finish before starting the next one. DISM repairs the Windows image that SFC relies on; SFC then checks and repairs protected system files. These tools address Windows-image and system-file integrity. Microsoft does not document them as a method for restoring arbitrary service startup values, executable paths, accounts, dependencies, or permissions, so query the service again after repair and correct a verified configuration field separately if necessary.
Microsoft’s procedure is documented at Use the System File Checker tool to repair missing or corrupted system files.
When Reset this PC is justified
Reset this PC reinstalls Windows and should be a later recovery choice when targeted correction, clean-boot reversal, System Restore, and file repair do not solve a broader system problem. Back up important data before starting any reset.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →| Reset option | Personal files | Apps and settings |
|---|---|---|
| Keep my files | Personal files are preserved according to Microsoft’s reset guidance | Installed apps and settings are removed |
| Remove everything | Personal files are removed | Apps and settings are removed |
Read Microsoft’s Reset your PC instructions and the broader Recovery options in Windows overview before choosing. A reset may solve a damaged installation, but it is disproportionate when one service entry is the only known problem.
Common mistakes and how to avoid them
Using the display name in a command
A friendly name and the internal service name are not guaranteed to match. Query the exact service name first and use that value in every sc.exe command.
Forgetting the space after “=”
Use start= auto, not start=auto. The documented syntax requires the space. The same rule applies to other options.
Assuming “demand” means the original default
demand is a command-syntax default when start= is omitted in Microsoft’s reference. It is not proof that the service was originally Manual. Verify the service-specific value instead.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problemsChanging every service to the same startup type
Windows services have different roles and dependencies. A blanket change can disable required components or start services that should remain on demand. Correct only the field and service you can identify.
Copying values from another Windows installation
Service configuration can vary by Windows version, edition, installed updates, and application version. Treat another computer as an unverified reference, not as a template.
Confusing a stopped service with a damaged configuration
Use sc.exe query to observe state and sc.exe qc to inspect configuration. If the settings match the authoritative reference, investigate the reported error, dependencies, permissions, or system-file integrity rather than rewriting the entry.
Ignoring the Windows version
Microsoft’s current support documentation covers Windows 10 and Windows 11, but ordinary Windows 10 support ended on October 14, 2025. Confirm procedures and service values against the release actually installed on the computer; do not assume that a current Windows 11 instruction is an original Windows 10 default.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →Quick Recap
A safe decision sequence
- Identify the affected service and describe the exact symptom.
- Find its internal service name and query it with
sc.exe qcandsc.exe query. - Record startup, path, account, dependencies, permissions, and other relevant fields before editing.
- Verify the intended values using same-version Microsoft documentation or the application publisher’s instructions.
- If a clean boot caused the change, return to normal startup instead of inventing new values.
- Use one narrowly scoped
sc.exe configcommand only when the correct value is established, observing the required space after each equals sign. - Re-query the service and test the dependent feature.
- Choose System Restore when a suitable restore point predates the issue and a broader rollback is acceptable.
- Run DISM followed by SFC when Windows component or protected-file corruption is suspected.
- Reserve Reset this PC for a broader Windows recovery need, and back up important files first.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
