Lumia 950XL - Project My Screen not working after Win10 1803 Update - Black Screen

Anonymous
2018-05-17T12:08:56+00:00

I use my 950XL extensively for demos of my company's software because it's much better display than my iPhone and doesn't need additional apps to do it.

I updated my Win10 desktop today to 1803 and also my phone updated to .104 and the app no longer works.

When I open the app I get the message on the phone to ask if I want to share and I agree. The display on the desktop is black, but I can actually start applications on the phone by clicking inside the black window, so there obviously is a connection, just no display.

I was working perfectly, but not now.

As a workaround, is it possible to use continuum? I'm sure there used to be an option to display the phone's screen rather than a full desktop to the connected display but that appears to be no longer available

Thanks,

Chris

***Moved from: Mobile Devices / Microsoft Lumia and Nokia Lumia / Continuum / 900-series.***

Windows for home | Windows 10 | PC projection

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

120 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2018-05-31T21:06:50+00:00

    Ok, yes , the search tool is pathetic. I get some 50 hits, but none on PmS. But read what the first line says...

    Was this answer helpful?

    0 comments
  2. Anonymous
    2018-05-31T19:37:22+00:00

    There are no diagnostics.

    Maybe there are.  PmS was originally a Developer tool, so maybe in order to use it still you need to indicate that you are a Developer and opting for diagnostics and features available that way.

    Serendipity found this

    https://docs.microsoft.com/en-us/windows/uwp/get-started/enable-your-device-for-development

    So, see if it helps to turn on these two Developer options  (under Enable Device Portal and Device Discovery)

    • Turn on remote diagnostics over local area network connect
    • Make your device visible to USB connections and your local area network

    I may try these to see if they at least make any difference in a ProcMon trace.

    Good luck

    Robert

    Was this answer helpful?

    0 comments
  3. Anonymous
    2018-05-31T03:32:27+00:00

    Did you try  Win+F?   

    FWIW here is the closest hit that I could find on the production feedback app.   You can do better I'm sure.

    https://aka.ms/AA1fof7

    (in Apps  All Other Apps  search for

        1803  ProjectMyScreen.exe

    )

    The search in that tool is pathetic.  So who knows if anyone has actually reported this or not--undoubtedly not like this.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2018-05-31T00:35:07+00:00

    No, sorry, I'm not an insider.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2018-05-30T21:37:20+00:00

    Not an Insider?  If you can reproduce the problem on a preview version you could add your feedback with the Insider feedback tool.  Otherwise, I'm not sure what kind of traction you would get from a report on the production feedback side.  Press Win+F and find out.

    Here's one (top hit) which claims the problem started with 16299.  This thread is indicating the problem started with 17134.

    https://aka.ms/AA1eudf

    Was this answer helpful?

    0 comments