Primary Display Swaps by Itself After Sleep or Reconnect? Wake Order, Re-enumeration & Main Display Diagnosis Guide

2026-11-16 | GPU Repair | 29 minutes | HK GPU Fix Editorial Team

Primary Display Swaps by Itself After Sleep or Reconnect? Wake Order, Re-enumeration & Main Display Diagnosis Guide

Key Summary

After sleep or reconnection, the taskbar may move to the other monitor, meaning Windows has reassigned which display is primary. This guide uses the taskbar as the decisive test, then checks wake order, DisplayPort versus HDMI behaviour, and re-enumeration to narrow five suspect layers to one through a seven-step diagnosis, without treating a single re-setting as a fix.

The Symptom That Needs a Name

The computer goes to sleep. It wakes up. Nothing has been unplugged, no setting has been touched, and yet the desktop has rearranged itself: the taskbar is on the other monitor, the main application windows open on the other monitor, and the display that was primary yesterday is now secondary. Setting it back works — until the next sleep, when it swaps again. Or it swaps only sometimes, following no pattern the user can see, which makes it feel random and therefore unfixable.

It is not random. It follows the wake-up sequence, and once the sequence is understood, the symptom becomes diagnosable. The key idea is re-enumeration: when the computer wakes from sleep, or when a display is reconnected, Windows detects the connected displays again and counts them in the order they respond. Whichever display wakes first gets counted first, and if the counting order changes, the primary display assignment can change with it. The user did not change a setting; the system re-ran its detection, and the detection came out in a different order.

That distinction — between a setting the user changed and a detection the system re-ran — is the foundation of this guide. A setting that was changed by hand stays changed until it is changed back. A detection that comes out differently each time will undo a manual correction on the next wake, because the manual correction only changed the result of the last detection, not the conditions under which the next detection runs. This is why re-setting the primary display, on its own, so often appears to work and then fails again: it treated the outcome, not the cause.

This guide exists because the symptom has had no article of its own. The neighbouring guide on window layout after sleep and reconnection covers windows moving to the primary display, but in that guide the primary display itself never changes — the windows move, the primary stays put. The guide on the boot screen appearing on the wrong monitor deals with the firmware layer, where the boot picture is on the wrong display but the desktop is correct once Windows loads, and it expressly places Windows-layer primary-display problems outside its own scope. The guide on games opening on the wrong monitor deals with the game layer, where the desktop and taskbar are completely normal, and it expressly excludes problems that appear after sleep. The guide on resolution and refresh rate dropping after waking covers a single display only, and it says so in its own scope: it deals with one display waking into a fallback mode, not with two displays swapping primary status. None of them covers a primary display that swaps by itself after sleep or reconnection. This guide fills that gap, and it does so with a single decisive test that separates it from all five neighbours at once.

The Decisive Test: Where Did the Taskbar Go?

Before anything is changed, before any cable is swapped or any setting is opened, look at the taskbar. After a sleep or reconnection that rearranged the desktop, the position of the taskbar answers the first and most important question: did the primary display really swap, or did only the windows move?

If the taskbar moved to the other monitor, the primary display genuinely swapped. The taskbar sits on the primary display, so its movement is the evidence that the primary assignment itself changed. This guide applies, and the investigation continues here.

If the taskbar did not move and only the windows moved, the primary display did not change. That is the window-layout problem covered by the neighbouring guide on windows moving after sleep and reconnection: the displays were re-enumerated, the desktop shrank or shifted while a display was briefly absent, and the windows were gathered onto the display that stayed connected. The primary assignment was never involved, and working through this guide would be working on the wrong problem.

Three other shapes are separated by the same glance. If the boot screen appears on the wrong monitor but the desktop is correct once Windows has loaded, that is the firmware layer, covered by the guide on the boot screen on the wrong monitor — not a Windows-layer swap. If only a game opens on the wrong monitor while the desktop and taskbar are completely normal, that is the game layer, covered by the guide on games opening on the wrong monitor; the primary display did not swap, because a swapped primary would show on the desktop without any game running. If a monitor switches its own input, or reports no signal, that is the monitor's firmware layer, where the display itself changes which input it listens to — a different layer from Windows reassigning which display is primary, and covered by the guide on a monitor switching inputs by itself.

One look at the taskbar, taken in the moment the symptom appears, separates five different guides. It is worth taking that look deliberately and recording it, rather than fixing the layout first and trying to remember afterwards which monitor the taskbar had been on. Once the layout has been corrected by hand, the evidence is gone. Record first: which monitor had the taskbar before sleep, which monitor has it after waking, and whether the windows moved with it or stayed behind.

How Wake Order Decides the Primary Display

The mechanism behind the swap is straightforward once it is laid out, and it has three parts: re-enumeration, wake order, and the difference between DisplayPort and HDMI when a display sleeps.

Re-enumeration is the trigger, not the fault itself. Sleep, reconnection, switching a KVM, and plugging or unplugging a dock all cause Windows to detect the connected displays again. Detection is not a fault; it is normal behaviour, and it happens every time the display chain changes. The fault, when there is one, is in what the detection produces — a counting order that differs from the order before sleep. The guide on window layout after sleep describes this same detection step, and the guide on games opening on the wrong monitor notes in passing that the primary display assignment can change and that the enumeration result can change. This guide takes those passing observations as its starting point and makes them the subject.

Wake order is what decides the counting order. The monitor that wakes first gets counted first, as an external guide on monitor order swapping after sleep puts it (unstuckguide.com, "Monitor Order Swaps After Sleep on Windows", 28 October 2026). If the two monitors wake in a different order on different occasions — because one takes longer to leave its power-saving state, because one was woken by a different signal, or because the computer asked for the displays before one of them was ready — the counting order can change, and the primary assignment can change with it. The wake-order comparison in Step 3 of this guide is built directly on this: wake the monitors first, wait until they are fully awake and showing a ready state, and only then wake the computer. If that order produces a normal wake, the fault sits in the timing of the wake sequence.

The third part is the difference between DisplayPort and HDMI when a display sleeps. A DisplayPort monitor, when it sleeps, is seen by the system as disconnected: the windows and taskbar move to the display that is still connected. An HDMI monitor, when it sleeps, is usually still recognised. This is documented in an ASUS official FAQ (FAQ 1044064), and it matters because it turns the choice of connector into a diagnostic comparison rather than a question of cable quality. If one monitor uses DisplayPort and the other uses HDMI, and the DisplayPort monitor is the one that loses primary status after sleep, the interface is a strong suspect — not because DisplayPort is faulty, but because its sleep behaviour is different by design. The comparison in Step 4 tests exactly this, by putting both monitors on the same kind of connection and waking twice.

A further mechanism sits behind the re-enumeration: Windows 11 can reset display settings after waking from sleep. The temporary multi-monitor manager, which automatically detects display changes, can reset the display arrangement and the primary display setting when the system wakes (windowsdigitals.com, "Stopping Windows 11 from Resetting Monitor After Sleep"). That is a setting being reset by the system, not a setting being changed by the user, and it is one more reason why re-setting the primary display by hand is not a repair: the next wake can reset it again. The symptom is also documented as a genuine user experience, not a hypothetical one: a Microsoft Q&A discussion ("Windows 11 Display settings change on their own") records a user reporting that the primary display changed by itself to the other monitor after the system woke from sleep. That discussion is cited here as published evidence that the shape exists; it is a public forum report, not testing carried out by this site.

The Five Suspect Layers

Everything that can make the primary display swap after sleep or reconnection sits in one of five layers. The layers are listed here so that each later step can be read as testing one of them.

Layer 1: The Wake-Timing Layer

This layer is the order in which the displays and the computer wake. Whichever display wakes first gets counted first, so a change in wake order is a change in counting order, and a change in counting order can change the primary assignment. Its decisive test is the wake-order comparison in Step 3: wake the monitors fully before waking the computer, and see whether the swap still happens. If changing the order changes the result, the fault sits in timing, and no cable, setting, or driver change is needed to explain it.

Layer 2: The Re-enumeration Layer

This layer is Windows detecting and counting the displays again after sleep or reconnection, and the counting order changing as a result. Re-enumeration is the trigger that all the other layers act through: sleep, reconnection, a KVM switch, and a dock being plugged or unplugged all cause it. The temporary multi-monitor manager resetting the arrangement and primary setting after waking belongs in this layer as well. Its clue is that the swap follows sleep or reconnection specifically, and does not happen during ordinary use, when no re-enumeration is taking place.

Layer 3: The Connection and Interface Layer

This layer is the physical connection: DisplayPort against HDMI, a KVM switch, a dock, an adapter, and any virtual display. The DisplayPort sleep behaviour described above — the system seeing a sleeping DisplayPort monitor as disconnected — is this layer's strongest clue. A KVM or dock belongs here too, because switching a KVM or plugging in a dock triggers re-enumeration, and a dock or switch that presents the displays in a different order each time will produce a different counting order each time. A virtual display, if one is present, can also take part in the enumeration and shift the counting order.

Layer 4: The Settings Layer

This layer is the primary display setting itself, the display arrangement, and whether the driver keeps the previous setting. Its characteristic pattern is that the primary display is set by hand, and the next sleep swaps it again. That pattern points to a problem with keeping the setting, not with the setting being wrong: the setting was correct when it was made, and something about the next wake undid it. Re-setting the primary display once and declaring the problem fixed is the error this layer invites, because a single successful re-setting says nothing about whether the setting will survive the next wake. The test for this layer is in Step 5: set the primary display again, then sleep and wake twice, and see whether the setting holds.

Layer 5: The Monitor Power and Firmware Layer

This layer is the monitor's own power state and firmware: deep sleep, the monitor's power-saving state, and the monitor's own input switching. A monitor that is slow to leave deep sleep will be counted late, or not counted at all on the first pass, which feeds directly back into the wake-timing layer. A monitor that switches its own input is a neighbouring problem, not this one: if the monitor changes input or reports no signal, the fault sits in the monitor's firmware, and the guide on a monitor switching inputs by itself is the one that covers it. The boundary is that in a primary-display swap, both monitors have a picture — only the primary and secondary roles have exchanged.

LayerWhat it coversStrongest clueDecisive test
1. Wake timingWhich display wakes first; order of waking monitors vs computerSwap follows a particular wake orderWake-order comparison (Step 3)
2. Re-enumerationWindows re-detecting and re-counting displays; settings reset on wakeSwap follows sleep or reconnection onlyTwo sleeps under the same wake conditions (Step 5)
3. Connection and interfaceDisplayPort vs HDMI, KVM, dock, adapter, virtual displayDisplayPort monitor loses primary; bypassing KVM/dock stops the swapInterface comparison (Step 4); bypass comparison (Step 6)
4. SettingsPrimary setting, arrangement, whether the driver keeps the settingRe-setting works once, then the next sleep swaps againRe-set, then sleep and wake twice (Step 5)
5. Monitor power and firmwareDeep sleep, power-saving state, monitor's own input switchingOne monitor is slow to wake; monitor changes input or shows no signalWake-order comparison; boundary with the input-switching guide

The layers interact, and that interaction is part of why the symptom feels confusing. A monitor in deep sleep (Layer 5) wakes late (Layer 1), so it is counted late (Layer 2), and if it is the DisplayPort monitor (Layer 3) the system may have seen it as disconnected in the meantime. No single layer explains every case, which is why the seven steps test them in an order that separates them, rather than treating the most visible layer as the cause.

The Seven-Step Diagnosis

The seven steps below are ordered so that the cheapest and most decisive comparisons come first, and so that each step's result decides which step follows. They should be worked through in order, with the record kept as they go.

Step 1: Check the Taskbar — Did the Primary Display Really Swap?

After a sleep or reconnection that rearranged the desktop, look at which monitor the taskbar is on before changing anything. If the taskbar moved to the other monitor, the primary display genuinely swapped, and this guide continues. If the taskbar did not move and only the windows moved, the primary display did not change, and the problem is the window-layout problem covered by the guide on windows moving after sleep and reconnection. If the boot screen was on the wrong monitor but the desktop is correct once Windows has loaded, that is the firmware layer, covered by the guide on the boot screen on the wrong monitor. If only a game opens on the wrong monitor while the desktop and taskbar are completely normal, that is the game layer, covered by the guide on games opening on the wrong monitor. If a monitor switched its own input or reports no signal, that is the monitor's firmware layer, covered by the guide on a monitor switching inputs by itself.

This step is the whole reason the taskbar test is described as decisive. It is also the step most often skipped, because the natural reaction to a rearranged desktop is to fix the layout immediately. Fixing it first destroys the evidence: once the primary display has been set back by hand, there is nothing left to observe about which monitor the system chose on its own. Look, record, and only then correct.

Step 2: Record the Baseline Before Changing Anything

Before any setting is changed, record the baseline: which monitor was primary before sleep, which monitor became primary after waking, whether it happens every time or only sometimes, which monitor wakes first, and which interface each monitor uses. Note the wake source as well — whether the computer was woken by the keyboard, the mouse, the power button, or a scheduled event — because the wake source can affect the timing of the sequence, and a swap that follows one wake source but not another is following a particular wake condition.

The baseline is the reference that every later comparison is measured against. Without it, there is no way to tell whether a later wake was normal because a step fixed something, or normal because the wake conditions happened to be different that time. A single swap after one sleep can be a coincidence; the test for a repeated pattern is in Step 5, where the same wake conditions are repeated twice. The baseline should also record whether the arrangement was set by hand after a previous swap, because a hand-set arrangement that swaps again on the next sleep is itself evidence — it says the setting is not being kept, which points at Layer 4.

Step 3: Run the Wake-Order Comparison

Wake the monitors first: wake each monitor and wait until it is fully awake and showing a ready state, and only then wake the computer. Then reverse the order on a second attempt: wake the computer first, with the monitors still asleep, and let the monitors wake afterwards. If the first order produces a normal wake and the second order produces a swap, the fault sits in the wake-timing layer: the computer asked for the displays too early, before one of them was ready. If the swap happens under both orders, timing is not the whole explanation, and the investigation continues.

The wording of the first half of this comparison is worth keeping exact, because it is the comparison the neighbouring single-display guide uses for its own wake-timing test: wake the monitor first, wait until it is fully awake and showing a ready state, and only then wake the computer. The principle transfers directly: a display that is fully awake when the computer asks for it will be counted in the order its wake state supports, while a display that is still waking may be counted late or missed on the first pass. The comparison costs nothing but a few seconds of waiting, and it is the single most informative test in this guide.

Step 4: Run the DisplayPort Against HDMI Comparison

Change both monitors to the same kind of interface, or swap the interfaces between them, and then sleep and wake twice under the same conditions. If the DisplayPort monitor is the one that loses primary status and the HDMI monitor does not, the fault sits in the interface layer, following the sleep behaviour described above: the system sees a sleeping DisplayPort monitor as disconnected, while a sleeping HDMI monitor is usually still recognised. If both interfaces swap in the same way, the fault is not in the interface layer, and the investigation continues.

Two sleeps are needed here, not one, because a single swap after a single sleep can be a coincidence. The rule applied throughout this guide is that a pattern counts as repeated only when it appears under the same wake conditions twice. One swap proves that a swap can happen; two swaps under the same conditions prove that it follows those conditions. The same rule applies to a normal result: one normal wake after a change does not prove the change fixed anything, because the swap may simply not have happened that time.

Step 5: Re-detect, Re-set the Primary Display, and Confirm Twice

After a swap, use the system's display re-detection, then set the primary display back by hand, and then sleep and wake twice to confirm. If the setting holds through both wakes, the fault sits in the settings-retention layer: the setting had been lost or reset, and re-establishing it under clean conditions held. If the next sleep swaps it again, the setting itself was not the problem, and the investigation continues — the re-setting only changed the outcome of the last detection, not the conditions of the next one.

This step is where the most common error in this area is made: re-setting the primary display once, seeing a normal desktop, and declaring the problem fixed. A single re-setting changes only the current assignment. It changes nothing about the wake order, the re-enumeration, or the interface behaviour that produced the swap, so the next sleep can undo it. The double confirmation — two sleeps, not one — is what separates a setting that was genuinely re-established from a setting that happened to survive one wake by chance.

Step 6: Run the KVM, Dock, and Virtual-Display Comparison

Bypass the KVM switch or dock and connect the monitors directly to the computer, then sleep and wake under the same conditions. If the direct connection wakes normally, the fault sits in the KVM or dock layer: switching a KVM or plugging in a dock triggers re-enumeration, and a switch or dock that presents the displays in a different order each time will produce a different counting order each time. If the direct connection still swaps, the KVM or dock is not the layer at fault. Separately, disable any virtual display and try again; a virtual display taking part in the enumeration can shift the counting order, and removing it from the enumeration is a clean way to test whether it was involved.

As with every other step, only one thing should change at a time. Bypassing the dock and changing the interfaces and updating the driver in the same attempt, and then watching a normal wake, says nothing about which of the three mattered. The bypass comparison is cheap and decisive precisely because it changes one thing: whether the KVM or dock is in the path.

Step 7: Change Cables and Ports, Compare Drivers, Then Seek Inspection

Under the same wake conditions that produce the swap, change the cable, and then change to another port of the same kind on the graphics card, testing after each change. Perform a clean installation of the driver, with the version chosen against current official guidance rather than on the assumption that the newest version is correct. If the swap still happens on every sleep after all seven steps, take the full record for inspection: the baseline (which monitor was primary, which one it became), the wake-order comparison result, the DisplayPort against HDMI result, the re-setting result, and the KVM or dock comparison result. That record is the difference between an inspection that starts from the beginning and one that starts from the evidence already gathered.

Inspection is charged under the website's published three-tier pricing of HK$400–2,800, with the actual price confirmed after inspection. The shop is at Room 1209, Dali Plaza, Shek Mun; phone 2186 8010, WhatsApp 6558 6806. There is no Mong Kok shop and no on-site service.

StepWhat to doResult that narrows the faultNext step
1Check where the taskbar wentTaskbar moved — primary swapped; taskbar stayed — window layoutStep 2, or the window-layout guide
2Record the baseline before changing anythingWhich monitor was primary, which it became, which woke first, interfaces usedStep 3
3Wake monitors first, then computer; then reverse the orderOne order normal, the other swaps — wake-timing layerStep 4 if both orders swap
4Same interface on both monitors; sleep and wake twiceDisplayPort monitor loses primary — interface layerStep 5 if both swap
5Re-detect, re-set primary, sleep and wake twiceHolds twice — settings-retention layer; swaps again — not settingsStep 6
6Bypass KVM/dock; disable virtual displayBypass wakes normally — KVM/dock layerStep 7 if direct connection still swaps
7Change cable and port; clean driver installFault follows one cable, port, or driver versionInspection with full record

Prevention: Making the Next Wake Behave the Same as the Last

Prevention for a primary-display swap is, in practice, prevention of a different wake order. The conditions that produce a swap are the conditions under which the displays wake in a different order or a different state from the time before, so keeping those conditions steady is what keeps the counting order steady.

Wake the monitors before the computer where that is practical, and give them time to reach a ready state before the computer asks for them. Keep the monitors on the same kind of interface where the setup allows it, rather than mixing DisplayPort and HDMI across the two displays, so that the two monitors behave the same way when they sleep. If a KVM or dock is in use, note whether the swap follows a KVM switch or a dock reconnection specifically, rather than sleep in general; a fault that follows one trigger and not another has already named its layer. Where a monitor has a deep-sleep or power-saving setting, note how it is set, because a monitor that is slow to leave deep sleep will be counted late on the next wake.

None of these habits guarantees that the counting order will never change. What they do is make the next diagnosis shorter, because the list of things that changed since the last normal wake is short and known. The seven steps above still apply; they simply have less ground to cover when the wake conditions have been kept steady.

Boundaries: When the Problem Belongs to Another Guide

The primary-display swap shares symptoms with several neighbouring problems, and the boundaries between them are worth stating plainly.

If the taskbar did not move and only the windows moved, that is the window-layout problem after sleep and reconnection — the primary display never changed. If the boot screen appears on the wrong monitor but the desktop is correct once Windows has loaded, that is the firmware layer. If only a game opens on the wrong monitor while the desktop and taskbar are completely normal, that is the game layer, where the choice is made by the game rather than by Windows. If a monitor switches its own input or reports no signal, that is the monitor's firmware layer, where the display itself changes which input it listens to. If resolution or refresh rate drops after waking, but the primary display does not change, that is the single-display wake problem, where the display wakes into a fallback mode; that guide is expressly limited to a single display, and a multi-display swap is outside its scope. If the swap happens only once in a while rather than every time, record the wake source and the power state of each monitor on that occasion, and see whether the swap follows one particular wake condition; an occasional swap should not be ignored simply because it does not happen every time. If the swap happens on a cold start after shutdown, but waking from sleep is normal, that is a different start-up state problem, not this one. And if there is only one display, there is no primary display to swap, and this guide does not apply at all.

The boundary that most often causes confusion is the one with the window-layout guide, because the two symptoms look alike at first glance: in both cases, the desktop looks rearranged after waking. The test that separates them is Step 1, and it takes seconds: the taskbar is the evidence for the primary display, and windows moving without the taskbar is not a swap.

Six Misconceptions

1. A swapped primary display means the user clicked the wrong setting. It does not. Sleep or reconnection can make the system re-enumerate the displays on its own, and a change in counting order can change the primary assignment without the user touching anything.

2. Windows moving means the primary display swapped. It does not. In the window-layout problem, the windows move and the primary display stays the same. The taskbar is the evidence for the primary display: only if the taskbar moved with the windows did the primary assignment change.

3. A game opening on the wrong monitor means the primary display swapped. It does not. A game opening on the wrong monitor is a game-layer choice, with the desktop and taskbar completely normal; a primary-display swap is a Windows-layer reassignment, visible without any game running, with the taskbar moved.

4. A monitor switching inputs by itself means the primary display swapped. It does not. A monitor switching inputs is the monitor's firmware changing which input source it listens to; a primary-display swap is Windows reassigning display identities after re-enumeration. The two layers are different, and both monitors have a picture in a swap — only their primary and secondary roles have exchanged.

5. Re-setting the primary display once means the problem is fixed. It does not. Setting it by hand only changes the current assignment; it changes nothing about the counting order at the next wake. If the next sleep swaps it again, the same wake condition has most likely repeated, and finding which wake condition that is remains the work to do.

6. A more expensive cable will definitely fix it. It will not. The cable is only one of five layers, and until the wake timing has been excluded, changing the cable may solve nothing. A cable comparison has to be run under the same wake conditions that produce the swap; otherwise a normal wake after a cable change proves nothing about the cable.

Sources

External sources are cited here by source and date only, as published material consulted for this guide, not as testing carried out by this site. unstuckguide.com, "Monitor Order Swaps After Sleep on Windows", 28 October 2026. ASUS official FAQ 1044064, on DisplayPort and HDMI sleep behaviour. windowsdigitals.com, "Stopping Windows 11 from Resetting Monitor After Sleep", on the temporary multi-monitor manager resetting settings after waking. Microsoft Q&A, "Windows 11 Display settings change on their own", a public forum report of a primary display changing by itself after waking from sleep. Neighbouring guides on this site are referred to by subject for boundary purposes only; their mechanisms are not reproduced here.

FAQ

After waking from sleep my primary display switched from one monitor to the other by itself — did I click the wrong setting?

Not necessarily. When the system wakes or reconnects, Windows re-enumerates the displays; the monitor that wakes first gets counted first, and a change in counting order can change the primary display assignment, without the user clicking anything.

How do I tell whether the primary display really swapped, or only the windows moved?

Look at which monitor the taskbar moved to. If the taskbar moved, the primary display genuinely swapped; if the taskbar did not move and only the windows moved, it is the window-layout problem in #267, and the primary display did not change.

Why does it only swap after sleep, when everything is fine during normal use?

Because the swap follows the sleep wake-up: when the system wakes, the whole display chain has to be re-enumerated, and which monitor wakes first and which wakes later decides the counting order. During normal use there is no re-enumeration, so no swap happens.

What is the difference between DisplayPort and HDMI after sleep?

When a DisplayPort monitor sleeps, the system sees it as disconnected, and the windows and taskbar move to the monitor that is still connected; when an HDMI monitor sleeps, it is usually still recognised. Changing both monitors to the same kind of interface and trying again can separate out whether it is an interface-layer problem.

What does waking the monitors before waking the PC tell me?

This is the wake-order comparison: wake the monitors first, wait until they are fully awake and showing a ready state, and only then wake the computer. If waking is normal twice under this order, it points to wake timing — the computer asked before the monitors were ready.

If I set the primary display again, is it fixed?

No. Setting it by hand only changes the current assignment, and changes nothing about the counting order at the next wake; if the next sleep swaps it again, the same wake condition has most likely repeated, and finding which wake condition that is remains the key.

Is a game opening on the wrong monitor the same thing as the primary display swapping?

No. A game opening on the wrong monitor is a game-layer choice problem (#436), with the desktop and taskbar completely normal; a primary-display swap is a Windows-layer matter, visible without opening any game, with the taskbar moved.

How is the monitor switching inputs by itself different from the primary display swapping?

A monitor switching inputs by itself is the monitor's firmware automatically changing its input source (EN #301), and the picture may report no signal; a primary-display swap is the identity assignment after Windows re-enumerates, with both monitors showing a picture and only the primary and secondary roles exchanged.

Could my KVM switch or docking station be causing the swap after sleep?

Possibly. KVM switching and dock plugging and unplugging both trigger Windows to re-enumerate the displays. Bypass the KVM or dock and connect directly, then try again: normal when bypassed points to the KVM/dock layer; still swapping when directly connected means it is not that layer.

If all seven steps still leave the primary display swapping after every sleep, what should I bring for inspection?

The baseline (which monitor was primary, which one it became), the wake-order comparison result, the DisplayPort against HDMI result, the re-setting result, and the KVM or dock comparison result. Inspection is charged under the website's published three-tier pricing of HK$400–2,800, with the actual price confirmed after inspection. The shop is at Room 1209, Dali Plaza, Shek Mun; phone 2186 8010, WhatsApp 6558 6806.

Related articles

Related services

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