Exit code improvements for Task Scheduler event log in Windows 8 and Windows Server 2012

Applies to: Windows Server 2012 DatacenterWindows Server 2012 DatacenterWindows Server 2012 Essentials


Consider the following scenario:
  • You have a computer that is running Windows 8 or Windows Server 2012.
  • You run a batch file through Task Scheduler.
  • You check the Task Scheduler event log.
In this scenario, the Task Scheduler event log always reports success instead of the actual exit codes.


This issue occurs because the Last Run Result value in Task Scheduler is an HRESULT interpreted value.

How to obtain the hotfix

To resolve this issue, we have released a hotfix for Windows 8 and Windows Server 2012.

Note After you install this hotfix, the event log exit codes work exactly like the Task Scheduler exit codes do in Windows 8.1, Windows Server 2012 R2, Windows 7, and Windows 2008 R2.

Hotfix information for Windows 8 and Windows Server 2012

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 this specific problem.

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, submit a request to 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.


There is no prerequisite to apply this hotfix.

Registry information

To use the hotfix in this package, you do not have to make any changes to the registry.

Restart requirement

You may have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

More Information


Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.


See the terminology that Microsoft uses to describe software updates.