Share via

Miracast quick black screen

Anonymous
2017-10-20T10:02:36+00:00

Hello, I was connecting my PC to another PC using Miracast. It worked well until last few days, when I try to connect, only a quick black screen shows up on both devices and the PC that was connecting says "Couldn't connect" What is the problem? Thanks

Moved from: Windows / Windows 10 / PC Projection & Continuum

Windows for home | Windows 10 | Internet and connectivity

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

6 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2017-10-20T13:54:58+00:00

    Hi Eugene,

    This could be due to compatibility issue between the two devices due to a recent update or change on the machines. To isolate the concern, please provide the following information:

    • Have you made any recent changes on either device prior to the issue?
    • Which OS versions are these PCs running?
    • If possible, can you send a screenshot of the display showing on at least one of the machines?

    Regards.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  2. Anonymous
    2017-10-21T17:19:48+00:00

    On the other PC, it shows the Connect page, "[PCNAME] is ready for you to connect wirelessly"

    Diagnostics on that side are just as vague.  However, at least there are things there to look at.  E.g. in the Projections dialog (link at the bottom of the Win-k Connect dialog you showed) there are options about use of a PIN and being plugged in which definitely play a factor in what the other side can see.  Also, I don't know about W10 but on W8.1 RT (which is the only other PC I have to screen cast to) I have to remove the previous instances of the connection before I am successful with new ones.  That possibility would show up analogously in ms-settings:bluetooth (for other devices, specifically wireless displays...)  Yeah.  I'm sure it will be the same thing.  I just clicked on the MWDA item and the only option shown there is "Remove device".  I will have to remember that that is there the next time I see the symptom with my MWDA.  Thanks for making me find it.   ; )

    FYI

    Robert

    Was this answer helpful?

    0 comments
  3. Anonymous
    2017-10-21T16:56:58+00:00

    What is the problem?

    That's what lots of people want to know but the troubleshooters aren't helping and the diagnostic tools are not clear.

    For example, it definitely seems to be related to Wi-Fi but it doesn't show there.  Something shows there peek-a-boo fashion which eventually gets seen in both Network and Sharing Center and PowerShell Get-NetConnectionProfile but then not in netsh wlan sh ne mo=BSSID.  At one point I thought it looked as if we needed to have a real Wi-Fi connection up in order to avoid the "couldn't connect" symptom but now I'm not so sure.  In my case I'm seeing this symptom with a MWDA, so YMMV.

    FYI

    Robert Aldwinckle

    Was this answer helpful?

    0 comments
  4. Anonymous
    2017-10-21T15:54:46+00:00

    This could be due to a driver which needs to be updated. To resolve the issue, please check this support article: Update drivers in Windows 10. The said article contains steps on how you can properly update your machine’s driver.

    Don’t hesitate to give us updates on your query.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2017-10-20T22:22:43+00:00

    I haven't, it just suddenly stopped working.

    They're always updated on latest version of Windows, both running version 1703, build 15063.674

    This is what looks like on the main PC

    On the other PC, it shows the Connect page, "[PCNAME] is ready for you to connect wirelessly"

    Was this answer helpful?

    0 comments