KVM switch + Windows 7 creates monitor switching nightmare

in much the same way as rlee17 stated i was able to 'fix' the problem with the vnc method.  I was not able to choose my native resolution of 1900x1200 via windows nor was i able to do it via nvidia display panel, but i was able to force a 1900x1080 resolution which makes things very tolerable. 

On at least one occasion however the default resolution of 1024x768 somehow took over, and i had to use the vnc connection to force the resolution again. I do not know what caused this to happen but be aware that it might.  Still a much less annoying situation exists now. 

When a monitor (possibly DVI only) 'goes away', either by switching away on a KVM, or turning your monitor off, Win7 freaks out and forces the video resolution to some default. How WIN7 determines what this default resolution will be i do not know, but if we had a reliable method via reg hack or user option, to set this default resolution to what we want it to be, it seems this would do the trick for the majority of users with the issue.  This is what we are doing or trying to do with the vnc method, but it is cluncky, problematic, and unreliable.

Come on MS, give us some help here. TIA!

i just want to add that i was able to "fix" this problem using the the vnc method posted earlier in this thread.

i wasn't able to choose my native resolution of 1920x1200 through the windows screen resolution option, but i was able to force 1920x1200 through the nvidia display panel while i was vnc'ed into my desktop from my laptop.

until microsoft fixes this, this is an acceptable solution to me since it doesn't have any other side effects as far as i can tell.

I don't think so arcanemethods, I've noticed problems like this coming into play in windows operating systems since the advent of DVI. I always suspected active behaviour on plug/unplug of monitors would lead to problems. There is no need for it in a lot of use cases.

I sincerely hope that this doesn't resolve down to a HDCP exposure issue.  If the exposure is within the HDCP spec itself rather than within Windows then MS would be closing a door here that it would be powerless to truly fix while maintaining enforcement.

The long silence from them in this thread concerns me.

After 3 seperate chats with microsoft I am told a patch is very close to fix this.I am not using a KVM but suffer the open windows resized issue.Since I am using my 52 inch sharp aquos I cannot find a monitor driver and windows is using the generic.ATI control panel however sees it as sharp HDMI.

Would I be correct in saying those using VGA do not have this problem?

If so then I beleive this is a poor attempt at HDCP enforcement by Microsoft.

The strange thing is the problem dissapeared for 2 days until I rebooted my PC.I tried to figure out what changed to cause the problem to dissapear but I could not track it down.It sure was nice knowing that it CAN be fixed....somehow.When it was fixed I DID NOT have the annoying device unplugged etc sounding.

I sure hope this gets fixed soon.

I think more likely this, and related display initialisation problems are a result of the software trying to be too helpful with info that is available for DVI connections.

When the PC didnt have the displays status things just worked. I would like to see all display connect/disconnect related functionality able to be disabled for all DVI connections. I would prefer to manually ask the desktop to resynch with display configuration changes when I know I have made a change (rarely) - not whenever the o/s thinks I have changed the configuration just because I have temporarily changed the state of a display.