“Cast this video to the TV” sounds like one job. On a home network it can mean three very different jobs: mirror the Windows desktop, hand a local file to the television, or ask a streaming receiver to play content from an app. Choosing the wrong button is why many perfectly healthy TVs appear to be “not detected.”

Pick the method that matches the job

  • Miracast: mirrors or extends the Windows display. It is best for presentations, demonstrations, and showing arbitrary desktop applications.

  • DLNA / Cast to Device: sends a local media item to a compatible network player. The TV decodes the file, so container, video, audio, and subtitle support matter.

  • Google Cast: uses Chrome or a Cast-enabled application with Chromecast, Google TV Streamer, or a TV with Google Cast. It is not a synonym for DLNA or UPnP.

  • HDMI: the dependable fallback for DRM-protected video, games, unusual codecs, congested Wi-Fi, or a TV that implements none of the required wireless standards.

Before connecting: two minutes that save an hour

  • Confirm the television’s manual or settings explicitly names Miracast, screen mirroring, DLNA/media renderer, or Google Cast. “Smart TV” alone guarantees none of them.

  • Connect the PC and TV to the same trusted home network for DLNA and Google Cast. Guest Wi-Fi commonly isolates clients and prevents discovery.

  • Turn on Wi-Fi even when the PC also uses Ethernet; Microsoft specifically requires Wi-Fi for Miracast discovery.

  • Install current graphics, Wi-Fi, browser, TV firmware, and Windows updates, then restart both endpoints after an update.

  • Avoid enabling media sharing on public hotel, airport, or workplace networks.

Method 1: project Windows 11 with Miracast

Put the TV into its screen-mirroring or Miracast input first. On Windows 11, press Windows + K, select the display, and accept any confirmation shown on the TV. Windows negotiates a wireless display session; it does not upload your media library.

Choose mirror or second-screen behavior

  • Press Windows + P and choose Duplicate when the audience should see the same desktop.

  • Choose Extend when the television should become a second workspace; move the player window onto it.

  • Choose Second screen only when you want the laptop panel off during playback.

  • Open Windows + K again and select Disconnect when finished.

Method 2: send a local file with DLNA

DLNA is useful when you want the television to play a video without mirroring the desktop. On trusted private networks, Windows exposes media-streaming controls through the legacy Control Panel/Windows Media Player components. Enable streaming only if needed, allow the intended television, then right-click a compatible local media file and choose Cast to Device.

What happens across the network

  • Discovery typically uses UPnP mechanisms, while DLNA defines media interoperability. That does not make every UPnP device a compatible video renderer.

  • Windows acts as the controller/server and the TV becomes the renderer. The TV—not the PC’s desktop player—usually decides whether the file’s codecs and subtitles work.

  • A device appearing in the list proves discovery, not decoding compatibility. Test a common H.264/AAC MP4 before blaming the network.

  • Restrict access to the chosen TV. Media streaming can reveal indexed libraries and metadata to permitted devices on that LAN.

Method 3: cast from Chrome or a supported app

For Chromecast, Google TV Streamer, or a television with Google Cast, connect the receiver and PC to the same Wi-Fi network. In current Chrome, open More → Cast, save, and share → Cast, choose a device, then choose the source when necessary.

Tab, screen, or local file?

  • Cast tab is usually the best browser option and can route tab audio to the TV.

  • Cast screen mirrors more of the desktop, but Google notes that audio may remain on the computer.

  • For a local file, open it in a Chrome tab with Ctrl + O, then cast that tab if Chrome supports the format.

  • Prefer the Cast button inside a supported streaming site or application when available; the receiver can often fetch the stream directly and preserve quality more efficiently.

Why the TV appears but playback fails

  • Unsupported codec: remux or transcode the file to a combination listed in the TV manual; changing only the filename extension changes nothing.

  • Unsupported subtitles: external subtitle files and styled subtitle tracks are handled inconsistently; burn them into a viewing copy or use a compatible player.

  • DRM or protected video: screen capture/casting can be intentionally blocked. Use the service’s native TV app or an HDCP-compatible HDMI path.

  • VPN or virtual adapter: multicast discovery may be routed or filtered incorrectly. Pause the VPN only if policy permits, retest, then configure trusted-LAN access instead of leaving protection disabled.

  • Firewall/network profile: a Public profile blocks discovery more aggressively. Change it only when this is genuinely a trusted private LAN.

  • Client isolation: disable AP/guest isolation for the trusted home SSID or place both devices on the same permitted segment.

A practical discovery checklist

  • If Windows + K says Miracast is unsupported, use HDMI or a compatible adapter; DLNA support cannot repair missing Miracast hardware/driver capability.

  • If only Chrome cannot see the TV, verify it is a Google Cast receiver and both endpoints use the same Wi-Fi network.

  • If Cast to Device is empty, verify the TV advertises DLNA renderer support, network discovery is permitted, and media streaming allows that device.

  • If discovery works after reboot but later disappears, update router/TV firmware and inspect multicast filtering, VLAN boundaries, sleep modes, and Wi-Fi isolation.

  • If video stutters, reduce wireless contention, move closer to the access point, use a less congested 5 GHz/6 GHz link where supported, or wire the TV/PC.

  • Test one layer at a time: device discovery → connection → a known-compatible file → the original file.

Privacy and security boundaries

Wireless convenience expands the trust boundary into the room and local network. Confirm pairing prompts on the intended display, avoid exposing libraries to “all devices,” disconnect presentations when finished, and never share a sensitive desktop while notifications, password managers, or private tabs are visible.

Official references