Windows Service Won't Start? Find the Event Viewer Error
When a Windows service won't start, Event Viewer can help you find the error recorded during the failed attempt. Start with the System log , then compare the service's event with application-specific messages from the same time.
For a business, that evidence can save time when an application or shared resource stops working. Before changing settings, capture the service name and the failure time so you can connect the right events to the problem.
Record the Service and Failed Start Time
Open the Windows Start menu, search for Services , and select the app. Find the affected service in the list, then open its properties.
Record both the display name and the service name shown on the General tab. They can differ, and an event message may use either one. Also note the computer name and whether the service is stopped or already trying to start.
Capture the Attempt
If an authorized administrator has already tried to start the service, record the approximate time and any message Windows displayed. Keep the complete wording, including any error code.
If a test is needed, coordinate it with IT first. A start attempt on a production server can affect other applications or generate additional messages, so staff should know which system is being tested.
Note the Business Impact
Write down what employees can't do and which devices or users are affected. One affected workstation calls for a different scope of investigation than an application failure reported across an office.
Also note any relevant change reported before the failure, such as a deployment or network change. Timing alone doesn't establish that the change caused the problem, but it gives IT a useful point to investigate.
Open the Relevant Windows Logs
Press Windows + R
, enter eventvwr.msc
, and press Enter. Event Viewer opens with a navigation tree on the left.
Expand Windows Logs and select System . Windows records Service Control Manager events here, making it the first place to look for a service start failure. Give the log time to load, especially on a busy server.
Review the Application Log
Under Windows Logs, select Application . Look around the same time for events associated with the affected application or its publisher.
The System log and Application log can contain different parts of the same incident. Keep both in view during the investigation rather than assuming that the first message tells the whole story.
Look for Product-Specific Logs
Expand Applications and Services Logs in the left pane. Some applications have their own folders and logs there. Windows components may also have logs under Microsoft > Windows , often with an Operational log inside a component folder.
Available logs vary by device and installed software. Open the folder that matches the affected component, if one exists, and inspect entries near the failed start time. An empty or disabled log won't provide a record of an earlier attempt.
Filter Service Control Manager Events
Return to Windows Logs > System . In the Actions pane on the right, select Filter Current Log .
Choose a useful period in the Logged menu. Then open the Event sources list and select Service Control Manager . Apply the filter to narrow the System log to events from that source.
You can also select event levels in the filter. Include errors and warnings, but don't assume that only error-level entries matter. Information events near the attempt may help establish what happened before or after the failure.
Find the Service in the Results
Sort or scan the filtered list by Date and Time . Select events close to the recorded attempt and read their messages for the service's display name or service name.
If the list is still long, use Find in the Actions pane and search for the name. A search helps locate matching text, but it doesn't replace checking the time and the surrounding entries.
Widen the Filter When Needed
If you don't see a matching event, expand the time range. Check whether the failed start was attempted on the computer whose logs you're viewing, especially when an application has several servers.
Clear the filter when you're ready to inspect other sources. A filter changes what Event Viewer displays; it doesn't remove the underlying events.
Correlate Events With the Failed Attempt
The most useful event is one that matches both the service and the time of the attempted start. Open it, then review entries immediately before and after it.
Record the event's Date and Time , source, level, and event ID. Compare those fields with the message shown during the start attempt. If the times differ, account for the time shown on the affected computer and the time zone used in the support record.
Next, check the Application log and any relevant component log for the same window. An application may record more detail than the Service Control Manager entry, although a nearby event can also be unrelated.
Avoid treating every warning on the computer as part of the incident. Look for a shared service name, application name, account, or other detail that connects the entries. When the connection isn't clear, preserve the event for review rather than treating it as proof.
Read the Event Details
Double-click an event to open Event Properties . The General tab shows a readable message. The Details tab provides the event's structured fields, including an XML view.
Capture the Full Message
Read beyond the event title. The message may name a service or include an error code and additional text. Copy the full entry rather than recording the event ID alone.
Event IDs identify event types, but the message and surrounding events provide context. Two entries with the same ID can still require different investigation when their service names or error text differ.
Compare Structured Fields
If the General message is unclear, inspect the Details tab for fields that identify the service or associated data. Copy the event in full when sending it to IT so the next person can examine both the readable message and its fields.
Don't edit or clear logs to make the issue easier to see. Keeping the original entries gives support staff a record of the sequence before and after the attempted start.
Follow the Clues in the Message
Use the error text to decide which service details need attention. The event is a starting point for investigation, not permission to change settings without understanding the application.
Account and Access Messages
If the message refers to a logon failure, record the account identified in the event, if one appears. An administrator can review the service's Log On tab in Services alongside the event.
For an access-denied message, capture the named resource and the complete wording. IT can use those details to review the relevant permissions. Don't send passwords, recovery codes, or other credentials with the event.
Repeated attempts can complicate an account investigation, so coordinate further testing with IT instead of retrying continuously.
Dependencies and File Paths
If an event names another service, compare that name with the affected service's Dependencies tab. Record the dependency's name and status along with any related events from the same time.
When an event includes an executable or file path, preserve the path exactly as displayed. The General tab in service properties also shows the configured path to the executable. IT can compare the two pieces of information without guessing from a shortened screenshot.
Prepare a Useful Support Request
A clear handoff lets your IT team investigate without repeating the first steps. Include the computer name, service display name and service name, the time of the attempt, and the business task affected.
Add the full event message, source, event ID, and any error code. If you've found related entries in the Application log or a component log, include those with their timestamps. Mention what was attempted and whether the problem affects other computers or users.
Event Viewer also offers options to copy an event or save selected events. Use your organization's approved support channel, and review attachments for sensitive information before sharing them.
Our guide to writing an effective IT support ticket covers the details that help a technician act on a request. For a separate example of using logs in Windows troubleshooting, see our guide to temporary profile errors.
Verify the Service After a Change
Once an authorized administrator has addressed the issue, repeat the start attempt in a planned test window. Record the new time so you can distinguish the test from earlier failures.
Check the Service and Logs
Return to Services and check the affected service's status. A Running status is a useful first sign, but observe it long enough to see whether the service remains running.
Then return to Event Viewer. Review the System log around the new attempt and inspect any application or component logs that contained relevant messages before. Record new errors as well as events that show the outcome of the test.
Test the Business Function
Ask an authorized user to test the application or resource that was unavailable. A service can appear to run while the business workflow still needs attention, so the user-facing test matters.
Document the change, the test time, and the result in the support record. If the failure returns, send IT the new event details alongside the original ones. That comparison gives the team a clearer record for the next investigation.
Use the Event Record to Guide the Next Step
When a Windows service won't start, begin with the service name and the time of the failed attempt. The matching event message , supported by nearby application or component logs, gives IT a stronger starting point than an isolated error code.
Keep the original record and compare it with a test after the change. The service status and the affected business workflow should both be part of the final check.

