Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

Event ID 1511 when you start a task that is created in Task Scheduler in Windows 8 or Windows Server 2012


View products that this article applies to.

Symptoms

This issue occurs when the task has the following settings:
  • Enable "Run whether user is logged on or not" in the general settings, and specify a user who does not have its user profile directory created yet on the local computer.
  • Enable "Repeat task every: xx" or "Stop task if it runs longer than: xx" in the triggers settings.
In this situation, when you run the task, a temporary user profile is created, and the specified user is logged on by using the temporary user profile. Additionally, event ID 1511 of User Profile Service that resembles the following is logged in the Application log:

↑ Back to the top


Hotfix information

Important Do not install a language pack after you install this hotfix. If you do, the language-specific changes in the hotfix will not be applied, and you will have to reinstall the hotfix. For more information, see Add language packs to Windows.

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.


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.
File 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:

    VersionProductMilestoneService branch
    6.2.920 0.21xxxWindows 8 and Windows Server 2012RTMLDR
  • 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 nameFile versionFile sizeDateTimePlatform
D61d61c8-d73a-4eee-8cdd-f6f9786b7124.xmlNot applicable3,18802-Jun-201214:32Not applicable
Schedsvc.dll6.2.9200.21397944,64019-Feb-201504:18x86
Schedsvc.mofNot applicable2,68402-Jun-201214:32Not applicable
Schedsvc.ptxmlNot applicable1,09925-Jul-201220:33Not applicable
For all supported x64-based versions of Windows 8 and of Windows Server 2012
File nameFile versionFile sizeDateTimePlatform
D61d61c8-d73a-4eee-8cdd-f6f9786b7124.xmlNot applicable3,18802-Jun-201214:33Not applicable
Schedsvc.dll6.2.9200.213971,284,60819-Feb-201505:24x64
Schedsvc.mofNot applicable2,68402-Jun-201214:33Not applicable
Schedsvc.ptxmlNot applicable1,09925-Jul-201220:30Not applicable
Schedsvc.mofNot applicable2,68402-Jun-201214:32Not applicable
Wow64_schedsvc.ptxmlNot applicable1,09925-Jul-201220:33Not applicable

Additional file information

Additional file information for Windows 8 and for Windows Server 2012
Additional files for all supported x86-based versions of Windows 8
File propertyValue
File nameX86_c81d86cd7039e68a8a30cf357c5912e8_31bf3856ad364e35_6.2.9200.21397_none_ffeac38cbd2e1893.manifest
File versionNot applicable
File size709
Date (UTC)19-Feb-2015
Time (UTC)23:45
PlatformNot applicable
File nameX86_microsoft-windows-taskscheduler-service_31bf3856ad364e35_6.2.9200.21397_none_2c2ddf81818c61b3.manifest
File versionNot applicable
File size132,039
Date (UTC)19-Feb-2015
Time (UTC)05:08
PlatformNot applicable
Additional files for all supported x64-based versions of Windows 8 and of Windows Server 2012
File propertyValue
File nameAmd64_1a29e8a18497051cd5f1d6b6a343a447_31bf3856ad364e35_6.2.9200.21397_none_47e986cbe215fb8c.manifest
File versionNot applicable
File size713
Date (UTC)19-Feb-2015
Time (UTC)23:45
PlatformNot applicable
File nameAmd64_554b34d8cc4d1a80a240de7f24486363_31bf3856ad364e35_6.2.9200.21397_none_0852eb47dae63b42.manifest
File versionNot applicable
File size1,068
Date (UTC)19-Feb-2015
Time (UTC)23:45
PlatformNot applicable
File nameAmd64_823a50cdb611c3e6d4d03b1870046ad5_31bf3856ad364e35_6.2.9200.21397_none_db4a8852e1d739fe.manifest
File versionNot applicable
File size713
Date (UTC)19-Feb-2015
Time (UTC)23:45
PlatformNot applicable
File nameAmd64_microsoft-windows-taskscheduler-service_31bf3856ad364e35_6.2.9200.21397_none_884c7b0539e9d2e9.manifest
File versionNot applicable
File size132,043
Date (UTC)19-Feb-2015
Time (UTC)07:09
PlatformNot applicable
File nameWow64_microsoft-windows-taskscheduler-service_31bf3856ad364e35_6.2.9200.21397_none_92a125576e4a94e4.manifest
File versionNot applicable
File size127,911
Date (UTC)19-Feb-2015
Time (UTC)04:39
PlatformNot applicable

↑ Back to the top


Status

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

↑ Back to the top


Cause

This issue occurs because the user name that is passed in from the Schedsvc.dll file is in the format of "domain name\username," and it does not pass the name check.

↑ Back to the top


References

See the terminology that Microsoft uses to describe software updates.

↑ Back to the top


Keywords: kbautohotfix, kbqfe, kbhotfixserver, kbfix, kbsurveynew, kbexpertiseinter, kb

↑ Back to the top

Article Info
Article ID : 3037318
Revision : 1
Created on : 1/7/2017
Published on : 4/24/2015
Exists online : False
Views : 157