When you configure the Windows HotStart feature in Windows Vista to start a program directly from the system startup process, there is a long delay before the program starts. For example, when the computer is asleep, and you press the access button for the program on the front panel of the computer or on the infrared remote control, it may take as long as a minute for the program to start after the computer wakes up.

Back to the top

Service pack information

To resolve this problem, obtain the latest service pack for Windows Vista. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

Back to the top

Hotfix information

A supported hotfix is now 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. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next service pack that contains this hotfix.

To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:Note If additional issues occur or 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. To create a separate service request, visit the following Microsoft Web site:

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

Windows Vista, x86-based versions

File name	File version	File size	Date	Time	Platform
Schedsvc.dll	6.0.6000.20556	595,968	14-Mar-2007	01:58	x86
Schedsvc.mof	Not applicable	2,250	07-Jan-2007	05:34	Not applicable
Update.mum	Not applicable	1,793	14-Mar-2007	09:38	Not applicable
X86_4198600188c2915643c06519f0a66aa4_31bf3856ad364e35_6.0.6000.20556_none_7c3b356e976232a8.manifest	Not applicable	709	14-Mar-2007	09:38	Not applicable
X86_microsoft-windows-taskscheduler-service_31bf3856ad364e35_6.0.6000.20556_none_2d746b0ab31cb102.manifest	Not applicable	121,714	14-Mar-2007	09:40	Not applicable

Windows Vista, 64-bit versions

File name	File version	File size	Date	Time	Platform
Amd64_e6e898aa73cba4fff0671a825f1d1fb5_31bf3856ad364e35_6.0.6000.20556_none_3345186f334ed8a9.manifest	Not applicable	713	14-Mar-2007	09:38	Not applicable
Amd64_microsoft-windows-taskscheduler-service_31bf3856ad364e35_6.0.6000.20556_none_8993068e6b7a2238.manifest	Not applicable	121,756	14-Mar-2007	09:45	Not applicable
Schedsvc.dll	6.0.6000.20556	844,288	14-Mar-2007	03:15	x64
Schedsvc.mof	Not applicable	2,250	07-Jan-2007	05:34	Not applicable
Update.mum	Not applicable	1,793	14-Mar-2007	09:38	Not applicable

Back to the top

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in Windows Vista Service Pack 1.

Back to the top

For more information about how to configure Windows HotStart, visit the following Microsoft Web sites: For more information about how hotfix packages are named, click the following article number to view the article in the Microsoft Knowledge Base: For more information about the standard terminology that is used to describe Microsoft software updates, click the following article number to view the article in the Microsoft Knowledge Base:

Back to the top