Connect to a Wireless Display? One Line Says If You Can

The TV is across the room, the laptop is on your knees, and you would rather not run a cable between them. Reasonable. Windows can do it, and there is a way to find out in ten seconds whether yours can.

The trouble is that two completely different jobs share the same name, and most instructions online quietly mix them up. That is why the steps you found did not match your screen.

I want to separate them first, because once they are separate the rest is short.

Two different jobs, one name

Sending your screen to something else. Your laptop, projecting onto a TV, a projector or another PC. This is what most people mean.

Receiving somebody else's screen on this PC. Your PC acting as the display, with a phone or another laptop projecting onto it.

⛔ Only the second one needs anything installed, and the confusion starts right there. Guides for receiving get read by people who want to send. They go hunting for an optional feature they do not need.

Microsoft's wording draws the line cleanly: "If the device you're connecting to is another Windows PC, the Wireless display app (an optional feature in Windows) needs to be installed."

That sentence is about the machine at the far end, not yours.

Sending your screen: two keys

Hold the Windows key and press K. A panel slides in from the right. It lists what it can find.

Microsoft names that shortcut as the way to check Miracast support in the first place. If a list of nearby displays appears, you are set. Your PC can do this.

Pick the TV or adapter from the list. On most TVs a prompt appears asking you to accept. Then your desktop arrives.

⚡ The same panel is under Settings if you prefer clicking. Go to Settings, System, Display, open Multiple displays, and use Connect to a wireless display.

The one line that tells you whether your PC can do it at all

This is the check worth learning. It beats every other test, and it names which half is missing.

Open Start, type cmd, open Command Prompt, and run:

netsh wlan show driver

Scroll to a line reading Wireless Display Supported. That is your answer.

Ours, and measured on a laptop here: the machine I ran it on returned `Wireless Display Supported: Yes (Graphics Driver: Yes, Wi-Fi Driver: Yes)` on a MediaTek Wi-Fi 6 card.

⭐ The two values in brackets are why this beats everything else. Miracast needs both the graphics driver and the Wi-Fi driver to support it, and this line tells you which one is saying no.

A No against the graphics driver sends you to your GPU driver. A No against Wi-Fi sends you to the wireless adapter's.

⛔ A No against both usually means the hardware genuinely cannot do it, and no download changes that.

When Windows tells you to use a cable

You may not get a list at all. You get a message instead.

Documented by Microsoft on its wireless display page: "If your device doesn't support Miracast, you might see a message saying you need to connect an external display with a cable."

That message is honest. It is not a bug. It means the check in the section above would have come back No.

Microsoft's own way around it: "you'll need a Miracast adapter (sometimes called a dongle) that plugs into an HDMI port."

⭐ The adapter does the receiving, so the TV stops mattering. That is the useful part. A TV with no wireless display support of its own becomes usable. The dongle is the thing your PC talks to.

⚠️ Check what your TV already has before buying one. Many sets support a manufacturer's own casting instead of Miracast, and a streaming stick already plugged in may cover it.

⚡ And a cable is not a defeat. A wired second display has its own short list of causes when it refuses to appear, and it needs no radio at all.

Wi-Fi has to be on, even with an ethernet cable

Small thing, and it stops more of these than it should.

Microsoft lists it as a first check: "Make sure Wi-Fi is turned on."

Miracast talks directly between the two devices over Wi-Fi. It does not go through your router. Being on a network is not the point. The radio simply has to be switched on.

⚡ That is also why a desktop on a cable often cannot do this at all. No wireless card means nothing to talk with, whatever the graphics card can manage.

Receiving on this PC, and the feature that has to be added

Now the other direction. Your PC as the screen.

An adviser answered it on Microsoft's board in June 2026: "To install the Wireless Display feature, go to Settings > System > Optional Features > View Features > Search for Wireless Display, select it, and select to install."

They add a useful correction, because people go looking for a download that does not exist: "You don't need to install another application to use Miracast."

Once it is installed, Settings, System, Projecting to this PC becomes usable and you set who is allowed to project.

When Wireless Display is not in that list

Time for the awkward part. The standard advice fails for a great many people, and almost nobody writes that down.

On the same June 2026 thread, two owners came back after being told to add the optional feature.

One in July 2026: "There is no optional wireless display feature available for me to install." Another, days later: "this option is not available".

⛔ Neither got an answer. The thread ends there.

⚠️ What that pattern points at is hardware. The feature is offered where your machine can actually receive a projection. An absent entry is usually that same No. The netsh command would have printed it.

Ours, and marked as ours: run the command before you go hunting through Optional Features. If it says No, the missing entry in that list is the consequence rather than the problem.

⛔ One of the answers on that thread was machine-written and labeled as such. I did not use it, and I am saying so rather than leaving the exclusion silent.

When it connects, then drops

A connection that works and then dies has its own short list. Microsoft's order is sensible.

Microsoft, on drivers: "Make sure your device drivers are up to date and the latest firmware is installed for your wireless display, or adapter." Firmware on the dongle counts here and gets forgotten.

Then the simple one: "Restart your PC and the wireless display."

Then forget the pairing and rebuild it. Microsoft's route is to "Remove the wireless display, and then reconnect it", through Settings, Bluetooth & devices, Devices.

⚡ Distance and interference matter more than people expect, because this is a direct radio link rather than a network one.

A microwave, a crowded 2.4 GHz band or a wall in between will show up as stutter and dropouts. Not as a failure to connect.

⚠️ If the picture arrives but the sound stays on the laptop, that is a separate setting rather than a casting fault. Windows picks its output device on its own and the fix is one click in the volume panel.

Status: checked 23 August 2026. Microsoft documents Windows key plus K, the cable message on unsupported hardware, the HDMI adapter route, and the optional feature being needed only on the receiving PC. The netsh output was read off a laptop here. Nobody answered the missing optional feature on the thread, which this page states.

How do I connect my laptop to a TV wirelessly?

Press the Windows key and K, then pick the TV from the list that appears. If nothing is listed, run netsh wlan show driver in Command Prompt. Read the Wireless Display Supported line. It tells you whether the PC can do it, and which driver is the obstacle.

Do I need to install Miracast on Windows 11?

No. There is no Miracast download. Support comes from your graphics and Wi-Fi drivers, and it is either there or it is not. The Wireless Display optional feature is a separate thing, needed only when you want other devices to project onto this PC.

Why is there no Wireless Display in my optional features?

Usually because the machine cannot receive a projection, and Windows only offers the feature where the hardware supports it. Two owners reported exactly this on Microsoft's board in July 2026 and neither received an answer. Run netsh wlan show driver first, because that names the real obstacle.

Why does Windows say I need to connect a display with a cable?

That is Microsoft's own message for a device without Miracast support. It is accurate rather than a bug. A Miracast adapter plugged into an HDMI port gets you there instead, and it also makes the TV's own capabilities irrelevant.

The Short Version

• Sending your screen and receiving one are different jobs and only receiving needs anything installed.
• Windows key and K is the whole thing when it works. Try it before reading further.
• netsh wlan show driver prints Wireless Display Supported and names which driver is refusing.
• Wi-Fi has to be on even on a wired connection, because Miracast is a direct radio link.
• No support at all is solved by an HDMI Miracast adapter, which also bypasses what the TV can do.
• The Wireless display optional feature is for the PC being projected onto, not the one projecting.
• A missing entry in Optional Features had no confirmed fix on the thread read, and usually means hardware.
• Dropouts point at drivers, dongle firmware and the 2.4 GHz band before they point at Windows.

Where to Next

Press Windows and K first. If your TV appears, everything above was unnecessary and you are two clicks from done.

If nothing appears, run the netsh command and read one line. It turns an evening of guessing into a straight yes or no, and it names the driver worth updating.

If the picture works and the sound does not follow it, that is Windows choosing an output device. Nothing to do with casting.

And if your machine says No against only one of the two drivers, post which one below. I want that split on record, because almost nobody writes it down.