This article describes an issue when you start a game that uses Microsoft Direct3D 9 in Windows 8.1, Windows RT 8.1, or Windows Server 2012 R2. A hotfix is available to resolve this issue. The hotfix has a prerequisite.

Symptoms

Assume that you start a game that uses Direct3D 9 on a computer that uses hybrid graphics and is running Windows RT 8.1, Windows 8.1, or Windows Server 2012 R2. Additionally, assume that the game runs on the discrete graphics processing unit (GPU). In this situation, this issue occurs. In addition, the cursor remains alive, and the audio still plays.

Note A computer that uses hybrid graphics has two GPUs. One is an integrated GPU that provides low power consumption, and the other is a discrete GPU that provides high graphics performance.

Resolution

To resolve this issue, install update rollup 2962409, or install the hotfix that is described in this article.

Update information

For more information about how to obtain update rollup 2962409, click the following article number to view the article in the Microsoft Knowledge Base:

2962409 Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2 update rollup: June 2014

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. 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, go to 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

To apply this hotfix, you must first install the update 2919355 on Windows 8.1, Windows RT 8.1, or Windows Server 2012 R2. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

2919355 Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2 Update April, 2014

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.

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 RT 8.1, Windows 8.1, and Windows Server 2012 R2 file information notesImportant Windows 8.1 hotfixes and Windows Server 2012 R2 hotfixes are included in the same packages. However, only "Windows 8.1" is listed on the Hotfix Request page. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 8.1" 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.3.960 0.17 xxx

    Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2

    RTM

    GDR

  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2" 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 Windows RT 8.1

File name

File version

File size

Date

Time

Platform

D3d9.dll

6.3.9600.17095

1,195,160

14-Apr-2014

05:27

Not applicable

For all supported x86-based versions of Windows 8.1

File name

File version

File size

Date

Time

Platform

D3d9.dll

6.3.9600.17095

1,797,896

14-Apr-2014

08:08

x86

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

File name

File version

File size

Date

Time

Platform

D3d9.dll

6.3.9600.17095

2,125,344

14-Apr-2014

09:37

x64


Status

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

More Information

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

824684 Description of the standard terminology that is used to describe Microsoft software updates

Additional file information for Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2

Additional files for Windows RT 8.1

File property

Value

File name

Arm_d69925780ca5ae3f58b2ccea1822a39c_31bf3856ad364e35_6.3.9600.17095_none_1e6c94d2959e815b.manifest

File version

Not applicable

File size

705

Date (UTC)

17-Apr-2014

Time (UTC)

21:40

Platform

Not applicable

File name

Arm_microsoft-windows-directx-direct3d9_31bf3856ad364e35_6.3.9600.17095_none_56e5b7687c644171.manifest

File version

Not applicable

File size

9,882

Date (UTC)

14-Apr-2014

Time (UTC)

05:41

Platform

Not applicable

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

File property

Value

File name

X86_5c491eb084f67f39cdef28606316f481_31bf3856ad364e35_6.3.9600.17095_none_5b12ef816d8d8f50.manifest

File version

Not applicable

File size

705

Date (UTC)

17-Apr-2014

Time (UTC)

20:38

Platform

Not applicable

File name

X86_microsoft-windows-directx-direct3d9_31bf3856ad364e35_6.3.9600.17095_none_56e345107c6722ab.manifest

File version

Not applicable

File size

10,759

Date (UTC)

14-Apr-2014

Time (UTC)

08:34

Platform

Not applicable

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

File property

Value

File name

Amd64_5c491eb084f67f39cdef28606316f481_31bf3856ad364e35_6.3.9600.17095_none_b7318b0525eb0086.manifest

File version

Not applicable

File size

707

Date (UTC)

17-Apr-2014

Time (UTC)

22:18

Platform

Not applicable

File name

Amd64_7822f9ee4fe7646e56813dd6c61d51c0_31bf3856ad364e35_6.3.9600.17095_none_0fe1beca6b3140a2.manifest

File version

Not applicable

File size

709

Date (UTC)

17-Apr-2014

Time (UTC)

22:18

Platform

Not applicable

File name

Amd64_microsoft-windows-directx-direct3d9_31bf3856ad364e35_6.3.9600.17095_none_b301e09434c493e1.manifest

File version

Not applicable

File size

10,764

Date (UTC)

17-Apr-2014

Time (UTC)

22:18

Platform

Not applicable

File name

X86_microsoft-windows-directx-direct3d9_31bf3856ad364e35_6.3.9600.17095_none_56e345107c6722ab.manifest

File version

Not applicable

File size

10,759

Date (UTC)

14-Apr-2014

Time (UTC)

08:34

Platform

Not applicable


Need more help?

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

Was this information helpful?

What affected your experience?

Thank you for your feedback!

×