Task that is created by using the "AT" command is not deleted after it is executed in Windows Vista, Windows Server 2008, Windows 7, or Windows Server 2008 R2
When you use the AT command to schedule tasks on a computer that is running Windows Vista, Windows Server 2008, Windows 7, or Windows Server 2008 R2, you experience one of the following issues.
Issue 1
When you schedule a single execution task by using the ATcommand, the task is not deleted after the task is executed. Specifically, you cannot find the task by using the AT command, but the task is listed in the Task Scheduler snap-in.at
Issue 2
Assume that you schedule a single execution task that runs at a scheduled time or date by using the ATcommand. In this situation, the task is not deleted after the task is executed, and the task runs weekly.
Notes
On a computer that is running a version of Windows that is earlier than Windows Vista and Windows Server 2008, task information is stored in a .job file.
On a computer that is running Windows Vista, Windows Server 2008, Windows 7, or Windows Server 2008 R2, task information is stored in an .xml file. Additionally, when you schedule a task by using the ATcommand, a .job file is created for compatibility.
Cause
These issues occur because the schema in the .job file does not have the "End boundary" and "Delete task as soon as its finished" nodes. When Schedsvc.dll registers a task by using the ATcommand, the Task Scheduler Compatibility plugin creates the .xml file that stores the task definition. However, the Task Scheduler schema v1.0 that Task Scheduler uses to create the .job file does not have the "End boundary" and "Delete task as soon as its finished" nodes. Therefore, the issues that are described in the "Symptoms" section occur.
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.
If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft website:
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.
Prerequisites
To apply this hotfix, you must be running one of the following operating systems:
Windows Vista Service Pack 2 (SP2)
Windows Server 2008 Service Pack 2 (SP2)
Windows 7
Windows 7 Service Pack 1 (SP1)
Windows Server 2008 R2
Windows Server 2008 R2 Service Pack 1 (SP1)
For more information about how to obtain a Windows Vista service pack, click the following article number to view the article in the Microsoft Knowledge Base:
How to obtain the latest Windows Vista service pack
For more information about how to obtain a Windows Server 2008 service pack, click the following article number to view the article in the Microsoft Knowledge Base:
How to obtain the latest service pack for Windows Server 2008
For more information about how to obtain a Windows 7 or Windows Server 2008 R2 service pack, click the following article number to view the article in the Microsoft Knowledge Base:
Information about Service Pack 1 for Windows 7 and for Windows Server 2008 R2
Registry information
To apply this hotfix, you do not have to make any changes to the registry.
Restart requirement
You must restart the computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace a previously released hotfix.
File information
Collapse this imageExpand this image
The global version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.
Windows Vista and Windows Server 2008 file information notes
Important Windows Vista hotfixes and Windows Server 2008 hotfixes are included in the same packages. However, only "Windows Vista" is listed on the Hotfix Request page. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows Vista" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.
The files that apply to a specific product, SR_Level (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table.
Collapse this tableExpand this table
Version
Product
SR_Level
Service branch
6.0.600
2
.
22xxx
Windows Vista and Windows Server 2008
SP2
LDR
The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows Vista and for Windows Server 2008" section. MUM files and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintaining the state of the updated component. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x86-based versions of Windows Vista and of Windows Server 2008
Collapse this imageExpand this image
Collapse this tableExpand this table
File name
File version
File size
Date
Time
Platform
Hashcleanup.exe
6.0.6002.22990
9,728
30-Nov-2012
01:28
x86
Taskcomp.dll
6.0.6002.22990
270,848
30-Nov-2012
02:54
x86
Taskschd.dll
6.0.6002.22990
352,768
30-Nov-2012
02:54
x86
Taskeng.exe
6.0.6002.22990
171,520
30-Nov-2012
01:28
x86
Taskeng.mof
Not applicable
2,254
09-Sep-2011
11:42
Not applicable
Schedsvc.dll
6.0.6002.22990
602,624
30-Nov-2012
02:54
x86
Schedsvc.mof
Not applicable
2,250
09-Sep-2011
11:42
Not applicable
Wmicmiplugin.dll
6.0.6002.22990
346,112
30-Nov-2012
02:54
x86
Collapse this imageExpand this image
For all supported x64-based versions of Windows Vista and of Windows Server 2008
Collapse this imageExpand this image
Collapse this tableExpand this table
File name
File version
File size
Date
Time
Platform
Hashcleanup.exe
6.0.6002.22990
10,240
30-Nov-2012
02:00
x64
Taskcomp.dll
6.0.6002.22990
410,624
30-Nov-2012
03:35
x64
Taskschd.dll
6.0.6002.22990
656,384
30-Nov-2012
03:35
x64
Taskeng.exe
6.0.6002.22990
268,800
30-Nov-2012
02:01
x64
Taskeng.mof
Not applicable
2,254
15-Nov-2011
15:19
Not applicable
Schedsvc.dll
6.0.6002.22990
857,088
30-Nov-2012
03:35
x64
Schedsvc.mof
Not applicable
2,250
15-Nov-2011
15:19
Not applicable
Wmicmiplugin.dll
6.0.6002.22990
500,736
30-Nov-2012
03:36
x64
Schedsvc.mof
Not applicable
2,250
09-Sep-2011
11:42
Not applicable
Taskcomp.dll
6.0.6002.22990
270,848
30-Nov-2012
02:54
x86
Taskschd.dll
6.0.6002.22990
352,768
30-Nov-2012
02:54
x86
Taskeng.exe
6.0.6002.22990
171,520
30-Nov-2012
01:28
x86
Taskeng.mof
Not applicable
2,254
09-Sep-2011
11:42
Not applicable
Collapse this imageExpand this image
For all supported IA-64-based versions of Windows Server 2008
Collapse this imageExpand this image
Collapse this tableExpand this table
File name
File version
File size
Date
Time
Platform
Hashcleanup.exe
6.0.6002.22990
20,480
30-Nov-2012
01:07
IA-64
Taskcomp.dll
6.0.6002.22990
807,936
30-Nov-2012
02:19
IA-64
Taskschd.dll
6.0.6002.22990
1,257,984
30-Nov-2012
02:19
IA-64
Taskeng.exe
6.0.6002.22990
523,264
30-Nov-2012
01:08
IA-64
Taskeng.mof
Not applicable
2,254
15-Mar-2011
06:01
Not applicable
Schedsvc.dll
6.0.6002.22990
1,418,240
30-Nov-2012
02:18
IA-64
Schedsvc.mof
Not applicable
2,250
15-Mar-2011
06:01
Not applicable
Wmicmiplugin.dll
6.0.6002.22990
986,624
30-Nov-2012
02:19
IA-64
Schedsvc.mof
Not applicable
2,250
09-Sep-2011
11:42
Not applicable
Taskcomp.dll
6.0.6002.22990
270,848
30-Nov-2012
02:54
x86
Taskschd.dll
6.0.6002.22990
352,768
30-Nov-2012
02:54
x86
Taskeng.exe
6.0.6002.22990
171,520
30-Nov-2012
01:28
x86
Taskeng.mof
Not applicable
2,254
09-Sep-2011
11:42
Not applicable
Collapse this imageExpand this image
Windows 7 and Windows Server 2008 R2 file information notes
Important Windows 7 hotfixes and Windows Server 2008 R2 hotfixes are included in the same packages. However, hotfixes on the Hotfix Request page are listed under both operating systems. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 7/Windows Server 2008 R2" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.
The files that apply to a specific product, SR_Level (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:
Collapse this tableExpand this table
Version
Product
Milestone
Service branch
6.1.760
0.21xxx
Windows 7 and Windows Server 2008 R2
RTM
LDR
6.1.760
1.22xxx
Windows 7 and Windows Server 2008 R2
SP1
LDR
The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows 7 and for Windows Server 2008 R2" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintaining the state of the updated component. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x86-based versions of Windows 7
Collapse this imageExpand this image
Collapse this tableExpand this table
File name
File version
File size
Date
Time
Platform
Hashcleanup.exe
6.1.7600.21386
9,728
30-Nov-2012
03:04
x86
Taskcomp.dll
6.1.7600.21386
304,640
30-Nov-2012
04:51
x86
Taskcomp.dll
6.1.7601.22177
305,152
30-Nov-2012
05:04
x86
Taskschd.dll
6.1.7600.21386
505,856
30-Nov-2012
04:51
x86
Taskschd.dll
6.1.7601.22177
506,880
30-Nov-2012
05:04
x86
Taskeng.exe
6.1.7600.21386
192,000
30-Nov-2012
03:04
x86
Taskeng.exe
6.1.7601.22177
192,512
30-Nov-2012
04:59
x86
D61d61c8-d73a-4eee-8cdd-f6f9786b7124.xml
Not applicable
3,188
22-Jul-2009
23:21
Not applicable
Schedsvc.dll
6.1.7600.21386
749,056
30-Nov-2012
04:50
x86
Schedsvc.mof
Not applicable
2,684
22-Jul-2009
23:21
Not applicable
D61d61c8-d73a-4eee-8cdd-f6f9786b7124.xml
Not applicable
3,188
10-Jun-2009
21:37
Not applicable
Schedsvc.dll
6.1.7601.22177
751,104
30-Nov-2012
05:04
x86
Schedsvc.mof
Not applicable
2,684
10-Jun-2009
21:37
Not applicable
Wmicmiplugin.dll
6.1.7600.21386
351,232
30-Nov-2012
04:51
x86
Collapse this imageExpand this image
For all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
Collapse this imageExpand this image
Collapse this tableExpand this table
File name
File version
File size
Date
Time
Platform
Hashcleanup.exe
6.1.7600.21386
10,240
30-Nov-2012
03:39
x64
Taskcomp.dll
6.1.7600.21386
473,600
30-Nov-2012
05:43
x64
Taskcomp.dll
6.1.7601.22177
474,112
30-Nov-2012
05:55
x64
Taskschd.dll
6.1.7600.21386
1,198,080
30-Nov-2012
05:43
x64
Taskschd.dll
6.1.7601.22177
1,198,080
30-Nov-2012
05:55
x64
Taskeng.exe
6.1.7600.21386
464,384
30-Nov-2012
03:40
x64
Taskeng.exe
6.1.7601.22177
465,408
30-Nov-2012
05:50
x64
D61d61c8-d73a-4eee-8cdd-f6f9786b7124.xml
Not applicable
3,188
22-Jul-2009
23:34
Not applicable
Schedsvc.dll
6.1.7600.21386
1,114,624
30-Nov-2012
05:42
x64
Schedsvc.mof
Not applicable
2,684
22-Jul-2009
23:34
Not applicable
D61d61c8-d73a-4eee-8cdd-f6f9786b7124.xml
Not applicable
3,188
10-Jun-2009
20:57
Not applicable
Schedsvc.dll
6.1.7601.22177
1,110,528
30-Nov-2012
05:55
x64
Schedsvc.mof
Not applicable
2,684
10-Jun-2009
20:57
Not applicable
Wmicmiplugin.dll
6.1.7600.21386
525,312
30-Nov-2012
05:43
x64
Schedsvc.mof
Not applicable
2,684
22-Jul-2009
23:21
Not applicable
Schedsvc.mof
Not applicable
2,684
13-Nov-2010
00:00
Not applicable
Taskcomp.dll
6.1.7600.21386
304,640
30-Nov-2012
04:51
x86
Taskcomp.dll
6.1.7601.22177
305,152
30-Nov-2012
05:04
x86
Taskschd.dll
6.1.7600.21386
505,856
30-Nov-2012
04:51
x86
Taskschd.dll
6.1.7601.22177
506,880
30-Nov-2012
05:04
x86
Taskeng.exe
6.1.7600.21386
192,000
30-Nov-2012
03:04
x86
Taskeng.exe
6.1.7601.22177
192,512
30-Nov-2012
04:59
x86
Wmicmiplugin.dll
6.1.7600.21386
351,232
30-Nov-2012
04:51
x86
Collapse this imageExpand this image
For all supported IA-64-based versions of Windows Server 2008 R2