Clone Display to TV or Projector Lowers Main Monitor Resolution & Refresh Rate or Opens Games on the Wrong Screen? Clone-Mode Common-Mode, Primary Display & Audio-Follow Diagnosis Guide

| HK GPU Fix

Clone Display to TV or Projector Lowers Main Monitor Resolution & Refresh Rate or Opens Games on the Wrong Screen? Clone-Mode Common-Mode, Primary Display & Audio-Follow Diagnosis Guide

Key Takeaways

When a monitor is cloned to a TV or projector, both screens must share one signal, so resolution, refresh rate, HDR and chroma fall to the mode both displays support. This guide explains the common-mode rule, the primary-display logic that decides where games open and where sound goes, and a step-by-step sequence for isolating whether the limit comes from the TV, the projector, the cable, the port, or the display setting itself.

Why Clone Mode Behaves Differently From Extend Mode

In Extend mode, the operating system treats each display as an independent surface. The monitor can run at its own native resolution and refresh rate, and the TV or projector can run at a different resolution and refresh rate, because the graphics processor renders two separate outputs and the driver negotiates a separate timing for each output. The desktop is wider, windows can be moved from one screen to the other, and a game can be assigned to one display while the other display shows something else.

Clone mode removes that independence. The system renders one image and duplicates it to both outputs. Both outputs must agree on a single timing: one horizontal resolution, one vertical resolution, one refresh rate, and one colour format that both displays can accept. If the monitor supports a higher mode than the TV, the system cannot keep the monitor at its higher mode while also sending a signal the TV can display. It must step down to a mode the TV can accept. The same logic applies in reverse: if the projector is the weaker display, the projector sets the ceiling. The result is a single shared mode, not two optimised modes.

This distinction explains the most common surprise in clone setups. A user connects a TV for a film night or a presentation, switches from Extend to Duplicate, and watches the main monitor drop from a crisp high-resolution, high-refresh-rate image to a softer, slower image. Nothing has broken in that moment. The system has simply changed the contract: instead of two independent timings, there is now one shared timing, and that timing must fit the less capable display. Understanding that contract before changing anything else prevents a long chain of unnecessary driver reinstalls, cable swaps, and settings changes that cannot override the underlying rule.

A second, related point is that clone mode is a display-mode decision, not a performance setting. It does not change how fast the graphics card renders a game, and it does not by itself make the graphics card weaker. What changes is the output timing and, in many cases, the colour format. A game rendered at a high internal resolution may still be downscaled to the cloned output resolution, and a high-refresh-rate monitor may be driven at the shared refresh rate for as long as cloning is active. Returning to Extend mode, or disconnecting the second display, restores the independent timings, provided the underlying settings have not been changed in the meantime.

The Common-Mode Rule: The Intersection, Not the Average

The common mode is best understood as an intersection of capability lists. Each display publishes a list of modes it accepts, through its Extended Display Identification Data, or EDID. Each port and each cable also imposes limits: an older HDMI port, a long passive cable, an adapter, or a docking station may not carry the same bandwidth as a direct, modern connection. The driver then looks for a mode that appears on every list at once. That mode becomes the cloned output.

This is not an average, and it is not a compromise halfway between the two displays. If the monitor supports 144 Hz and the TV supports 60 Hz, the shared refresh rate is 60 Hz, not a midpoint. If the monitor supports a high resolution and the TV supports a lower resolution, the shared resolution is the lower one, unless the system uses scaling to present a higher-resolution image inside a lower-resolution signal, which still does not give the TV a true higher-resolution picture. If the monitor supports HDR and a wide colour format, but the TV or projector does not support the same combination at the same resolution and refresh rate, HDR or the wider colour format may drop out of the cloned signal altogether.

Bandwidth is the hidden constraint behind many of these intersections. Resolution, refresh rate, colour depth, and chroma subsampling all consume bandwidth, and the total must fit within what the weakest link in the chain can carry. A mode that looks modest on paper can exceed the available bandwidth once HDR and full chroma are added. That is why a clone that works at one resolution may fail, flicker, or silently fall back to a lower colour format when a higher resolution or a higher refresh rate is requested. The driver may choose a lower chroma format, such as 4:2:2 or 4:2:0 instead of 4:4:4, to fit the signal into the available bandwidth, and text may then look softer even though the headline resolution number has not changed.

Scaling adds another layer of confusion. Some systems offer a clone mode in which the higher-resolution display shows a scaled version of the shared signal, or the lower-resolution display shows a downscaled version. The headline numbers in the settings panel may therefore not tell the full story. A monitor that reports a high resolution in clone mode may still be displaying a signal that was rendered and transmitted at a lower resolution and then upscaled. Conversely, a TV that reports a lower resolution may be receiving a downscaled image that looks softer than a native signal at the same resolution. For diagnosis, the reported mode, the perceived sharpness, and the refresh rate actually in use must all be checked, not just one of them.

Capability Intersection at a Glance

CapabilityMain monitor aloneTV or projector aloneCloned output (typical result)
ResolutionHigher native resolutionLower native resolutionLower resolution, shared by both
Refresh rateHigher refresh rate, for example above 60 Hz60 Hz60 Hz, shared by both
HDRSupported at the native modeNot supported, or supported only at a lower modeHDR off, or limited to the lower shared mode
Chroma / colour formatFull chroma at the native modeLimited chroma at higher modesReduced chroma if needed to fit bandwidth
Colour depthHigher depth at the native modeLower depth at the shared modeLower depth if the shared mode requires it
Scaling behaviourNative, one-to-one pixelsNative, or upscaled from the shared signalOne shared signal, scaled on at least one display

The table is illustrative, not a specification for any particular model. Real displays differ, and the exact intersection depends on the EDID lists of the two specific displays, the ports used, and the cable. The diagnostic value of the table is the pattern: the cloned column never exceeds the weaker display, and any capability that only one display supports is at risk in clone mode.

Why the Main Monitor Drops Resolution and Refresh Rate

The drop is a direct consequence of the intersection rule, but the way it appears can vary, and those variations matter for diagnosis. Sometimes the resolution drops immediately when Duplicate is selected, and the settings panel shows the lower resolution on both displays. Sometimes the resolution number stays the same but the refresh rate drops, because the system keeps the resolution and sacrifices the refresh rate to fit the shared bandwidth. Sometimes the resolution and refresh rate numbers stay the same, but the image looks softer, because chroma subsampling or colour depth has changed to fit the signal through the weaker link. Sometimes HDR disappears from the settings panel entirely while cloning is active, and returns when the clone is ended.

Another variation is a drop that only appears at a particular combination. A TV may support a high resolution at 60 Hz but not at a higher refresh rate, or may support HDR at a lower resolution but not at the higher resolution. A projector may support a given resolution over one input but not over another input, because the inputs have different bandwidth or different processing paths. In those cases, cloning at one combination looks normal and cloning at another combination forces a fallback. Testing only one combination and concluding that cloning is broken, or that it works, can therefore mislead. The diagnosis must test the combinations that matter: the combination the user actually wants to use, and the native combination of each display on its own.

A further variation involves the order in which displays are connected. If the TV is connected and recognised first, the system may initially propose a mode based on the TV, and the monitor may then follow. If the monitor is connected first, the system may initially propose a higher mode and then step down when the TV is added. Neither order is wrong, and neither order changes the final intersection, but the intermediate steps can look inconsistent if only one order is tried. For a clean diagnosis, the order should be noted, and the test should be repeated with the displays connected in the order the user normally uses them.

It is also important to separate a clone-mode drop from a single-display limit. If the monitor drops resolution or refresh rate even when the TV is disconnected and the system is in single-display mode, the cause is not cloning. If the monitor returns to its native mode as soon as cloning ends, the clone intersection is the likely explanation, even if the exact numbers are surprising. That before-and-after comparison, in Extend and then in Clone, is the single most informative test in this whole guide, and it should be done before any deeper step.

Primary Display: A Separate Decision From Cloning

Clone mode decides what image both displays show. Primary display decides which display the system treats as the main display. The two decisions interact, but they are not the same decision, and confusing them causes many of the wrong-screen problems that users report.

The primary display is where the taskbar, the main desktop icons, and many system dialogs appear by default. It is also the display that many games treat as the default full-screen target, especially in exclusive full-screen mode. Changing which display is primary, without changing the clone setting, can therefore change where a game opens, where a new window appears, and which display the system treats as the reference for certain settings. Changing the clone source, where the settings panel offers that choice, can have a similar effect, because the source display defines the image that is duplicated.

In a clone setup, the primary display still matters even though both displays show the same image. The image is the same, but the system still has a notion of a main display for window placement, for full-screen assignment, and for audio routing in some configurations. A user who clones a monitor to a TV, makes the TV the primary display by accident, and then launches a game may find the game opening in a way that feels tied to the TV, even though the picture appears on both screens. A user who then changes the primary display back to the monitor may find the game behaviour changes again, even though the clone setting has not changed. Tracking the primary display separately from the clone setting is therefore essential.

The practical rule is to set the primary display deliberately, not leave it to the order in which displays were connected. In the display settings, identify each display by number, confirm which physical display corresponds to which number by using the identify function, and then set the intended main display as primary. After changing the primary display, test the exact behaviour that was problematic, whether that is a game opening, a window placement, or an audio route, rather than assuming the change has fixed it. If the behaviour does not change, the cause lies elsewhere, and the next step in the sequence should be tried.

Why Games Open on the Wrong Screen in Clone Mode

Games add a further layer, because full-screen games do not always follow the same rules as desktop windows. A windowed or borderless-windowed game generally follows the display it was launched on, or the display where its window sits, and can often be moved. An exclusive full-screen game, by contrast, typically takes over one display output, and the choice of output is governed by the game's own display selection, by the primary-display setting, and by the adapter and output order that the driver reports. In a clone setup, where two outputs are showing the same image, the game's choice of output can still matter for resolution, refresh rate, HDR, and for which display's timing the game actually uses.

The symptom described as opening on the wrong screen can therefore mean several different things, and each meaning points to a different check. It can mean the game window appears on the TV rather than the monitor in Extend mode, which is a window-placement and primary-display issue. It can mean the game renders at the TV's resolution and refresh rate even though the monitor is the intended display, which is a clone common-mode issue. It can mean the game opens in full-screen on one output and the other display goes black, flickers, or shows a duplicated image at the wrong size, which is an exclusive-full-screen and output-handshake issue. It can mean the game opens correctly but at a lower refresh rate than the monitor supports, which is again the common-mode ceiling. Naming the exact symptom, rather than using the shorthand wrong screen, is the first step to a correct diagnosis.

A useful test is to separate the game's display selection from the clone setting. First, in Extend mode, set the intended display as primary, launch the game, and observe where it opens and at what mode. Then, if the game offers its own display selector, set it explicitly to the intended display and test again. Then, switch to Clone mode and repeat the same launch, noting any change in resolution, refresh rate, or target display. If the game behaves correctly in Extend mode but changes in Clone mode, the clone intersection or the clone source is implicated. If the game behaves incorrectly in Extend mode as well, the problem is in the primary-display setting, the game's display selector, or the game's full-screen handling, and cloning is not the primary cause.

Another useful test is to test each display alone. Disconnect the TV or projector, launch the game on the monitor alone, and record the mode. Then disconnect the monitor, launch the game on the TV or projector alone, and record the mode. This isolates whether either display, on its own, forces a lower mode for reasons unrelated to cloning, such as a port limit, a cable limit, or a game setting that remembers a previous mode. Only after each display has been characterised alone can the cloned result be interpreted with confidence.

Audio Follows the TV: A Separate Routing Decision

Sound routing is another area where clone mode surprises users, because the audio decision is separate from the image decision. When a TV is connected over HDMI or DisplayPort, the TV often appears as an audio endpoint, and the system may switch the default audio device to the TV, or may keep the previous default, depending on the settings and on the order of connection. The result can be sound coming from the TV speakers when the user expected sound from desktop speakers or headphones, or sound staying on the desktop speakers when the user expected it from the TV for a film.

The key point is that cloning the image does not, by itself, dictate the audio route. The audio route follows the default playback device setting, and in some systems it follows the primary display or the most recently connected HDMI audio endpoint. Changing the clone setting without checking the audio setting can therefore leave the sound on the wrong device, and changing the audio setting without checking the clone setting can leave the picture on the wrong display. Both must be checked explicitly.

For diagnosis, the audio test should be simple and isolated. With the clone active, play a known sound and note which device produces it. Then open the sound settings, identify the current default playback device, and change it deliberately to the intended device, whether that is the TV, the desktop speakers, or headphones. Test again. If the sound follows the change, the routing was a settings issue. If the sound does not follow, or if the intended device does not appear at all, the next checks are the cable, the port, and whether the TV input selected actually carries audio from the connected port. Some TV inputs and some projector inputs handle audio differently, and an input that shows a picture may still not be the input that the system recognises as the audio endpoint.

A related boundary case is a projector with no speakers, or with speakers that are muted or set to a different input. In that case, the system may still list the projector as an audio endpoint, but no sound will be heard from it, and the user may conclude that audio is broken when it is in fact routed to a silent endpoint. Checking the actual playback device, rather than assuming the picture and the sound travel together, avoids that misdiagnosis.

The Step-by-Step Diagnosis Sequence

The sequence below is designed to isolate one variable at a time. Skipping steps, or changing several things at once, makes the result uninterpretable, because it becomes impossible to know which change produced the improvement. Each step should be recorded: what was changed, what mode resulted, and what symptom changed.

Diagnosis Sequence

StepActionWhat to recordWhat the result means
1In Extend mode, test the monitor alone at its native resolution and refresh rateNative mode achieved, or notEstablishes the monitor baseline without cloning
2In Extend mode, test the TV or projector alone at its native resolution and refresh rateNative mode achieved, or notEstablishes the second display baseline without cloning
3Switch to Duplicate or Clone and record the forced shared modeShared resolution, refresh rate, HDR and chroma stateReveals the common-mode intersection
4Change the primary display to the other display, then repeat step 3Whether the shared mode or game behaviour changesTests whether primary-display logic, rather than capability, drives the symptom
5Change the clone source, where the setting exists, then repeat step 3Whether the shared mode or game behaviour changesTests whether the source display defines the cloned image
6Test each display alone again, with the other display disconnectedMode on each display aloneSeparates a single-display limit from a clone intersection
7Change one link in the chain, such as the cable or the port, and repeat steps 3 to 6Whether the shared mode improvesIsolates a cable, port, or adapter limit
8Check the audio default separately, with the clone activeWhich device actually plays soundSeparates audio routing from image cloning

Step 1 and step 2 are the baselines. Without them, a cloned result cannot be judged, because there is no known native mode to compare it against. A monitor that cannot reach its native mode even alone has a different problem from a monitor that reaches its native mode alone but drops in clone mode, and the two problems require different next steps. The same applies to the TV or projector: a TV that cannot reach its stated mode alone, for example because of the input selected or the cable used, will also limit the clone, and fixing the single-display issue may raise the clone ceiling.

Step 3 is the clone observation. It should be recorded in full: resolution, refresh rate, HDR on or off, and, where the settings panel shows it, colour format. A partial record, such as resolution only, can hide a chroma or HDR change that explains why the picture looks softer even though the resolution number is unchanged.

Steps 4 and 5 test the logic layer. If changing the primary display or the clone source changes where a game opens, or changes the audio route, but does not change the shared resolution or refresh rate, then the capability intersection is still the ceiling, and the logic change has only affected placement and routing. If changing the primary display or the clone source changes the shared mode itself, then the system is using the primary or source display as a reference for the clone negotiation, and that reference should be set to the intended display for the user's normal use.

Step 6, testing each display alone again, guards against a change made during the earlier steps that has persisted. Display settings sometimes persist after a clone is ended, such as a lower refresh rate left selected, or a primary display left changed. Re-testing alone after the clone steps confirms whether the baselines are still intact, or whether a setting needs to be restored.

Step 7 changes one link at a time. The chain includes the port on the computer, the cable, any adapter or docking station, the port on the TV or projector, and the input selected on the TV or projector. Changing the cable and the port at the same time, and seeing an improvement, does not tell which link was the limit. Changing one link, re-testing the clone, recording the result, and then, if needed, changing the next link, produces a chain of evidence that can be followed back if the problem returns.

Step 8 is the audio check, kept separate because audio routing follows its own setting. It should be done with the clone active, because the audio endpoint list can change when a display is connected or disconnected, and a test done with the TV disconnected may not reflect the endpoint list that exists during cloning.

Boundary Cases That Change the Intersection

Adapters and converters are a frequent boundary case. A passive adapter that converts one connector type to another may carry only the bandwidth of the older standard, even if both displays support a higher mode. An active converter may support a higher bandwidth but may also impose its own EDID or its own timing limits. A docking station may share bandwidth between its outputs, so that two displays connected through the same dock have a lower combined ceiling than the same displays connected directly. In each case, the intersection must be calculated including the adapter or dock, not just the two displays. Testing the same displays with a direct connection, where possible, isolates whether the adapter or dock is the limiting link.

Long cables are another boundary case. A cable that works at a lower mode may fail or fall back at a higher mode, especially at longer lengths or through wall plates and extenders. The symptom may be intermittent: a picture that works at one resolution but flickers or drops at a higher resolution, or a mode that is offered in the settings panel but does not hold when selected. In clone mode, a marginal cable on one leg of the chain can lower the shared mode for both displays, even though the other leg is sound. Testing with a shorter, known-good cable on the suspect leg, one leg at a time, is the clean way to isolate this.

TV and projector inputs are a third boundary case. Not all inputs on the same TV are equal. One input may support a higher bandwidth, a higher refresh rate, or HDR, while another input supports only a lower mode. A projector input may be limited by its own processing path, or by a setting such as a game mode or a presentation mode that changes the accepted timings. The diagnosis should therefore note which physical input is in use, and test a different input on the same TV or projector where the manual or the settings panel indicates a difference. Changing the input and seeing the clone ceiling rise points to the input, not to the display panel itself.

A fourth boundary case is a display that reports a mode it cannot sustain in clone mode because of its own scaling or processing. Some TVs apply overscan, motion processing, or a presentation preset that changes the effective picture, even when the input timing is correct. The settings panel may report the correct resolution and refresh rate, but the picture may look cropped, soft, or delayed. In that case, the TV's picture settings, not the computer's display settings, are the next place to check, and the test should be done with the TV's processing presets noted.

A fifth boundary case involves multiple graphics outputs from different sources, such as a discrete graphics card and an integrated graphics output on the same computer. If the monitor is connected to one source and the TV to another, the clone negotiation may involve two different drivers or two different capability lists, and the result may differ from a clone where both displays are driven by the same graphics processor. Noting which port belongs to which graphics source, and testing both displays from the same source where possible, helps to separate a source-mixing issue from a pure clone intersection.

Common Misconceptions

The first misconception is that cloning should preserve each display's best mode. It cannot, by definition, because it sends one signal to both displays. Expecting the monitor to stay at its highest mode while the TV also shows a correct picture is expecting two different signals, which is Extend mode, not Clone mode. If the goal is to keep each display at its best mode, the correct setting is Extend, with the content moved to the intended display, not Clone.

The second misconception is that a higher-numbered cable or a newer port automatically raises the clone ceiling. It raises the ceiling only if the cable or port was the limiting link. If the TV itself only supports a lower mode, a better cable cannot make the TV accept a higher mode, and the clone will still fall to the TV's limit. The diagnosis sequence matters here: changing the cable before establishing the baselines can waste effort and can create a false impression that the cable was at fault when the display limit remains.

The third misconception is that the primary display setting changes the clone resolution. In many systems it does not, or it does so only indirectly, by changing which display's list is used as a reference. If the shared mode does not change when the primary display is changed, that is not a failure of the setting. It is evidence that the capability intersection, not the primary setting, is the ceiling, and the next step should be the cable, port, input, or display capability, not repeated primary-display changes.

The fourth misconception is that a game opening on the wrong screen means the clone is broken. As described above, game display selection, primary-display logic, and exclusive full-screen handling are separate from the clone signal. A game can open on the unintended display in Extend mode, and can open on the intended display in Clone mode, depending on those settings. The game test must therefore be done in both modes, with the game's own display selector noted, before cloning is blamed.

The fifth misconception is that audio should automatically follow the picture. Audio follows the default playback device, which may or may not follow the picture, depending on the system. If sound comes from the wrong device, the first check is the sound settings, not the display settings, and the fix is to set the default playback device deliberately, not to change the clone mode and hope the audio follows.

The sixth misconception is that a single successful clone at one mode proves that all modes should work. Capability lists are mode-specific. A TV may accept a high resolution at a lower refresh rate, or HDR at a lower resolution, but not both at once. A clone that works at one combination and falls back at another is consistent with the intersection rule, and the fallback combination should be recorded as a separate data point, not treated as a contradiction.

Routing: Related Problems That Are Not This Problem

Several related display problems share surface symptoms with clone-mode limits, but they have different mechanisms and different fixes, and they should not be rewritten as clone problems. If the symptom involves cloning specifically to a capture card and the result is a black screen related to content protection, that is the subject of the capture-card clone and HDCP discussion, covered separately as topic 200, and the checks there focus on the capture path and its protection handling rather than on the general common-mode rule. If the symptom involves a single TV on its own, with bandwidth or overscan as the dominant issue and no second display cloned, that is the single-TV bandwidth and overscan discussion, covered separately as topic 186, and the checks there focus on the single link and the TV's own scaling.

If the symptom is a mode lock on a single display, where one display alone cannot be set to its native mode regardless of cloning, that is the single-display mode-lock discussion, covered separately as topic 110, and the checks there focus on that display's EDID, port, and driver negotiation without a second display in the chain. If the symptom is that a display is misidentified, so that the system negotiates modes for the wrong model, that is the EDID misidentification discussion, covered separately as topic 259, and the checks there focus on identification and EDID handling rather than on the clone intersection itself. If the symptom is that windows rearrange themselves after the system wakes, with displays reconnecting in a different order, that is the wake window-rearrangement discussion, covered separately as topic 267, and the checks there focus on wake and reconnection order rather than on the shared clone timing. Routing a symptom to the correct discussion matters, because applying the clone sequence to a single-display lock, or applying a single-display fix to a clone intersection, will not resolve the underlying cause.

When the Clone Ceiling Cannot Be Raised

In some setups, the clone ceiling is simply the capability of the weaker display, and no cable, port, or setting change will raise it without replacing that display or changing the setup. In that situation, the honest options should be stated clearly. The user can accept the shared lower mode while cloning is active, and return to Extend mode or single-display mode for work or gaming that needs the higher mode. The user can use Extend mode instead of Clone mode, and move the content that needs to be shared to the TV or projector, while keeping the monitor at its native mode for everything else. The user can use a separate output or a separate device for the TV or projector, rather than cloning the main monitor at all. Or the user can replace the limiting link, whether that is the display, the cable, or the adapter, after the diagnosis sequence has identified which link it is.

What should not be done is to force a mode the weaker display cannot accept, in the hope that it will somehow work. Forcing an out-of-range timing can produce a black screen, a flickering picture, or a display that reports no signal, and it can make the diagnosis harder, because the system may then retain a forced mode that persists after cloning ends. The diagnosis sequence above is designed to find the highest mode that both displays genuinely accept, not to force a mode beyond that intersection.

For users who need both a high-refresh-rate monitor for gaming and a TV for shared viewing, the practical workflow is often to switch modes for the task at hand: Extend or single-display for gaming at the monitor's native mode, and Clone only for the period when shared viewing is actually needed, accepting the shared mode for that period. That workflow is not a workaround for a fault. It is the correct use of two different display modes for two different purposes.

For further help with a setup where the diagnosis sequence points to a hardware limit rather than a settings issue, contact details are: Dali Plaza Room 1209, Shek Mun; telephone 2186 8010; WhatsApp 6558 6806.

Frequently Asked Questions

Why does my main monitor drop resolution as soon as I clone it to a TV?

Because clone mode sends one shared signal to both displays, and that signal must fit the TV as well as the monitor. If the TV supports a lower resolution than the monitor, the shared resolution falls to the lower one. Test each display alone in Extend mode first to confirm each native mode, then compare the cloned mode against those baselines.

Why does the refresh rate drop to 60 Hz in clone mode even though my monitor supports more?

Because the shared refresh rate must be supported by both displays, and by the cable and ports in the chain. If the TV or projector supports only 60 Hz, or supports a higher rate only at a lower resolution, the cloned refresh rate will be limited to the shared value. The monitor returns to its higher rate when cloning ends and Extend or single-display mode is restored.

Why does HDR disappear when I clone, and return when I stop cloning?

Because HDR at a given resolution, refresh rate, and colour format requires bandwidth and support on both displays. If the second display does not support the same HDR combination, or if the shared mode cannot carry it within the available bandwidth, HDR drops out of the cloned signal. It returns when each display is driven independently again.

Why does text look softer in clone mode even when the resolution number is unchanged?

Because chroma subsampling or colour depth may have changed to fit the shared signal into the available bandwidth, even though the resolution number stayed the same. Check the colour format where the settings panel shows it, and compare the cloned picture against each display alone at the same resolution.

Why does a game open on the wrong screen when I am cloning?

Because game display selection, primary-display logic, and exclusive full-screen handling are separate from the clone signal. Check the primary display setting, check the game's own display selector, and test the same game in Extend mode and on each display alone before concluding that cloning is the cause.

Why does sound come from the TV when I expected desktop speakers, or vice versa?

Because audio follows the default playback device setting, not automatically the cloned picture. Open the sound settings while the clone is active, identify the current default device, and set it deliberately to the intended device. If the intended device does not appear, check the cable, the port, and the TV input selected.

Should I keep changing cables until the clone matches my monitor's best mode?

No, not without baselines. Establish each display's native mode alone first, then record the cloned mode, then change one link at a time. If the TV itself is the limit, a better cable cannot raise the clone ceiling, and repeated cable changes without baselines will not identify the real limiting link.

Related articles

Related services

If you need Chip-level GPU repair, see these service pages: