2
I just noticed that I can no longer start, stop, or restart the Task Scheduler service. When I open a Command window and attempt to stop the service in that fashion, I get an "permission denied" error, even when running as Administrator.
Is there a solution to this issue? I am running Vista SP1.
RHPT
Posted 2009-08-02T01:21:13.557
Reputation: 1 086
3
You should not disable Task Scheduler in Vista or Windows 7. Unlike XP, Vista actually uses Task Scheduler to perform system tasks.
The How-To Geek
Posted 2009-08-02T01:21:13.557
Reputation: 5 482
And what happens when the service malfunctions, and you have other user-critical tasks to complete prior to a Window restart? Microsoft cannot protect users from themselves with everything they could do to adversely alter the operation of Windows. – user66001 – 2015-08-24T03:52:20.083
3I had to down vote this because it doesn't fix the problem. – dlux – 2011-02-11T20:22:47.240
5
You can't stop the task scheduler. From Technet ...
The Task Scheduler service cannot be stopped or disabled by administrators using the Services Microsoft Management Console (MMC) snap-in user interface, unless special permissions are added to the administrator token.
There are some registry tweaks that claim to get it to stop, but your best bet is to use a tool. Security Explorer has a trial version that should work for you. If you want to prevent users from scheduling tasks, there is a way.
The best registry entry I found was below. But I don't have a Vista machine to test it on.
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Schedule]
"Start"=dword:00000002
JP Alioto
Posted 2009-08-02T01:21:13.557
Reputation: 6 278
I already have that Registry flag set with that value. Maybe I've never been able to disable it and never noticed before. – RHPT – 2009-08-02T17:24:41.260
1
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Schedule]
"Start"=dword:00000002
That is almost correct. Set it to 4 and reboot to disable. Some things will not work right such as updates (sometimes). Just re-enable when you go to run updates.
jatfq
Posted 2009-08-02T01:21:13.557
Reputation: 11
Please note that this is a crucial service and should most likely not be disabled. – Tamara Wijsman – 2011-11-01T13:45:41.297
1
Just found a way to a stop and then start, or restart, services that are launched under accounts like the SYSTEM account, causing even an Administrator-context cmd.exe process not to be able to manage them.
Download Sysinternal's Process Explorer.
Extract all files in ProcessExplorer.zip.
Right click on resulting procexp.exe and select 
Run as administrator; Click Continue button on resulting dialog.
Find svchost.exe in Process list, that has child process' of taskeng.exe.
Right click on the svchost.exe identified in step 4. and select Properties.
Select a Service; For the Task Scheduler click on Service Schedule line.
Click the Permissions button.
Add at least Write, if not Full control permissions to a group your user account belongs to, or just your user account, and click OK button.
With the permission-changed service line still highlighted in the list, happily Restart or Stop (and the Start again, noting the consequences of not doing so in other answers to this question) your permission-changed service.
user66001
Posted 2009-08-02T01:21:13.557
Reputation: 1 050
0
This is the behavior I'm seeing too.
There is a check box under the 'Services' tab of msconfig for 'Task Scheduler' though. Maybe that would be worth exploring?
opello
Posted 2009-08-02T01:21:13.557
Reputation: 696
if you uncheck this box - it just immediately rechecks itself – Simon – 2011-01-12T23:52:22.287
Please note that Microsoft has done this to prevent yo from stopping that service as it is crucial. – Tamara Wijsman – 2011-11-01T13:44:31.533