Updates from editor

Author: v-phoebh

support/windows-client/system-management-components/task-scheduler-service-not-start.md

@@ -1,7 +1,7 @@
 ---
 title: Troubleshoot Task Scheduler Service Startup Failure
 description: Helps troubleshoot the failure to start the Task Scheduler service in Windows computers.
-ms.date: 04/09/2025
+ms.date: 04/11/2025
 manager: dcscontentpm
 audience: itpro
 ms.topic: troubleshooting
@@ -26,16 +26,16 @@ The Task Scheduler service isn't started in the **Services** snap-in (**Services
 
 Each error message has different causes and resolutions.
 
-## The Task Scheduler service on Local Computer started and then stopped
+## Error: The Task Scheduler service on Local Computer started and then stopped
 
-This error occurs because the Time Broker service is either stopped or disabled. To resolve the error, enable and then start the service by using one of the following methods.
+This error occurs because the Time Broker service is either stopped or disabled. To resolve the error, enable and start the service by using one of the following methods.
 
 > [!NOTE]
-> The Time Broker service coordinates the execution of background work for WinRT applications. If this service is stopped or disabled, then background work might not be triggered.
+> The Time Broker service coordinates the execution of background work for WinRT applications. If this service is stopped or disabled, background work might not be triggered.
 
 ### Use the Services snap-in
 
-Select **Start** > **Windows Administrative Tools** > **Services**, and check if the Time Broker service is running. If it isn't running or is in a disabled state, enable it and then start it.
+Select **Start** > **Windows Administrative Tools** > **Services**, and check if the Time Broker service is running. If it isn't running or is disabled, enable it and then start it.
 
 ### Use Registry Editor
 
@@ -47,23 +47,24 @@ If that doesn't resolve the issue and you still can't start the Task Scheduler s
 
 ## Error 5: Access is denied
 
-This error occurs because the NT AUTHORITY\\SYSTEM account doesn't have write permissions on the System event log. The permissions might have been modified by a system administrator with a `CustomSD` registry key for other purposes.
+This error occurs because the NT AUTHORITY\\SYSTEM account doesn't have write permissions to the System event log. The permissions might have been modified by a system administrator using a `CustomSD` registry key for other purposes.
 
 The Task Scheduler service runs under the SYSTEM account. By default, the SYSTEM account has write permissions to the System event log to allow the Task Scheduler service to log events into the System event log.
 
-The security of each log is configured locally through the values in the registry key:
+The security of each log is configured locally through the values in the following registry key:
 
 `HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\EventLog`
 
-If the System event log permissions are customized, the System log security descriptor is configured through:
+If the System event log permissions are customized, the System log security descriptor is configured through the following registry key:
 
 `HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\EventLog\System\CustomSD`
 
-The security descriptor is specified by using Security Descriptor Definition Language (SDDL) syntax. The SDDL should have the SYSTEM account with Read, Write, and Clear permissions in the following context:
+The security descriptor is specified using the Security Descriptor Definition Language (SDDL) syntax. The SDDL should grant the SYSTEM account Read, Write, and Clear permissions in the following context:
 
 `(A;;0xf0007;;;SY)`
 
-The value of SY (SYSTEM account) is 7, which means Read(1)+Write(2)+Clear(4). If not, change it to 7 for it to have the proper permissions on the System event log. Once the SDDL of the SYSTEM account has been corrected, restart the machine and check if the Task Scheduler service is started.
+The value of SY (SYSTEM account) is `7`, which means Read(1)+Write(2)+Clear(4). If not, change it to `7` so it has the proper permissions to the System event log. Once the SDDL of the SYSTEM account has been corrected, restart the machine and check if the Task Scheduler service is started.
+
 You can also check the SDDL of the System event log by running the following command:
 
 ```console
@@ -88,16 +89,16 @@ If that doesn't resolve the issue and you still can't start the Task Scheduler s
 
 This error occurs because a file related to the Task Scheduler service is missing or can't be found.
 
-In this case, a required system file is missing, or the Task Scheduler service is referring to an invalid file under its registry configuration.
+In this case, a required system file is missing, or the Task Scheduler service refers to an invalid file under its registry configuration.
 
 Determine if the service is configured correctly under its registry configuration:
 
 1. Open Registry Editor.
-2. Go to the Task Scheduler service location under:
+2. Go to the Task Scheduler service location under the following path:
 
     `HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Schedule\Parameters`
 
-3. In right pane, check if the registry value `ServiceDll` has the value data of `%systemroot%\system32\schedsvc.dll`.
+3. In the right pane, check if the registry value `ServiceDll` has the value data of `%systemroot%\system32\schedsvc.dll`.
 4. If it does, check if the **schedsvc.dll** file exists under **%systemroot%\system32**.
 5. If the DLL file is missing, [use the System File Checker tool to repair missing or corrupted system files](https://support.microsoft.com/topic/use-the-system-file-checker-tool-to-repair-missing-or-corrupted-system-files-79aa86cb-ca52-166a-92a3-966e85d4094e).
 6. Once the repair is done, start the Task Scheduler service.