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: Oldest
  1. Anonymous
    2015-02-14T20:24:18+00:00

    I can only tell you that MY work around is to make sure the Arc Touch Mouse is

    flattened before I start a Miracast session. After it is established, I open the

    mouse and the resolution stays at full HD.

    __________________________________________________________________________________________________

    Barb

    No Barb, not in my experience.

    As soon as I reconnect my mouse (or any other BT device) the connection is lost, when I reconnect the MWDA I have the resolution problem.

    Even so when I use the MWDA in the correct 1920 resolution with BT ON and no device connected, as soon as I open the BT configuration screen the connection with the adapter is lost...

    We all use the same Surface Pro 3, second screen, MWDA and Arc touch BT mouse. Due to my interference our small company here in The Netherlands switched to this configuration. And everybody is blaming me now. This is a small problem in your eyes, but it is more then that over here!

    I have also contacted MS support in other ways. And probably that will not be our last step to take.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2015-02-14T21:09:02+00:00

    I can only tell you that MY work around is to make sure the Arc Touch Mouse is

    flattened before I start a Miracast session. After it is established, I open the

    mouse and the resolution stays at full HD.

    __________________________________________________________________________________________________

    Barb

    No Barb, not in my experience.

    As soon as I reconnect my mouse (or any other BT device) the connection is lost, when I reconnect the MWDA I have the resolution problem.

    Even so when I use the MWDA in the correct 1920 resolution with BT ON and no device connected, as soon as I open the BT configuration screen the connection with the adapter is lost...

    We all use the same Surface Pro 3, second screen, MWDA and Arc touch BT mouse. Due to my interference our small company here in The Netherlands switched to this configuration. And everybody is blaming me now. This is a small problem in your eyes, but it is more then that over here!

    I have also contacted MS support in other ways. And probably that will not be our last step to take.

    Besides the mouse, do you have any other BT devices paired, like mobile phones, etc.? (I will pass your experience on).

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2015-02-16T10:55:10+00:00

    Just to add to this thread.

    I have exactly the same issue and I'm in the UK. I don't have the option to rollback my driver so as has been suggested this appears to be a problem outside of the US.

    I have the following Bluetooth devices attached (besides the pen):

    • Arc Touth Bluetooth Mouse
    • Ultrathin Bluetooth Mouse
    • Mobile Wedge Keyboard

    The Arc mouse was only added yesterday and I had the problem before this so that is not the issue. Hopefully it helps. If there is no workaroujnd by the end of the week my Microsoft Display Adapter will have to go back as it's effectively useless for me.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2015-02-16T11:40:15+00:00

    Paul,

    I'm going to post something that may or may not work, that I have not personally tried, and that I don't know what other impacts it might have on your system. Do the following at your own risk. The intent is to replace the Intel video driver.

    First, create a system restore point so you have something to go back to. Also be sure you have a local copy of the official Intel driver for SP3 from the Microsoft Surface site. The US site is https://www.microsoft.com/en-us/download/details.aspx?id=38826 - not sure if this will redirect for other countries or not. You should grab both the MSI zip and the non msi zip to be safe.

    Second, go to https://downloadcenter.intel.com/Detail_Desc.aspx?DwnldID=24594&lang=eng&ProdId=3721 and download the Intel generic driver for 64 bit

    Third, use the instructions from https://photographylife.com/microsoft-surface-pro-3-banding-and-calibration as a guide for installing - use the drivers above, not the ones he points to

    While the person who wrote of the instructions did this to solve a different issue, the instructions look to be quite good.

    Again, I can't promise the generic Intel driver will solve your problem or that this driver won't create other issues. If this doesn't work or if it creates other issues, you should have a restore point to go back to, plus you should have the "official" drivers you already downloaded.

    I really hope that if you do decide to try this that it solves the problem. PLEASE let us know.

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2015-03-05T22:51:44+00:00

    I tried this solution with the current intel drivers, as well as the version before that. Neither of these worked, and the problem remained.

    I have a US device and am unable to roll back my drivers. Please let us know as soon as Microsoft has a solution to this. I will be purchasing another product until then.

    Was this answer helpful?

    0 comments No comments