Would I be correct in saying those using VGA do not have this problem?
These problems do seem to be DVI related. I look forward to seeing a patch for these issues.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
I have a problem with Windows 7 and my KVM switch (Iogear model# gcs1764) which is makes switching via KVM an absolute nightmare. The iogear KVM does not use drivers nor are any available on their website.
Here's what happens:
I switch from Win 7 (2 monitors) to XP (1 monitor) via KVM. When I switch back to Win 7 (2 monitors) sometimes Win 7 will throw my desktop to the 2nd monitor (1st monitor goes blank) and opening up display settings only shows the 2nd monitor as existing. It's as if the 1st monitor is now unplugged which it isn't. At this point I have to go into display settings, click Detect, and then it re-detects my 1st monitor and "extends" my desktop back out over 2 monitors. All windows have now been thrown to my 1st monitor and i have to rearrange all my work back across 2 monitors. This is why KVM switching in Win 7 makes my work life a living nightmare. This isn't all of it either...
When everything gets thrown to my first monitor, it takes any windows that were maximized and resizes them to about 1/4 my screen size. Due to compatibility issues between Win 7 and SQL Server Management Studio, Management Studio has a redraw bug that doesn't "re-size" the query window correctly. So even though I maximize the app, when I start typing in the query window my text disappears about 1/4 the way across the whole window. The only way to fix this is to save all my work, close the app, and then re-open the app with all my work. So basically every time I switch computers there's about a 1/5 chance I have rinse and repeat everything I just typed above. Fun times.
So are there any future fixes planned for this? I have tried everything and nothing fixes this problem. I have all the latest Nvidia drivers (my card: Nvidia GTS 250).
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.
Would I be correct in saying those using VGA do not have this problem?
These problems do seem to be DVI related. I look forward to seeing a patch for these issues.
Thanks mortimusmaximus for contacting them about this. I'm keeping my fingers crossed that it happens soon.
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.
ATEN CS-62DU (DVI) KVM
connector 1: NVIDIA ION Win7 64bit (195.62 NVidia drivers)
connector 2: NVIDIA 280 Win7 64bit (195.62 NVidia drivers)
For some inexplicable reason one of the systems works flawlessly (namely ION) while the other one (Nvidia 280 card) displays the widely described behavior (reverting to 1024 resolution, window resize, stuck at low res. Sometimes it even stops displaying Aero and claims that video drivers need to be updated). The only difference in configuration (apart from obvious hardware differences) is that 280 system has got it's monitor driver updated via Windows update while the ION still runs on Generic PnP Monitor with Windows Update being optional and on hold. I refuse to tamper with it at the moment, but I will try to revert to generic display on 280 system and see if it maybe solves the issue.
After reading all posts, I couldn't care less about EDIDs, buying additional adapters or presumably "compatible" KVMs while all it would apparently take is a software/registry change. If it worked before, why can't it work now all of a sudden? Especially if it's not only related to KVMs but also monitors being switched off.
The answer proposed by summerfk while not a solution, does make things tolerable in my case. The objective is to get the monitor settings, which WIN7 has decided to change to while you are switched away, the same as the monitor settings you use when you are switched to the system.
Using VNC (RDP will not work) you connect to system while switched away. In my case, upon connecting i found the monitor was called KVM Monitor and in advanced settings was called a Generic PnP monitor, with max resolution of 1024x768. I first installed my Dell 2408WFP driver which required a reboot to make it recognized. Win7 still wanted native resolution of 1024x768, but by unchecking Hide all modes the monitor cant display, i was able to force the monitor to 1920x1080. I could not get 1920x1200 so any window which is near the taskbar will be moved up about an inch, when I return from being switched away. This is much better than the movement/resizing which happened when it was going to 1024x768 while away.
As i stated this is not a solution and you may find it troublesome getting these settings set for your systems, but i will now be able to tolerate Windows7's freaking out because my display has suddenly disappeared, because i have forced those freaking out settings to something close to my real settings.
At the very least instead of checking this thread twice daily for solutions, I will now check less often. :)
EDIT: This method also does nothing for the occasional time when i switch back, and the resolution is 'stuck' and does not change back to the 1920x1200 which it should be. However again 1920x1080 is not that far from 1920x1200 so it is not a big issue and by clicking the Detect button it switches properly.