.png?width=100&auto=webp&quality=80&disable=upscale "Picture of John Savill")
.png?width=400&auto=webp&quality=80&disable=upscale "John Savill")
Sign up for the ITPro Today newsletter
Stay on top of the IT universe with commentary, news analysis, how-to's, and tips delivered to your inbox daily.
Why do programs scheduled to run using the Windows 2000 Scheduler stop running after 72 hours?
John Savill
October 30, 2001
1 Min Read
A. Win2K introduced a maximum running time of 72 hours for programs executed using the Scheduler. To remove or modify this timeframe, contact Microsoft and request the Q304288 fix, which consists of updated mstask.exe and mstask.dll files. After you apply these files, you can use a new registry entry to set the timeout period. To edit the registry, perform the following steps:
Start a registry editor (e.g., regedit.exe).
Navigate to HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesSchedule.
From the Edit menu, select New - DWORD value.
Enter a name of AtTaskMaxHours, and press Enter.
Double-click the new value, set the value to the number of hours (between 1 and 999, or set the value to 0 to disable a maximum time), and click OK.
Close the registry editor.
Restart the machine for the changes to take effect.
Microsoft plans to release this fix in Win2K Service Pack 3 (SP3).
About the Author
You May Also Like
.png?width=700&auto=webp&quality=80&disable=upscale)