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: Oldest
  1. Anonymous
    2017-04-21T16:44:26+00:00

    Update: A couple of weeks ago I did some surgery on my machine and only had one monitor connected. Upon going back to a tri-monitor configuration, this problem came back again. I did *mostly* the same scenario as I did before to fix it, a couple of times, but it didn't work. I connected my primary (center) monitor first (the NEC), then my left and right monitors and re-positioned them in Appearance->Display->Screen Resolution, and the monitor identities were ordered 2->1->3 or 3->1->2.

    I read my first post again, and realized the order I originally listed to connect the monitors was LG->NEC->Dell. This is how I have my monitors positioned on my desktop as well.

    So I ran the exact scenario as I originally listed: connect LG->NEC->Dell. After being re-positioned in Appearance->Display->Screen Resolution, monitor identities are in the order 1->2->3 from left to right. Then delete the first two registry entries, and problem solved again.

    But is the order 1->2->3 of the monitors in Windows the key? I'm not sure. One other possibility I'm considering is the connection type: the LG is HDMI, while the other two are DVI. Perhaps HDMI needs first dibs in the registry? Unlikely, since HDMI is just a different implementation of DVI, but weirder things have happened. Maybe someday if I hit this problem again, I'll investigate further.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2017-08-05T14:33:59+00:00

    I got the same problem with Windows 10 since I got my Asus PB278Q monitor connected on HDMI port. Although I don't have the exact same entries under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\GraphicsDrivers\Configuration, your hint is a good start. I check out every entries to replay 1024 x 768 for 2560 x 1440 and it works!

    Thanks Michael.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2017-08-05T17:35:34+00:00

    Thanks! this helped me. Every single time I closed my laptop lid Windows was popping up a graphics not running optimal resolution balloon. It would then resize my Chome windows and basically shift anything else I had open at the time, then go back to full rez, but take a few seconds to do so. SUPER annoying. I scoured the internet for like an hour at least, pissing around with my Nvidia drivers, DDU, updating and even deleting the Intel HD drivers, blah blah blah. 

    Your post led me to the registry editor, and I simply deleted every single display profile in that folder. There was like 50 of them at least. LOL. I do customer training for a living so I've connected to a ton of external monitors. There was no ill-effect by deleting every profile. Though I did backup the registry before doing so. The problem ceased immediately. Not sure why it even began, it only started a few weeks ago. All's well now thanks.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2017-08-10T06:47:40+00:00

    very interesting thread. i was forced by our IT department to change from win7 to win10 last week (august 2017). to the newest patched win10 and newest intel graphics drivers. and guess what???? exactly this problem is still there!!!! so microsoft didn't dare to fix this extremely annoying problem for the PAST 7 YEARS!

    thank you, microsoft!

    Was this answer helpful?

    0 comments No comments