A new instance of an MCML-based application starts when the ApplicationContext.ReturnToApplication method is called on a Windows Vista-based computer

Consider the following scenario:

• On a Windows Vista-based computer, you are running a Media Center Markup Language (MCML)-based application.
• You switch to another application. Therefore, the MCML-based application is in the backstack.
• The ApplicationContext.ReturnToApplication method is called.

In this scenario, you do not return to the original instance of the MCML-based application as expected. Instead, a new instance of the MCML-based application is started. Therefore, the application consumes extra resources when you restart it. If the application consumes lots of extra resources, this issue may affect system performance.

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: A hotfix is available to resolve this problem. After you apply this hotfix, the MCML-based application returns to its original instance when the ApplicationContext.ReturnToApplication method is called. Therefore, the application does not consume extra resources when you restart it.

Hotfix information

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

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, contact 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 Web site: 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

No prerequisites are required.

Restart requirement

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

Hotfix replacement information

This hotfix does not replace any other previously released hotfixes.

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

Windows Vista, x64-based versions

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.

When you run a Media Center extensibility application, and the ApplicationContext.ReturnToApplication method is called, you do not experience the problem that is described in the "Symptoms" section.

For more information, click the following article number to view the article in the Microsoft Knowledge Base:

For help with system performance issues in Windows Vista, visit the following Microsoft web page: