Skip to content

Commit 46ecdaf

Browse files
authored
Updates from editor
1 parent 549284e commit 46ecdaf

1 file changed

Lines changed: 5 additions & 5 deletions

File tree

support/windows-client/system-management-components/task-schedular-service-is-not-available.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,8 @@
11
---
2-
title: Scheduled tasks fail with error "Task schedular service is not available"
3-
description: Helps resolve the error in which scheduled tasks fail with the error "Task schedular service is not available."
2+
title: Scheduled Tasks Fail with Error Task Schedular Service Is Not Available
3+
description: Helps resolve the error Task schedular service is not available in which scheduled tasks fail.
44
manager: dcscontentpm
5-
ms.date: 04/07/2025
5+
ms.date: 04/10/2025
66
ms.topic: troubleshooting
77
ms.reviewer: kaushika, warrenw, v-lianna
88
ms.custom:
@@ -31,7 +31,7 @@ Use the following steps to resolve the issue:
3131
## Step 1: Clean up at tasks if they exist
3232

3333
> [!NOTE]
34-
> [At](/windows-server/administration/windows-commands/at) tasks refer to tasks scheduled to run automatically by the OS using the `at` command. It's a legacy command in Windows for scheduling tasks at specified time and date. These tasks are managed by the Task Scheduler service. After an OS upgrade, such tasks might fail due to compatibility issues or problems with the Task Scheduler service. This could affect the successful launch of Task Scheduler.
34+
> [At](/windows-server/administration/windows-commands/at) tasks refer to tasks scheduled to run automatically by the OS using the `at` command. It's a legacy command in Windows for scheduling tasks at specified time and date. These tasks are managed by the Task Scheduler service. After an OS upgrade, such tasks might fail due to compatibility issues or problems with the Task Scheduler service. This might affect the successful launch of Task Scheduler.
3535
3636
Check the **C:\\Windows\\System32\\Tasks** folder to determine if you have any `at` tasks created under Task Scheduler. If so, the tasks are listed under the following locations. For example:
3737

@@ -108,7 +108,7 @@ To resolve this issue, clean up the legacy tasks by using the following steps:
108108

109109
## Step 2: Delete corrupted tasks and then create them again if needed
110110

111-
If you have cleaned up the `at` tasks or you don't have `at` tasks, you might have corrupted tasks that causing this issue. Find the corrupted tasks, delete them and then create them again if needed.
111+
If you have cleaned up the `at` tasks or you don't have `at` tasks, you might have corrupted tasks that cause this issue. Find the corrupted tasks, delete them, and then create them again if needed.
112112

113113
1. Find the corrupted tasks:
114114

0 commit comments

Comments
 (0)