I've written a little utility to address this issue. It's still very thrown together, but opensource, so you can compile from sources if you've got any security concerns.
Hope it works out for you!
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
I have 2 monitors connected to a nVidia FX 580 card running Windows 7 Pro 64-bit. One monitor is connected via DVI and the other via DP (Display Port).
If I turn off the DP monitor, I hear the windows sound indicating hardware was "removed". When I turn the monitor back on, I hear the new hardware sound, windows re-detects the monitor as if I just installed it, and my entire desktop icon layout and any windows I had open are then all rearranged and takes a significant amount of time re-organizing to get back to where I was.
I leave my PC on 24hrs a day for several reasons - and for years have always just turned my monitors off when not in use.
I need to be able to turn off my monitors without windows deciding that I have "removed" a monitor.
I work for a medical imaging software company where we provide complete hardware and software solutions for use in Radiology departments in hospitals. These systems typically have 3 or 4 monitors connected, all via DP these days. Because of the possibility of the users desktop getting messed up if they happen to turn off a monitor, we are unable to install systems with Windows 7.
While many may see this as nothing more then a inconvenience, this is a show-stopper as far as we are concerned. As of yet I have not found a workable solution to this issue.
So here's the question: How do we disable this new behavior in Windows 7 and allow it to understand that the monitor hasn't gone away and that the desktop should not be rearranged simply because the monitor was turned off?
Thank you.
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.
I've written a little utility to address this issue. It's still very thrown together, but opensource, so you can compile from sources if you've got any security concerns.
Hope it works out for you!
I came here to see if someone had found a better solution but it seems not.
It’s sad that I had to resort to using these “monitor detect killer” adapters, especially since a software fix would off been best but at least these solved the problem and I can finally turn off my monitors with no issues:)
I have reviewed this list of gripes, rants, and workarounds. This really is the fault of both Microsoft and hardware vendors. Microsoft Windows is all about ease of use. They place a great deal of emphasis on user-experience. So when people who aren't IT Professionals undock their computer the windows move seamlessly to the active window. So this is actually a "feature" than a technical failure. I've been in IT for over 24 years, so I believe I can say with some expertise that not having this feature would generate a greal deal more mayhem for all markets. Yet the manufacturers of the intelligent displays also made the fatal error of making their device show "always on" to their source regardless if they really are.
Before I offer some suggestions, which I am currently testing, I want to say to those of you who taken to outright indecency in their posts to Microsoft agents on this thread. They're IT professionals like you and I. They aren't the engineers the did this, they're just left to support it the best they can. So for lack of a better term "back off". If you're an home consumer who's frustrated, there is no where in license agreement that says if you're not happy you can speak condescendingly to someone. I'd recommend you remember the rules of common decency still apply to people trying to help you, even on the internet.
Now, so far I've only found a few workarounds, while I research this:
So until MS corrects for this, or the manufacturers figure it our, this is what we've got until someone finds a permanent solution.
Good point about the low NVS 3D performance. Not an issue for me. Primary reason for this card in my case was standard office app use and low cost along with low profile form factor. If 3D performance is needed, I suggest a card should be chosen that is optimum for the primary application it will service.
FYI - in general as video adapter performance and feature sets increase, so do all the associated things that make that possible. Memory allocations, driver quirks, power demands, price of adapter, etc.
By the way, NVS-series of graphcs card are totally unfit for 3D.
Once, by an accident I ordered a computer with it and had to exchange because Autodesk Inventor (and SolidWorks) on a new machine looked horrendous comparing to a 4-year old machine with the same mfg. card (nVidia).
For real high-end and for 3D MANDATORY - use nVidia's other cards (GeForce for consumers, Kepler & beyond for professionals).
NVS card was only designed for 2D applications - business charting, line drawings/sketches, word processing, etc. 3D cards are GeForce cheap, and Kepler or higher - professional