230

I have a Windows Server 2008 with scheduled tasks running, mainly .bat files calling PHP files. I have 2 users on the server, one Admin and the other is a Standard user.

I used the Standard User to clear the history log in the Task Scheduler History tab using the Event Viewer. Now it won't record any history anymore. All of the scheduled tasks no longer have history in the History tab. However, the Last Run Result returns 0x0 and the schedulers are working fine.
Please advise.

numaroth
  • 1,295
  • 4
  • 25
  • 36
martti d
  • 2,552
  • 2
  • 17
  • 20
  • If you keep coming back to this answer after each Windows update disables history, consider [upvoting this issue in the Windows Feedback app](https://aka.ms/AA5ic2y) – Carl Walsh Jul 03 '19 at 01:10

8 Answers8

417

Step 1: Open an elevated Task Scheduler (ie. right-click on the Task Scheduler icon and choose Run as administrator)

Step 2: In the Actions pane (right pane, not the actions tab), click Enable All Tasks History

That's it. Not sure why this isn't on by default, but it isn't.

B T
  • 57,525
  • 34
  • 189
  • 207
Brian Clark
  • 4,366
  • 1
  • 16
  • 4
  • 2
    I have Windows Server 2008 Standard, and there is no "Actions pane, click Enable All Tasks History". There are no histories for any running task, even MS scheduled system tasks. – Logman May 14 '14 at 12:13
  • 15
    Open Task Scheduler. In the left pane, right click Task Scheduler (Local), then click Enable All Task History. – billvsd Jun 21 '14 at 22:04
  • 3
    My History was recently 'disabled' - not by me - maybe by a Win 10 update? Of course I only found out when I actually wanted to see the History for a Task. :( – maxhugen Apr 27 '16 at 04:31
  • Brian Clark: Could you please update your answer as per billvsd's comment? On Windows 2008 `Enable All Tasks History` is not in the Actions pane, but rather you have to right-click in the top-left `Task Scheduler` node, and it's in the context menu under that. – HerrimanCoder Jul 28 '16 at 13:05
  • This is quite possibly one of the easiest fixes, and I don't know why it's disabled by default. – user208145 Sep 30 '16 at 09:06
  • 6
    very useful info. one question: is there any overhead on the system after enabling all tasks history ? – armen Aug 09 '17 at 16:03
  • 2
    There doesn't seem to be a way to enable history on one task, just a global flag. As Jeremy's answer points out, the history is a view over the Windows Event Log, so history is all-or-nothing. – Carl Walsh Mar 24 '18 at 16:21
  • In Windows Server 2016 if the Actions Pane is not visible, click on the "Show/Hide Action Pane" button under the menu bar in the top left corner. – Marianna S. Dec 13 '18 at 22:38
20

I have another possible answer for those wondering why event log entries are not showing up in the History tab of Task Scheduler for certain tasks, even though All Task History is enabled, the events for those tasks are viewable in the Event Log, and all other tasks show history just fine. In my case, I had created 13 new tasks. For 5 of them, events showed fine under History, but for the other 8, the History tab was completely blank. I even verified these tasks were enabled for history individually (and logging events) using Mick Wood's post about using the Event Viewer.

Then it hit me. I suddenly realized what all 8 had in common that the other 5 did not. They all had an ampersand (&) character in the event name. I created them by exporting the first task I created, "Sync E to N", renaming the exported file name, editing the XML contents, and then importing the new task. Windows Explorer happily let me rename the task, for example, to "Sync C to N & T", and Task Scheduler happily let me import it. However, with that pesky "&" in the name, it could not retrieve its history from the event log. When I deleted the original event, renamed the xml file to "Sync C to N and T", and imported it, voila, there were all of the log entries in the History tab in Task Scheduler.

  • 2
    I have the same problem--some tasks with history, some without. However the & character doesn't seem to be the problem.... Solution: Searched the actual event log and it appears that the event log is purged after a certain number of records. The history I was looking for is already purged. – Jeff Mar 29 '16 at 01:39
  • Cheers Jeremy you've saved me a lot of anguish – ryansin Feb 28 '20 at 14:19
19

The adjustment in the Task Scheduler app actually just controls the enabled state of a certain event log, so you can equivalently adjust the Task Scheduler "history" mode via the Windows command line:

wevtutil set-log Microsoft-Windows-TaskScheduler/Operational /enabled:true

To check the current state:

wevtutil get-log Microsoft-Windows-TaskScheduler/Operational

For the keystroke-averse, here are the slightly abbreviated versions of the above:

wevtutil sl Microsoft-Windows-TaskScheduler/Operational /e:true
wevtutil gl Microsoft-Windows-TaskScheduler/Operational
Glenn Slayden
  • 17,543
  • 3
  • 114
  • 108
  • 1
    Can you comment on the `retention: false` and `autoBackup: false` and `publishing: ` lines? I don't see any explanation for these lines. Perhaps you can add to your answer what each of the lines of the current state mean. – Jon Grah Jul 05 '18 at 20:32
  • @JonGrah Sorry, no idea what you're talking about. The words you've mentioned don't appear in my answer. – Glenn Slayden Jul 06 '18 at 00:22
  • I apologize. I should have included a screenshot: https://www.screencast.com/t/FY6u6v2A . Hope that clarifies what I am asking about `retention: false` and `autoBackup: false` and `publishing: lines`? – Jon Grah Jul 07 '18 at 03:26
  • @JonGrah Ok thanks for the clarification. I haven't noticed that before. Hopefully some else will chime in--or you could post a new question... – Glenn Slayden Jul 07 '18 at 07:00
  • 1
    The 'retention' and 'autobackup' are related to the eventvwr, and what eventvwr does do with the logs. (i.e. EVENTVWR.EXE /l:%SystemRoot%\System32\Winevt\Logs\Microsoft-Windows-TaskScheduler%4Operational.evtx ) – Luuk May 18 '19 at 08:35
  • What is operational here? – Shashwat Kumar May 18 '21 at 05:04
13

I think the confusion is that on my server I had to right click the Task Scheduler Library on left hand side and right click to get the option to enable or disable all tasks history.

Hope this helps

Jim Wallis
  • 131
  • 1
  • 2
6

Here is where I found it on a Windows 2008R2 server. Elevated Task Scheduler Click on "Task Scheduler Library" It appears as an option on the right hand "Actions" panel.

enter image description here

Daniel Williams
  • 8,912
  • 15
  • 68
  • 107
4

This may help others where there is no option to Enable/Disable the history anywhere in Task Scheduler.

Open Event Viewer (either in Computer Management or Admin Tools > Event Viewer).

In Event Viewer make sure the Preview Pane is showing (View > Preview Pane should be ticked)

In the left hand pane expand Application and Service Logs then Microsoft, Windows, TaskScheduler and then select Operational.

You should have Actions showing in the preview pane with two sections - Operational and below that Event nnn, TaskScheduler. One of the items listed in the Operational section should be Properties. Click this item and the Enable Logging option is on the General tab.

My problem was that the maximum log size had been reached and even though the overwrite old events option was selected it wasn't logging new events. I suspect that might have been a permissions issue but I changed it to Archive when full and all is now working again.

Hope this helps someone else out there. If you don't have the options I've mentioned above I'm sorry, but I don't know where you should look.

Mick Woods
  • 41
  • 4
  • Though my problem was an "&" in the job name (Jeremy's answer), yours got +1 too, for giving specific navigation in EventVwr, so we could see the PRIOR history. – Doug_Ivison Jun 15 '16 at 20:20
3

Win 8.1 Pro

Brian Clark's answer above worked for me, but I'm posting here for those who may have to follow a slightly different sequence as I did.

When I ran Control Panel > Administrative Tools > Right Click Task Scheduler - 'Run as Administrator', I found the Actions pane to already contain the following action:

Disable All Tasks History

So my machine already had History enabled. But my machine needed to disable history first, then go back and 'Enable All Tasks History'. After that, my History showed up and I received no more errors. I'm assuming that action performed some type of initialization or setup that was never done properly from all the way back to OS installation.

I will also add that I had to exit Task Scheduler and reenter it before I could toggle the History Enable/Disable setting back and forth.

Alan
  • 1,587
  • 3
  • 23
  • 43
1

As noted earlier, there is an option to turn on or off History provided you open up task manager under the elevated "Administrator" mode (right click on the Task Scheduler program/shortcut and choose "Run As Administrator"). Then under "Tasks" is your spot to stop or start History.

Adam Michalik
  • 9,678
  • 13
  • 71
  • 102
Chris Raisin
  • 384
  • 3
  • 7