Skip to content
Sign in
Open Ticket
  • There are no suggestions because the search field is empty.

Miracast Windows + K menu does not detect a previously connected ScreenBeam receiver

This article applies to all ScreenBeam receivers.

Beginning March 24, 2026, we have received reports from some customers that their Windows devices cannot discover a previously connected ScreenBeam receiver. This behavior appears after recent Microsoft Tuesday security updates released between March 10 and March 17.

In these cases, when the user presses Windows + K, the intended ScreenBeam receiver does not appear in the list, while other nearby ScreenBeam receivers are still visible.

ScreenBeam version: All versions

Windows version: Most commonly Windows 11 24H2, but other versions may also be affected.

Troubleshooting observations:

  • Restarting Windows and/or the ScreenBeam receiver does not resolve the issue.

  • The affected Windows device can successfully connect to a different ScreenBeam receiver.

  • Other Windows devices can successfully connect to the affected ScreenBeam receiver.

Preliminary conclusion: A recent Windows update may have impacted Miracast functionality.

Temporary workaround

Remove the stored ScreenBeam receiver profile from the Windows “Bluetooth & devices” settings. Navigation may vary by Windows build:

  • Newer Windows builds: Settings > Bluetooth & devices > Devices > Wireless displays & docks

  • Older Windows builds: Control Panel > Hardware and Sound > Devices and Printers

To remove the profile, locate the ScreenBeam receiver by name, right‑click the icon, and select Remove. After removing the profile, the Windows + K menu should once again detect the ScreenBeam receiver.

For a permanent resolution, we strongly recommend opening a support ticket with Microsoft or contacting your Microsoft support representative regarding this issue.