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

Does the phone have anything equivalent to Mouse Sonar (e.g. in Mouse Properties, Pointer Options) so you could use a Ctrl- key to give you some concentric circles to center a click action with?  Or the equivalent of a Pen visual pointer to allow you to see a pen tracking across the screen?

Guys - the clue is in the name - Project My Screen.

Who cares what happens on the phone screen the entire point of the app is to show the phone's screen on the computer.

It doesn't.

It used to.

1803 broke it.

There are no diagnostics.

It needs to be fixed.

I only know what the Connect app may cause. Let's forget the Connect application. I do not have a wireless display. I cannot use the Connect application.

Your PC would be your "wireless display"!  E.g. my Connect window goes on my VGA monitor when it is active.  Why can't you use the Connect application?  Let's investigate that tack.

BTW I have now realized how ancient the PmS app is.  I did a ProcMon trace of it starting up and saw that one of the things it would do is check for compatibility.  So I would imagine that installing it in W8 compatibility mode would probably be a good thing to try if you really wanted to pursue the PmS method of making this connection work.  But first I suggest you find out why a Wi-Fi connection would not be possible.  Apparently the old app is supposed to work via Wi-Fi anyway too.

C.f.

https://nokiapoweruser.com/project-my-screen-on-wi-fi-works-on-windows-10-mobile-build-14328-finally/

(via BING search for

    projectmyscreen compatibility

)

Note the checked check box "Allow input from a keyboard or mouse connected to this display".  This is starting to help me understand what a message about enabling Touch input may mean.  I never see any such UI prompts on my use of this tool because to my other Surface it is only another display it can Project to.  I would have to find some method of both making it think that it was connecting to a Touch screen and figure out how the Connect app could be made to think that its client knew that (i.e, that someone on the other side had used a UI element that indicated they were OK to have mouse or keyboard input--I'm assuming that's where the input would be coming from--but if you could hook up a mouse and keyboard combo to your phone (e.g. either Bluetooth or USB wireless) then that concept would be reversed.  Extending the idea to pen support would be phenomenal.  E.g. then I would be able to use my Surface Pro stylus instead of my Surface RT capacitive pen!

As a phone user which would you prefer, in relation to your screen projection, using a mouse and keyboard from your phone or from your PC?

BTW another hit on a completely different tack came up with the same search.  Have you looked at the Lumia Beamer app?  Looks like it would project something like the PmS UI to the remote display (e.g. to the PC's Connect window, wherever it happened to be placed.)   Hmm... looks like that one may be passe now too.  I tried what it said was the "new" URL and got a 404 saying that maybe it should have been an Azure redirect.  But there appears to be no knowledge of it where that led

https://azure.microsoft.com/en-ca/search/?q=lumiabeamer

OK BING knows.  It's long gone.

https://www.onmsft.com/news/microsoft-discontinues-lumia-beamer-app-windows-phone

HTH

Robert

Let's stay on the topic and forget "Connect " . It does not work  with my configuration. (display attached via DVI to a desktop PC )

And also :

"Project My Screen " app cannot be installed in any compatibility mode. See what  "Troubleshooting compatibility" says , when applied to ProjectMyScreenApp.msi : 

Moreover, https://www.microsoft.com/en-us/download/details.aspx?id=42536 under "System Requirements" clearly states that this app must work with Windows 10.

Therefore.... 1803 Update needs to be fixed. !!!!

forget "Connect " . It does not work  with my configuration. (display attached via DVI to a desktop PC )

[hardware wasn't specifically designed for wireless projection.  Version 10.0.17134.1]

Have you never been able to work around that message?  I have always had it, so it has been a fact of life for my experience with Connect / PmS.

However, I will admit that I can't test the new version because I am only running it as a Hyper-V VM and it will not allow me to make any changes to the Display configuration.  I still haven't figured out how to boot its .vhdx natively.  If I ever get that done I would be in a better position to test that case specifically.

Nevertheless, provided your PC can do Miracast, I still think that networking will play a bigger role in why this functionality is not working.  That ability is found under  netsh wlan sh d  (for   Wireless Display Supported: Yes (Graphics Driver: Yes, Wi-Fi Driver: Yes) )  and  Device Manager View Show hidden... (for Software Devices where I find my host name and an IPv6 Address for its Location: which I assume is the client when it was last working).  I suppose I should also admit that I do have an MWDA and have "cast" my PC screen to a smart TV, in case having done that makes a virtual Wi-Fi Direct connection any more probable.

"Project My Screen " app cannot be installed in any compatibility mode.

It would be the .exe not the .msi which would have to be treated that way.   ProcMon would show you if you had managed to achieve that with this approach.  Actually ProcMon would also help show if anything useful is being done with the USB tether and perhaps if there would be any diagnostics available using that device.

BTW I would agree that it should not be necessary for us users to try to find workarounds for functionality that we would like to have working or devise diagnostics which show why their (closed source undocumented) implementations aren't working but accept that that is a fact of life too.

HTH

Robert

Moreover, https://www.microsoft.com/en-us/download/details.aspx?id=42536 under "System Requirements" clearly states that this app must work with Windows 10.

I'm wondering if that is wishful thinking about compatibility.  Does that give you anything more recent than this?

PS>gi .\ProjectMyScreenApp.exe

Directory: C:\Program Files (x86)\ProjectMyScreenApp

Mode                LastWriteTime         Length Name

----                -------------         ------ ----

-a----       2002-02-01     17:02         516096 ProjectMyScreenApp.exe

So, I reinstalled the PmS app.  At first I thought there might be a discrepancy in the size of the .msi file but neither that nor (more importantly) the .exe had changed since I last installed it.  Like I said, it's ancient.