Windows 10: How to fix Win+K projection not working.

Hi guysI can't seem to project my screen wirelessly from my main PC to my TV, windows CAN see my TV it sends the request to the TV and once i accept it it connects and immediately disconnects. Working fine on other notebooks around the house.Already checked drivers.I've already tried every single post on the community.Here's my specs. And i'm connecting to a LG OLED C1 TV.Im Using a LENOVO LEGION 5AMD Ryzen 7 5800H with Radeon Graphics 3.20 GHzWith a 3050 GPU Windows 11 Home Single Language.

:)

 

Win+K Shortcut not Working

I probably should have been more specific about what I did for the testing of RunTimeBroker's Analyze Wait Chain...

• Sort by Image and check all instances of RunTimeBroker. FWIW I was surprised by how many there were but just doing it again now indicates to me that this will be normal now; e.g. I can remember when there was one, so this step would not have been required.
• Once RunTimeBrokers are grouped at the top of the tab you can choose a different sort order. So, then sort by Threads descending.
• Go though each RunTimeBroker and do the Analyze Wait Chain... on them.

I suppose the only really essential parts of the procedure are 1 & 3. It's just that it seems more likely that a task which has the most threads will show a hung one.

I think this is going to be something else. It's strange that you can use Win+K but not Win+P and even stranger that you can't see any devices in your Win+K display. I suspect that's something more than
a hung UI transition but am not a Windows 10 programmer and don't know either how it is supposed to work or what diagnostics would be available to help show that it was working the way it was supposed to work.

For example, right now I am on my MWDA Second Screen Only. Win-K shows that state. However, "Second Screen Only" is apparently not giving us a complete picture of the real state of my video system.
There is nothing at all on my Tablet screen, so that is consistent with Second Screen Only but my real attached monitor is in its blank and static noise state. Heh. I just checked again. In fact, it is showing some windows that were previously open on the
tablet. So, it looks as if "Second Screen Only" should really be known as "Second
Screens Only" or "PC Screen Off"? Win-K and Win-P do not work on that other monitor, only on the MWDA one.

Bizarrely if I use either Win-K's Change Projection Mode (or Win-P) and switch to
Duplicate all three screens show the same thing and the Win+K etc. work on them all. It's really only bizarre though because in my case my tablet is oriented in Portrait mode and that mode is
then rendered on all three monitors (instead of seeing landscape on the two widescreen displays and something else on the tablet. So, continuing my list of misnamed features or incorrectly implemented functionality, it would seem that Duplicate doesn't really
mean "duplicate the primary screen" but "duplicate whatever might be rendered on the native screen even though it is not primary and currently blank"?

What do your users use their laptop screen for? Could it be switched to Duplicate? In any case, see if you can do something using Duplicate for a workaround.

The next part of the implementation that I think we will need to examine is what is the state of the machine's Network adapters both for the normal case and for the problem case. I suggest using PowerShell
for this

Get-NetConnectionProfile

Get-NetAdapter -IncludeHidden

For example, when I am using the MWDA the first command shows a Local Area Connection* being used (I assume somehow by the MWDA but don't know exactly how) and the second command can give further details
about it (and about anything else which may be related) E.g. I have two which seem identical except for their Name and that seems to me to be a good opportunity to have the other one "Up" when it should really be "Disconnected" so the one that we want to
be working does whatever it is supposed to do.

Then another thing that could be useful then is using the Network troubleshooter for Network adapters. E.g. if it listed the wrong "Wi-Fi Direct Virtual Adapter" you could hope that it would discover that
one should be disconnected. If it was showing the right one then I would have to change my hypothesis. ; )

HTH

Robert

---

 

Win+K Shortcut not Working

I am finally breaking my habit of using Win+P first and think I may have seen an instance of this; i.e. an immediate Win+K not being responsive. My scenario is with an MWDA which shows that the connection is broken, e.g. because my tablet is on battery
and was idle long enough that it decided to sleep. When this happened my first reaction (from dealing with the same symptom with my HDMI-2 for so long) was to press Win-P to find out what its state was. However, I soon realized that what I needed to
do first was get reconnected and that is what the Win-K could do to reduce the number of steps. (The tablet's screen is usable fortunately but I anticipate getting into a situation where it is not and that will be when I will need to use Narrator for
a workaround.)

So, here's an outline of what I will be doing when I see my MWDA waiting for a connection:

• Get out of the Lock screen (somehow)
• Optionally Login after that or just press Win-K right there in the Login prompt
• Click on the Win-K list item that represents the monitor
• Wait for the connection to switch my session. To my surprise it actually remembers that I want to be using Second Screen Only, so all I may need to do is move a few windows and I am back in business.

When step 2 failed I just used Win+P for its alternative. E.g. it did say PC Screen Only but now instead of just pressing End Enter (to select Second Screen Only) I need to press End,
Tab, Enter to get another try at starting the wireless display connection (otherwise it would be switching to my HDMI-2 which is still plugged in but not being used). BTW
Backtab only goes back to Second Screen Only; so no advantage to doing that; it would just be the same as the End to select the Second Screen Only option on the way to getting to the
Connect to a wireless display link at the bottom.



Does any of this match your scenario?

HTH

Robert

---

 

Win+K Shortcut not Working

I currently have a teacher's laptop in front of me that I have finally gotten to fail in the same manner.

The laptop is not connected to anything except the wireless display.

When I turn on Narrator and try win+k, it says "Windows K" and nothing else. The connect screen is not showing up on any other window, it is just simply not doing anything. The laptop is still connected to the network, it has not dropped it's connection.
The laptop was connected to the wireless display and suddenly, for no reason, dropped the connection to the display and then win+k would not work any more.

Win+Crtl+Shift+B makes the screen flash, but does not resolve the issue.