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
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

236 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2014-11-15T23:06:41+00:00

    What a load of nonsense. It's not a driver problem, it's a windows limitation. The simulated monitor is clearly for when Windows is used headless. It appears to be limited to something like 1920x1080. i imagine, back in the day when it was written they never expected 4K displays and they never expected monitors to power down their inputs to reduce power. Welcome to the 21st century.

    Today, more people are buying high res monitors with advanced power saving. They'll have to do something about it sooner rather than later.

    In the mean time don't let windows power down your monitor. Use a blank screensaver.

    If you're really **** about window size and position like me, you can use Sizer.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2014-10-27T12:47:02+00:00

    Started in 2006 with the release  of WDDM . problem is microsoft does not write all the drivers, but there should be more focus on this issue,  only long term solution really is to develop the hardware and operating system under one roof. hence mac or new microsoft made computer.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2014-10-27T03:13:03+00:00

    It has been years Microsnot chooses to ignore the issue. This is the fourth year of it.

    Remember, this posting is just a tip of an iceberg. For every person that writes here, there are many millions that are affected and curse MSFT few times a day, every day. This could not be good for business.

    Was this answer helpful?

    0 comments
  4. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

    Comments have been turned off. Learn more