Unexpected Device Error While Casting From Windows 10?

If you see an “unexpected device error” when casting from Windows 10, the fix is usually to restart the Cast Sender service and check your network profile. This error typically appears when Windows can’t reach the Miracast or DLNA receiver due to a stalled service, a blocked port, or a misconfigured firewall.

What Causes the Unexpected Device Error

The error is a generic message that Windows 10 shows when the Cast feature (built into the Action Center) fails to connect to a wireless display or audio receiver. It is not a single failure point—it can come from several different layers:

Cast Sender service stopped: Windows uses the “Cast Sender” background service to discover and stream to devices. If it is disabled or hung, you get the error.
Network profile set to Public: Windows blocks device discovery and streaming on public networks by default. If your Wi‑Fi is marked as “Public,” casting will fail.
Firewall or antivirus blocking: Third‑party security software or Windows Defender Firewall can block the UDP ports used for discovery (1900 for SSDP) and streaming (7250–7259 for Miracast).
Driver or firmware mismatch: An outdated Wi‑Fi adapter driver or an old TV/Chromecast firmware can cause the handshake to fail.
Multiple active network adapters: Having both Ethernet and Wi‑Fi enabled can confuse the discovery protocol.

Quick Fix: Restart the Cast Sender Service

This is the most common fix and works in about half of the cases. Do this first before trying anything else.

Press Win + R, type services.msc, and press Enter.
Scroll down to Cast Sender (it may be listed as “Cast Sender Service” or “Windows Cast Sender”).
Right‑click it and select Restart. If the service is not running, click Start.
Set its startup type to Automatic (right‑click → Properties → Startup type).
Close the window and try casting again.

If the service won’t start, check that the “Windows Media Player Network Sharing Service” is also set to Automatic and running—Cast Sender depends on it for DLNA.

Check Your Network Profile and Ports

Windows 10 treats networks as either Private or Public. Casting is only allowed on Private networks unless you explicitly enable it.

Go to Settings → Network & Internet → Wi‑Fi (or Ethernet) and click your connected network.
Set the network profile to Private.
If you are on a work or school network, you may not be able to change this—ask your admin.

If that doesn’t help, check that your firewall is not blocking the required ports. Windows Defender Firewall normally creates rules for Cast Sender automatically, but third‑party firewalls often block them. Temporarily disable your third‑party firewall to test, then re‑enable it and add an exception for the Cast Sender service.

Update or Roll Back Your Wi‑Fi Driver

Miracast uses the Wi‑Fi adapter’s driver to create a direct peer‑to‑peer connection. A buggy or outdated driver is a frequent culprit.

Press Win + X and select Device Manager.
Expand Network adapters and find your Wi‑Fi adapter (e.g., Intel Wireless, Realtek, Qualcomm).
Right‑click it and select Update driver → Search automatically.
If that doesn’t find a new driver, go to your laptop manufacturer’s support site and download the latest driver for your exact model.
If the error started after a recent driver update, try Roll Back Driver instead.

After updating, restart your PC and try casting again.

Disable Other Network Adapters

When you have both Ethernet and Wi‑Fi active, Windows may try to discover devices on the wrong interface. This is especially common on laptops that are plugged into a dock.

Open Control Panel → Network and Sharing Center → Change adapter settings.
Right‑click the adapter you are not using (e.g., Ethernet if you are on Wi‑Fi) and select Disable.
Try casting again. If it works, you can re‑enable the other adapter.

Use the Wireless Display App Instead of Action Center

Windows 10 has two ways to cast: the quick action “Connect” tile and the standalone “Wireless Display” app. Sometimes the app works when the quick action fails.

Open the Start menu and type Wireless Display.
Launch the app—it will scan for available displays.
Select your TV or receiver and connect.

If the app also fails, the issue is likely at the hardware level (driver or device compatibility).

When Nothing Works: Check the Target Device

Sometimes the problem is not on your Windows 10 PC at all. The TV or streaming stick may have gone to sleep or lost its network connection.

Reboot the TV or streaming device (unplug for 30 seconds).
Make sure the target device is on the same Wi‑Fi network (or connected via Ethernet to the same router).
For Miracast, the TV must support Miracast—many older TVs do not. Check the TV’s manual for “Screen Mirroring” or “Miracast” support.
If you are casting to a Chromecast, the Google Home app may show a firmware update—install it.

If the target device is a second Windows 10 PC, ensure that the “Project to this PC” setting is enabled on the receiving PC (Settings → System → Projecting to this PC).

Frequently Asked Questions

Why does the error say “unexpected device error” instead of a specific code?

Windows uses this generic message when the Cast Sender service cannot complete a handshake with the receiver. It does not differentiate between a network timeout, a driver failure, or a device that refuses the connection—so you have to troubleshoot each layer.

Does this error happen with both Miracast and Chromecast?

Yes. The Cast feature in Windows 10 uses Miracast for wireless displays and DLNA for some smart TVs. Chromecast uses a different protocol (Google Cast), but the error can still appear if Windows cannot reach the Chromecast over the network.

Can I fix this by changing the Wi‑Fi band (2.4 GHz vs 5 GHz)?

Sometimes. If your router broadcasts both bands and your TV is on the 2.4 GHz band while your PC is on 5 GHz, they may not see each other. Connect both devices to the same band and try again.

Is there a way to cast without using the Action Center?

Yes. You can press Win + P and select “Connect to a wireless display.” This opens the same device picker but uses a different code path that sometimes bypasses the stuck service.

Will reinstalling the display driver help?

It can, but only if the issue is graphics‑related. The “unexpected device error” is more often a network or service issue. If you have an Intel or NVIDIA GPU, you can try reinstalling the graphics driver after checking the Cast Sender service.

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →