Meeting Room Screen Not Working: 7 Fast Fixes
The most common cause is simple: the screen is asleep, powered off, or on the wrong HDMI input rather than a real fault.
Check it with the display's own remote first, then reseat the HDMI cable at both ends. The fixes below run in order of how often we actually see them.
Work top to bottom - most common causes first
1. The screen is off, asleep, or on the wrong input
The display shows a 'No signal' message, a manufacturer logo, a home screen, or stays completely black with no backlight change when you try to start a call.
- 1Find the screen's own remote control (not the room touch panel) and press its power button to confirm the screen itself is switched on.
- 2Use the screen's remote to press the Source or Input button and cycle through each HDMI input until you see the meeting room touch console image or a vendor splash screen.
- 3If the screen normally switches input automatically over HDMI-CEC and has instead opened its built-in TV tuner, smart hub, or a connected streaming stick, manually select the HDMI port the room system is wired to.
- 4Wake the room system itself by tapping the touch console or, on camera-bar systems with presence detection, standing in front of the camera for a few seconds.
If the screen powers on and you can select every HDMI input with none of them showing anything, the fault is more likely a cable or the room system itself, not the display - move to the next step.
2. A video cable is loose, damaged, or unplugged
The correct input is selected (visible on the screen's own on-screen menu) but the picture stays black or shows 'No signal' - often starting straight after cleaners, an office move, or furniture being shifted.
- 1Unplug and firmly reseat the HDMI cable at both the screen end and the room system or wall plate end.
- 2If a spare HDMI cable is available, swap it in to rule out a damaged cable.
- 3Check any HDMI wall plate, extender, or booster box has power - these often run off their own small adapter that can come loose or fail.
- 4For long cable runs (over roughly 10 metres), confirm it's a certified active or fibre HDMI cable - passive cables that long are a common cause of intermittent signal loss.
If you've swapped the cable and reseated every connection and it's still blank, check whether this is a content-sharing issue rather than a display issue - see the next section.
3. Laptop content isn't appearing even though the room screen works
The meeting room touch panel and screen work fine for joining calls, but when you connect or share from a laptop nothing appears on the room screen.
- 1On the laptop, press Windows key + P (Windows) or open System Settings > Displays (Mac) and confirm it's set to extend or mirror, not 'PC screen only'.
- 2Check the room system has automatically switched to the HDMI content-share source - on Teams Rooms and Zoom Rooms this normally happens within a few seconds of a laptop being connected; if not, look for a prompt on the touch console to show the HDMI or cable input.
- 3Reseat the HDMI or USB-C cable at the table connection point - table boxes and cable cubbies take more physical wear than any other cable in the room.
- 4Try a different laptop if one is available, to rule out a laptop-side display driver or dock fault.
If content still won't share from any laptop, this usually means the room system's HDMI ingest isn't detecting a signal at all, rather than a fault with the screen - an IT admin should check the console.
4. The video system or room PC has frozen and needs a restart
The touch console is unresponsive, stuck on a loading spinner, showing a sign-in screen repeatedly, or the room system's desktop is visible but nothing responds to touch.
- 1Try a soft restart first: on Teams Rooms devices, use the touch console's settings or admin menu to restart the app (this may need the room's admin password).
- 2If that's not accessible, power-cycle the compute unit (mini PC, NUC, or codec) - turn it off, wait 30 seconds, then turn it back on. Power-cycling only the screen does not reset the room system.
- 3Allow 2-3 minutes for the system to fully boot and rejoin the network before assuming it's failed.
- 4Confirm the network cable to the room system is connected - a dropped network connection can leave Teams Rooms or Zoom Rooms stuck on a black or loading screen.
If the system won't complete a restart or keeps looping back to the same frozen state, this needs IT admin access to the device or its remote management portal (Teams admin centre or Zoom Rooms dashboard).
5. HDCP or an incompatible switcher is blocking the signal (IT admin)
The fault started right after a new HDMI switcher, extender, or matrix was installed, or after trying to pass protected streaming content through the room's HDMI input.
- 1IT admin: check whether any HDMI switch, extender, or splitter in the signal path has an HDCP (copy-protection) setting, and disable it. Microsoft Teams Rooms specifically does not support HDCP-protected HDMI input, and leaving it enabled on an upstream switch is a known cause of ingest failing.
- 2Avoid routing DRM-protected content, such as streaming services, through the room's HDMI-in - this can trip an HDCP handshake and drop the signal.
- 3Use the vendor-supplied ingest cable or adapter rather than a generic HDMI-to-USB-C adapter, which can fail the HDCP or resolution handshake.
- 4Check the HDMI ingest health status in the vendor's admin portal (Teams admin centre device health, or the room system's own diagnostics page) for an explicit ingest error.
If ingest still shows unhealthy after disabling HDCP and checking cabling, log a fault with the device manufacturer - this usually points to a firmware or hardware fault on the ingest module itself.
6. One of two screens isn't detected in a dual-screen room
One screen displays the meeting correctly, but the second stays black, shows the wrong content, or duplicates the first screen instead of showing a different layout.
- 1Check the resolution set on the primary display - some dual-screen systems, notably Logitech Rally, only activate the second HDMI output when the first is running at 1080p60 or lower, so a 4K primary display can silently disable the second port. Other systems drive 4K on both outputs, so check your model's documentation.
- 2Reseat the HDMI cable for the second screen specifically - on some systems it carries a lower-priority signal and is more sensitive to a poor connection.
- 3IT admin: open the room system's display settings, via its admin web page or touch console settings, and confirm dual-display or extended mode is enabled rather than single-display mode.
- 4Power-cycle both screens together, then the room system, so they renegotiate their display handshake in the correct order.
If the second screen still won't activate at any resolution, this is usually a room-system configuration limit rather than a cable fault - an IT admin should check the vendor's dual-display support matrix for that exact model.
7. A pending update or sleep setting is causing intermittent no-signal (IT admin)
The fault is intermittent - fine most of the day, but showing no signal first thing in the morning or after the room has sat empty, then resolving itself after a few minutes or a manual wake.
- 1IT admin: check the device for a pending firmware or OS update stuck mid-install - this can leave a room system in a partially-booted state that doesn't output video.
- 2Check the device's sleep or standby signal settings - some systems have an option controlling whether an active HDMI signal is sent while asleep; if it's disabled, screens with strict auto-input switching may not wake correctly.
- 3Schedule updates outside working hours and confirm the device has fully rebooted, not just the app, after any update completes.
- 4If the issue recurs on a predictable schedule, such as every Monday morning, report it to the manufacturer or your AV integrator as a pattern rather than a one-off.
If restarts and update checks don't stop the fault recurring, this points to a firmware bug or hardware wake fault that needs the manufacturer or your AV integrator's support team.
Vendor-specific quirks worth knowing
Microsoft Teams Rooms: Teams Rooms does not support HDCP-protected HDMI input. If a switcher, extender, or matrix upstream has HDCP enabled, HDMI ingest can fail outright - disable HDCP on any third-party switching hardware in the signal path.
Cisco (Webex Room / Room Kit): On some display models, Cisco's CEC wake command switches the TV on but leaves it on its native tuner or hospitality input instead of the HDMI port, showing 'No signal' until a call starts or content is shared, at which point it usually switches automatically.
Logitech (Rally / Rally Bar): In dual-display Rally rooms, the second HDMI output only activates if the primary display is running at 1080p60 or lower - the link between Rally's hubs carries either one 4K signal or two 1080p signals, never both. A primary display set to 4K can silently disable the second screen entirely; this is a documented resolution limit, not a fault.
Neat (Bar Pro / Board 50): These two models have a configurable 'HDMI sleep signal' setting under System Settings > Display (not available on the standard Bar or Board). If it's switched off to save power, the device sends no active signal at all while asleep - some auto-switching displays may then treat it as a disconnected source and sit on a different input when the room wakes.
When to stop and call an engineer
- ·The fault recurs on the same room after a reboot, cable swap, and input check have already fixed it once - a repeating fault usually means failing hardware, not user error.
- ·Any cabling, wall plate, or screen mount is visibly damaged, hanging loose, or the screen has moved on its bracket - this is a safety issue and should not be handled without proper access equipment and training.
- ·The room system's admin diagnostics report a confirmed hardware fault, such as an unhealthy HDMI ingest module or an offline camera or codec, rather than a cabling or settings issue.
- ·The device is still within its manufacturer or MAV warranty period - self-repair or third-party parts can void cover that a proper fault claim would otherwise use.
- ·In-ceiling or in-wall cabling needs re-terminating or re-routing - this requires access to structured cabling and should be done by whoever installed the system.
We support all five major vendors - Neat, HP Poly, Logitech, Yealink and Cisco - and it doesn't matter who installed the room. Tell us what you're seeing and an engineer will take it from here.