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

Symptoms

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.

Cause

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:

http://support.microsoft.com/contactus/?ws=supportNote 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

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

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 8 and Windows Server 2012 file information and notes

Important Windows 8 hotfixes and Windows Server 2012 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 8/Windows Server 2012" 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, milestone (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:

    Version

    Product

    Milestone

    Service branch

    6.2.920 0.20xxx

    Windows RT, Windows 8, and Windows Server 2012

    RTM

    LDR

    6.2.920 0.21xxx

    Windows RT, Windows 8, and Windows Server 2012

    RTM

    LDR

  • GDR service branches contain only those fixes that are widely released to address widespread, critical issues. LDR service branches contain hotfixes in addition to widely released fixes.

  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information" section. MUM, MANIFEST, and the associated security catalog (.cat) files, are very important to maintain the state of the updated components. 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 8

File name

File version

File size

Date

Time

Platform

Taskhost.exe

6.2.9200.20569

53,760

27-Nov-2012

04:23

x86

Taskhostex.exe

6.2.9200.20652

53,760

02-Mar-2013

08:30

x86

Ubpm.dll

6.2.9200.21316

251,392

06-Dec-2014

05:41

x86

For all supported x64-based versions of Windows 8 and of Windows Server 2012

File name

File version

File size

Date

Time

Platform

Taskhost.exe

6.2.9200.20651

77,824

02-Mar-2013

02:40

x64

Taskhostex.exe

6.2.9200.21316

72,192

06-Dec-2014

06:43

x64

Ubpm.dll

6.2.9200.21316

320,000

06-Dec-2014

06:42

x64

Ubpm.dll

6.2.9200.21316

251,392

06-Dec-2014

05:41

x86

Additional file information

Additional file information for Windows 8 and Windows Server 2012

Additional files for all supported x86-based versions of Windows 8

File property

Value

File name

X86_09a23267f73d6c9ed094b449ec1b85d5_31bf3856ad364e35_6.2.9200.21316_none_e6e94bd7b8a0314b.manifest

File version

Not applicable

File size

696

Date (UTC)

06-Dec-2014

Time (UTC)

13:25

Platform

Not applicable

File name

X86_61ac7a149ecc09ae00385c191d630f92_31bf3856ad364e35_6.2.9200.21316_none_af400e5b663301f0.manifest

File version

Not applicable

File size

719

Date (UTC)

06-Dec-2014

Time (UTC)

13:25

Platform

Not applicable

File name

X86_microsoft-windows-taskhost_31bf3856ad364e35_6.2.9200.21316_none_25c0e85f449fc915.manifest

File version

Not applicable

File size

3,106

Date (UTC)

06-Dec-2014

Time (UTC)

13:28

Platform

Not applicable

File name

X86_microsoft-windows-u..roundprocessmanager_31bf3856ad364e35_6.2.9200.21316_none_63d25100dbb21b98.manifest

File version

Not applicable

File size

4,624

Date (UTC)

06-Dec-2014

Time (UTC)

06:35

Platform

Not applicable

Additional files for all supported x64-based versions of Windows 8 and of Windows Server 2012

File property

Value

File name

Amd64_4538a683d9dc2b0b7764b79b581b58ec_31bf3856ad364e35_6.2.9200.21316_none_a0aa4824cfeca0a2.manifest

File version

Not applicable

File size

700

Date (UTC)

06-Dec-2014

Time (UTC)

13:25

Platform

Not applicable

File name

Amd64_63d8032b8a393ee6e0507eeb25a26299_31bf3856ad364e35_6.2.9200.21316_none_b24ca97099407888.manifest

File version

Not applicable

File size

723

Date (UTC)

06-Dec-2014

Time (UTC)

13:25

Platform

Not applicable

File name

Amd64_6b39bc9efc881ac3fd84f914a4645307_31bf3856ad364e35_6.2.9200.21316_none_5a2e54aec0aa37e3.manifest

File version

Not applicable

File size

1,086

Date (UTC)

06-Dec-2014

Time (UTC)

13:25

Platform

Not applicable

File name

Amd64_microsoft-windows-taskhost_31bf3856ad364e35_6.2.9200.21316_none_81df83e2fcfd3a4b.manifest

File version

Not applicable

File size

3,110

Date (UTC)

06-Dec-2014

Time (UTC)

13:25

Platform

Not applicable

File name

Amd64_microsoft-windows-u..roundprocessmanager_31bf3856ad364e35_6.2.9200.21316_none_bff0ec84940f8cce.manifest

File version

Not applicable

File size

4,628

Date (UTC)

06-Dec-2014

Time (UTC)

08:30

Platform

Not applicable

File name

X86_microsoft-windows-u..roundprocessmanager_31bf3856ad364e35_6.2.9200.21316_none_63d25100dbb21b98.manifest

File version

Not applicable

File size

4,624

Date (UTC)

06-Dec-2014

Time (UTC)

06:35

Platform

Not applicable

Status

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

References

See the terminology that Microsoft uses to describe software updates.

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

Thank you for your feedback!

Thank you for your feedback! It sounds like it might be helpful to connect you to one of our Office support agents.

×