![]() ![]() Apply this hotfix only to systems that are experiencing the problem described in this article. However, this hotfix is intended to correct only the problem that is described in this article. Get the hotfix for Windows 8.1 or Windows Server 2012 R2A supported hotfix is available from Microsoft Support. ![]() Get the November 2014 update rollup for Windows RT 8.1, Windows 8.1, or Windows Server 2012 R2 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. Therefore, the update rollup takes longer to download. The update rollup is larger than the hotfix. We recommend that you use the update rollup. The update rollup fixes many other issues in addition to the issue that the hotfix fixes. To resolve this issue, we have released an update rollup and a hotfix for Windows 8.1 or Windows Server 2012 R2. For example, the local display is set to a resolution of 1280 x 768. In this scenario, the local display is set to the lower resolution that you set for the external display. For example, you set the external display to a resolution of 1280 x 768. You set the screen resolution for the external display to a lower resolution than the local display. For example, you set the local display to a resolution of 1366 x 768. You set the local display to the maximum supported resolution. In this scenario, the local display is set to the minimum supported screen resolution. Then, you restart the system.Īfter the computer shuts down, you restart it. Note You shut down the system completely. ![]() You leave Miracast connected and then shut down the system You set the screen resolution for the external display to a resolution that is not supported on the local display. You connect to Miracast and then wirelessly project to an external display by using extended display mode. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |