Microsoft Wireless Display Adapter with Surface Pro 3 Resolution Problem

Anonymous
2015-01-23T23:46:25+00:00

My Surface Pro 3 is fully updated with the latest firmware and updates and the wireless display also has the latest updates.

When I have my bluetooth on and I connect to the wireless display adapter, my TV's max resolution that I can set is 1366 x 768 but when I turn my bluetooth off first and then connect to the wireless display adapter I can set my TV to 1920 x 1080.

It's kind of annoying to have to turn bluetooth off first before I connect to my tv. Is there something I can do to fix this issue?

Surface | Accessories | Wireless display adapter

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

142 answers

Sort by: Newest
  1. Anonymous
    2015-03-23T23:00:31+00:00

    This was through Microsoft's Surface Pro 3 chat support. In fact, I had two different representatives claim that the issue was fixed with the March update. Both tried to get me to refresh my system.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2015-03-23T22:46:46+00:00

    A Microsoft support representative claimed to me that the Bluetooth/Miracast issue has been resolved with the March 15 firmware update. However, I continue to be unable to use Bluetooth peripherals at the same time as Miracast. 

    Before I go through the hassle of refreshing my system or exchanging my SP3, I want to know if the firmware update has successfully resolved this problem for anyone. Any success stories out there?

    The issue is with the Intel video driver. That was NOT updated in March. The support rep was wrong. How did you contact support?

    Refresh/exchange will NOT fix this issue.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2015-03-23T22:32:28+00:00

    A Microsoft support representative claimed to me that the Bluetooth/Miracast issue has been resolved with the March 15 firmware update. However, I continue to be unable to use Bluetooth peripherals at the same time as Miracast. 

    Before I go through the hassle of refreshing my system or exchanging my SP3, I want to know if the firmware update has successfully resolved this problem for anyone. Any success stories out there?

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2015-03-21T11:23:55+00:00

    On Sat, 21 Mar 2015 05:15:05 +0000, Jehad Al-refaie wrote:

    >>I am using this mouse http://www.amazon.com/Microsoft-Sculpt-Bluetooth-Windows-Tablets/dp/B008OEHPPM/ref=sr_1_12?ie=UTF8&qid=1426914769&sr=8-12&keywords=microsoft+sculpt

    >>

    >>and it is showing the problem.

    >>

    >>

    >>

    >>the root cause here is latest SP3 windows update

    It is the Intel Display adapter that was released in January that causes this

    issue. If you have the ability to roll the display driver back in device manager

    (some people do and some don't for some reason) this may fix the issue.

    Microsoft knows about this problem but I doubt it will be fixed quickly. Could

    be several months. Or longer.

    __________________________________________________________________________________________________

    Barb

    Windows Entertainment and Connected Home MVP

    My Blog - http://digitalmediaphile.com/

    Please mark as answered if this answers your question

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2015-03-21T05:15:05+00:00

    Nicolas,

    What exact BT devices are you using?

    In fact, i'm sure that it's the arc touch mouse which causes the problem, not all bluetooth devices. And this mouse is very useful when i'm doing powerpoint presentations (i'm a teacher).

    Thanks 

    I am using this mouse http://www.amazon.com/Microsoft-Sculpt-Bluetooth-Windows-Tablets/dp/B008OEHPPM/ref=sr\_1\_12?ie=UTF8&qid=1426914769&sr=8-12&keywords=microsoft+sculpt

    and it is showing the problem.

    the root cause here is latest SP3 windows update

    Was this answer helpful?

    0 comments No comments