A refresh rate missing from display settings can reflect the limits of the complete connection route. The panel may support that rate through one input or at one resolution while a dock, adapter or host output cannot deliver the same combination. Identify the requested mode precisely before treating its absence as an operating-system error.
Write down the complete mode and connection
Record the display resolution, desired refresh rate, color depth and HDR state, together with the monitor's exact model and selected input. Include every intermediate device. A claim that a monitor supports a high refresh rate without a resolution and input is incomplete, and a cable's connector shape does not establish its supported signal capability.
Consult the monitor documentation for the relevant input and supported timing. Some modes depend on a particular menu setting, input version or supported compression path. Follow the product's documented configuration rather than enabling unfamiliar options at random. Check whether a firmware revision or variant changes the capabilities described in a general product-family page.
Review the host's simultaneous display limits and the dock's mode tables. A pair of monitors can share a bandwidth budget, and some combinations reduce the available rate even when each monitor works at a higher setting individually. USB data allocation and connection technology can also matter, so compare the exact two-display arrangement with the supported specification.
Separate an unsupported route from detection trouble
Test the monitor alone through a documented direct output when the hardware allows it. If the desired mode appears, reconnect the second display and then the dock as separate comparisons. Track what changes at each stage. This helps identify a route limitation without implying that the missing option proves a specific accessory is defective.
Use a suitable cable and adapter whose documented capabilities cover the intended mode. Avoid forcing custom timings as a first diagnostic step. An option that can be entered manually is not necessarily safe, stable or supported by the entire path, and a brief visible picture does not establish reliability during sleep, reconnect or sustained work.
If the documentation supports the exact combination but it remains unavailable, inspect the operating-system and graphics-driver information. Check for a recognized monitor model and vendor guidance about the route. Preserve working settings before an update, and make changes separately so a detection improvement can be distinguished from a simultaneous reduction in resolution or color settings.
Choose an available supported combination while investigating, weighing motion smoothness against resolution and readability for the actual task. Record the final rate for each screen rather than assuming both changed together. A useful outcome is a stable, documented configuration with a clear explanation of its boundary, whether that boundary comes from the host, a shared connection or the monitor input.
