Windows 7 moves/resizes windows on monitor power cycle

Anonymous
2010-10-08T22:13:48+00:00

I have a new W7 ultimate install on a new PC (AOpen DEX4501 w intel GM45 graphics). I have installed the latest Intel graphics drivers 8.15.10.2202, and all relevant windows updates.

It is connected via HDMI to a Grundig Misuro HD TV. My resolution is set to 1600x900, windows recommended resolution is 1920x1080 but this displays badly so I don't use it.

When Windows sleeps, or I turn off (then later on) the monitor, most windows are moved/resized to the upper left with the lower right at 1024x768.

Firefox, Excel(2003),Explorer windows resize/move, Outlook(2003) did not move/resize.

I have a Samurize (Gadget like) display on the right which someimes get relocated to the top left, but not this morning. The windows resize/move also happens when Samurize is not running.

I have found three other entries related to this;

They don't seem to have been resolved for a long time.

This is a Windows monitor power managment issue, can it be fixed please it is very annoying.

I won't be recommending W7 to others with such issues outstanding.

Windows for home | Previous Windows versions | Devices and drivers

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments
Answer accepted by question author
Anonymous
2010-10-09T02:55:58+00:00

I have found a work-around.

Using Sysinternals ProcessMonitor I found that Windows was accessing the following Registry path;

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\GraphicsDrivers\Configuration

My system had three entries;

DELF003YY7707BR0MUL_30_07D7_6A^9A3774EB79DEE3E3E38496CC7DF4D936

QHD32000001_31_07D6_D5^63E1ABDD175E7871DCAEB710418A0F75

SIMULATED_8086_2A42_00000000_00020000_1010100^CDE365D1B3F0942F0CF38BFB8E127AB4

Under each is a tree called "00" two of the keys are

PrimSurfSize.cx

PrimSurfSize.cy

Under "00" was another branch also called "00" two of the keys are;

ActiveSize.cx

ActiveSize.cy

The first two of the configs (ie DELF00... & QHD3...) the above keys were 1440x900,

so they were not involved.

The third (SIMULATED...) were set to 1024x768.

I changed these to 1600x900 and the problem was solved.

Further I changed resolution (via control panel) to 1920x1080, the moving/resize issue returned,

but the lower right corner was set to 1600x900, ie the SIMULATED... settings.

So for some reason one of the configs does not get set correctly.

I don't know why there are three configs, I have only ever used one monitor.

Hope this helps someone out there...

Was this answer helpful?

400+ people found this answer helpful.
0 comments No comments

236 additional answers

Sort by: Most helpful
  1. Anonymous
    2015-05-08T05:04:00+00:00

    And if we crank up that fixed resolution by tweaking the registry, why does Windows still push windows away from the right edge? 

    I believe you just need to adjust the STRIDE registry key to fix that behavior as discussed by L.. T.. on page 2.

    Quote:

    "In addition to MichaelAtOz's answer, which also worked for me, there is a third parameter that affects window horizontal placement in that registry hive. It's called 'Stride'. 

    In my computer's registry SIMULATED_10DE_1280 entry (Primary graphics card -- NVIDIA GeForce GT 635) Stride was set to 4096 (4*1024), whereas the DEL monitor entry was set to 10240 (4*2560). I also changed that parameter, and now it seems the problem is completely resolved"

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2015-04-23T23:56:19+00:00

    I have found a work-around.

    Using Sysinternals ProcessMonitor I found that Windows was accessing the following Registry path;

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\GraphicsDrivers\Configuration

    My system had three entries;

    DELF003YY7707BR0MUL_30_07D7_6A^9A3774EB79DEE3E3E38496CC7DF4D936

    QHD32000001_31_07D6_D5^63E1ABDD175E7871DCAEB710418A0F75

    SIMULATED_8086_2A42_00000000_00020000_1010100^CDE365D1B3F0942F0CF38BFB8E127AB4

    Under each is a tree called "00" two of the keys are

    PrimSurfSize.cx

    PrimSurfSize.cy

    Under "00" was another branch also called "00" two of the keys are;

    ActiveSize.cx

    ActiveSize.cy

    The first two of the configs (ie DELF00... & QHD3...) the above keys were 1440x900,

    so they were not involved.

    The third (SIMULATED...) were set to 1024x768.

    I changed these to 1600x900 and the problem was solved.

    Further I changed resolution (via control panel) to 1920x1080, the moving/resize issue returned,

    but the lower right corner was set to 1600x900, ie the SIMULATED... settings.

    So for some reason one of the configs does not get set correctly.

    I don't know why there are three configs, I have only ever used one monitor.

    Hope this helps someone out there...

    I just purchased a new 2560x1440p monitor [only new hardware in my current setup] and was experiencing this as well connected through DP.

    Changing these registry values to my native resolution [2560x1440p] corrected this.

    Thanks for figuring this out and posting, such a shame MS couldn't figure this out themselves.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2015-04-03T16:01:15+00:00

    The reason for all this, I think is mostly related to laptops, and usage on projectors, it need to fallback on some resolution that can be visible when you switch to an projector.

    The fact that this destroys the experience for normal users is on the other hand, totally unacceptable.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2015-04-03T15:09:44+00:00

    I didn't notice mr_andrew's post before. I think he's spot on regarding the interaction of monitor and graphics devices.

    But even if, due to a misunderstanding, Windows believes the monitor was unplugged, why does it fall back on a particular fixed resolution, rather than just stick to the current resolution? And if we crank up that fixed resolution by tweaking the registry, why does Windows still push windows away from the right edge?

    As to the first question, maybe it falls back on VGA output. I think that really old monitors hooked up to VGA couldn't be identified at all. So maybe Windows, to the best of its knowledge, believes you switched to an unknown, undetectable monitor on the VGA port, at the maximum resolution such an antiquity is supposed to handle. So what if I hook up a real monitor on the VGA port, one that advertises a greater resolution, like the very monitor I have already hooked up through the DVI cable? Well, in my case, the problem seems to be solved! There is still an unplug sound, but windows near the right edge stay put.

    Was this answer helpful?

    0 comments No comments