fatik911turbo15c102df
New member
- Joined
- Apr 9, 2026
- Messages
- 3
Bug report: MPG 491CQP QD-OLED — KVM does not wake sleeping host, and OSD source menu is inaccessible when no signal is present
Product: MSI MPG 491CQP QD-OLEDFirmware version: Scaler FW.030 (build 7710)Setup
- Host A: work laptop, connected via USB Type-C (DP Alt Mode + USB data + Power Delivery), one cable only.
- Host B: desktop PC, connected via DisplayPort/HDMI + USB Type-B upstream.
- Shared keyboard and mouse are plugged into the monitor's USB-A hub ports.
- KVM mode in OSD (G.I. → KVM) is set to Auto. Input Source auto scan is also enabled.
Steps to reproduce
- Laptop is connected via Type-C and working normally through the monitor.
- Put the laptop to sleep, then power on the desktop PC. The monitor auto-switches the video input and KVM/USB routing to the PC, as expected.
- Work on the PC using the shared keyboard and mouse.
- Turn the PC off completely.
- Try to wake the sleeping laptop using the keyboard connected through the monitor.
Expected behavior
Either the keyboard should still be able to send a wake signal to the laptop (e.g. the monitor should fall back to the Type-C input when the currently selected input loses signal and nothing else is live), or, at minimum, the user should be able to open the OSD and manually reassign the KVM/USB source to Type-C.Actual behavior
Nothing happens — the laptop does not wake, because keyboard input is still routed to the now-powered-off PC's USB-B side, not to the laptop's Type-C side. The only way to recover is to physically unplug and replug the USB-C cable between the laptop and the monitor. This forces a fresh USB device-attach event, which both re-binds the KVM/USB routing to Type-C and wakes the laptop.
More importantly: when the monitor is in this "no signal on any input" state, the OSD menu itself cannot be opened via the joystick to manually switch the KVM or Input Source. This leaves no software recovery path at all — only the physical cable reconnect works. A KVM feature that becomes unusable exactly in the situation it's meant to handle (one host asleep, one host off) defeats its own purpose.
Additional information
- This exact setup (same cables, same PC, same laptop, same Windows power settings) worked completely reliably on my previous monitor, an MSI MPG 346CQRF X24 — the keyboard always woke the laptop there with zero issues. Nothing on the laptop/OS side changed when I switched monitors, which points to this being a monitor-side (KVM controller firmware) issue specific to the QD-OLED line.
- The same symptom is independently reported by other MPG 321URX QD-OLED owners on the MSI forum ("My MSI MPG 321URX does not wake pc with KVM" — forum-en.msi.com, thread ID 398030), suggesting this is a shared firmware/KVM-controller regression across the QD-OLED KVM lineup, not an isolated unit defect.
- Already tried and ruled out on the OS side: updated the monitor to the latest firmware, Scaler FW.030 (build 7710), via MSI Center/Gaming Intelligence — the issue persists identically after this update; confirmed in Windows that the relevant USB hub is armed to wake the system (powercfg /devicequery wake_armed); disabled USB selective suspend; disabled Fast Startup. None of this changed the behavior, which confirms the fault is in the monitor's KVM/USB switching logic, not in Windows power management, and that it has not been addressed by the current latest firmware.
Requested fix
- Fix the "Auto" KVM mode so it doesn't get stuck on a now-powered-off host when both video inputs simultaneously report "No Signal" — it should fail over to whichever input last had an active USB device, or at least allow re-detection on the next USB activity.
- Make the OSD Input Source / KVM menu reachable via the joystick even when no video signal is present on any input, so users have a manual way to recover without physically reconnecting a cable.
Happy to provide additional logs, a screen recording, or test a beta firmware if that helps track this down.