Symptoms

Consider the following scenarios.

Scenario 1

  • You connect to Miracast and then wirelessly project to an external display by using extended display mode.

  • You set the screen resolution for the external display to a resolution that is not supported on the local display.

  • You leave Miracast connected and then shut down the system

    Note You shut down the system completely. Then, you restart the system.

  • After the computer shuts down, you restart it.


In this scenario, the local display is set to the minimum supported screen resolution.

Scenario 2

  • You connect to Miracast and then wirelessly project to an external display by using extended display mode.

  • You set the local display to the maximum supported resolution. For example, you set the local display to a resolution of 1366 x 768.

  • You set the screen resolution for the external display to a lower resolution than the local display. For example, you set the external display to a resolution of 1280 x 768.

  • You leave Miracast connected and then shut down the system

    Note You shut down the system completely. Then, you restart the system.

  • After the computer shuts down, you restart it.


In this scenario, the local display is set to the lower resolution that you set for the external display. For example, the local display is set to a resolution of 1280 x 768.

Resolution

To resolve this issue, we have released an update rollup and a hotfix for Windows 8.1 or Windows Server 2012 R2.

The update rollup fixes many other issues in addition to the issue that the hotfix fixes. We recommend that you use the update rollup. The update rollup is larger than the hotfix. Therefore, the update rollup takes longer to download.

Get the update rollup for Windows 8.1 or Windows Server 2012 R2To resolve this issue, install the update rollup that is dated November 2014.

Get the November 2014 update rollup for Windows RT 8.1, Windows 8.1, or Windows Server 2012 R2

Get the hotfix for Windows 8.1 or Windows Server 2012 R2A supported hotfix is available from Microsoft Support. 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 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 update, you must first have update 2919355 installed on Windows 8.1 or Windows Server 2012 R2.

Restart requirementYou do not have to restart the computer after you apply this hotfix.

Hotfix replacement informationThis hotfix does not replace any previously released hotfix.

The English (United States) 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.1 and Windows Server 2012 R2 file information and notesImportant Windows 8.1 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 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 8.1 and Windows Server 2012 R2" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are extremely 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.1

File name

File version

File size

Date

Time

Platform

Win32k.ptxml

Not applicable

4,213

21-Aug-2013

23:39

Not applicable

Win32k.sys

6.3.9600.17381

3,469,312

20-Sep-2014

18:46

x86

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

File name

File version

File size

Date

Time

Platform

Win32k.ptxml

Not applicable

4,213

22-Aug-2013

06:44

Not applicable

Win32k.sys

6.3.9600.17381

4,182,016

20-Sep-2014

19:29

x64

Wow64_win32k.ptxml

Not applicable

4,213

21-Aug-2013

23:39

Not applicable

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

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

File name

Package_1_for_kb3002859~31bf3856ad364e35~x86~~6.3.1.0.mum

File version

Not applicable

File size

1,810

Date (UTC)

23-Sep-2014

Time (UTC)

12:56

File name

Package_2_for_kb3002859~31bf3856ad364e35~x86~~6.3.1.0.mum

File version

Not applicable

File size

1,824

Date (UTC)

23-Sep-2014

Time (UTC)

12:56

File name

Package_for_kb3002859_rtm_gm~31bf3856ad364e35~x86~~6.3.1.0.mum

File version

Not applicable

File size

1,681

Date (UTC)

23-Sep-2014

Time (UTC)

12:56

File name

Package_for_kb3002859_rtm~31bf3856ad364e35~x86~~6.3.1.0.mum

File version

Not applicable

File size

1,679

Date (UTC)

23-Sep-2014

Time (UTC)

12:56

File name

X86_2b4ebe27dcd0325333ca3d2976752a95_31bf3856ad364e35_6.3.9600.17381_none_fa5b2056b96577a6.manifest

File version

Not applicable

File size

694

Date (UTC)

23-Sep-2014

Time (UTC)

12:56

File name

X86_microsoft-windows-win32k_31bf3856ad364e35_6.3.9600.17381_none_4d90269bb6232c9a.manifest

File version

Not applicable

File size

125,471

Date (UTC)

20-Sep-2014

Time (UTC)

19:39

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

File name

Amd64_50324b40156ae4b2c42f48fb0d46ffa3_31bf3856ad364e35_6.3.9600.17381_none_8c5d76d93cbc9032.manifest

File version

Not applicable

File size

698

Date (UTC)

23-Sep-2014

Time (UTC)

13:00

File name

Amd64_a24c34b2c7ec545410d0a448a02bf976_31bf3856ad364e35_6.3.9600.17381_none_d0a5ee8302b7ef37.manifest

File version

Not applicable

File size

698

Date (UTC)

23-Sep-2014

Time (UTC)

13:00

File name

Amd64_microsoft-windows-win32k_31bf3856ad364e35_6.3.9600.17381_none_a9aec21f6e809dd0.manifest

File version

Not applicable

File size

125,475

Date (UTC)

20-Sep-2014

Time (UTC)

20:21

File name

Package_1_for_kb3002859~31bf3856ad364e35~amd64~~6.3.1.0.mum

File version

Not applicable

File size

1,820

Date (UTC)

23-Sep-2014

Time (UTC)

13:00

File name

Package_2_for_kb3002859~31bf3856ad364e35~amd64~~6.3.1.0.mum

File version

Not applicable

File size

2,284

Date (UTC)

23-Sep-2014

Time (UTC)

13:00

File name

Package_3_for_kb3002859~31bf3856ad364e35~amd64~~6.3.1.0.mum

File version

Not applicable

File size

2,281

Date (UTC)

23-Sep-2014

Time (UTC)

13:00

File name

Package_for_kb3002859_rtm_gm~31bf3856ad364e35~amd64~~6.3.1.0.mum

File version

Not applicable

File size

1,969

Date (UTC)

23-Sep-2014

Time (UTC)

13:00

File name

Package_for_kb3002859_rtm~31bf3856ad364e35~amd64~~6.3.1.0.mum

File version

Not applicable

File size

2,810

Date (UTC)

23-Sep-2014

Time (UTC)

13:00

File name

Wow64_microsoft-windows-win32k_31bf3856ad364e35_6.3.9600.17381_none_b4036c71a2e15fcb.manifest

File version

Not applicable

File size

124,742

Date (UTC)

20-Sep-2014

Time (UTC)

19:39


Status

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

More Information

Miracast is a wireless technology that the computer can use to project your screen to televisions, projectors, and streaming media players that also support Miracast. You can use this technology to share what you’re doing on your computer, present a slide show, or even play your favorite game on a larger screen.

References

Learn about 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?

What affected your experience?

Thank you for your feedback!

×