Take the 2-minute tour ×
Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

After I remote into my desktop machine the monitor will not sleep again until I use the desktop locally. This started several months ago. Hard to say what changed since I don't think I immediately noticed a problem.

When I first remote in the monitor will immediately wake up and display the "remote logged in from blah blah" and will go black after the configured sleep time, but is still powered on.

This is on an nvidia card and Vista SP1, though it started pre-SP1 and I've gone through a few video driver updates by now.

share|improve this question
    
Why don't you just turn the monitor off when you leave the computer? –  Stefan Thyberg Jul 19 '09 at 16:08
    
Yes, that's my current solution. Additionally, I'd like the hardware to behave correctly. :) –  brian Jul 20 '09 at 2:20
    
I've noticed this too, and I'm using an ATI card, so it's not the video drivers fault. Another things that happens is that maximized windows are displayed behind the task bar, and I have to restart explorer.exe to get maximized windows to "dock" with the taskbar again. –  Anders Öhrt Jul 25 '09 at 7:53
    
An update... I bought a new primary monitor, making the "problem" monitor a second monitor, and the problem went away. Both monitors remain asleep during and after remote desktop sessions. –  brian Aug 12 '09 at 1:05
2  
Please add an answer to your own question with the info from your last comment, and accept it, so the question does not come up as unanswered. –  Joshua Nurczyk Jan 4 '10 at 20:34

1 Answer 1

up vote 1 down vote accepted

Original poster discovered a fix for this issue by adding a new monitor to the system. The new monitor was configured as the primary display, and the "problem" monitor as the secondary.

This indicates the problem was due to some corruption in the display preferences or monitor settings that got reset when the new monitor was added and/or when the displays were reconfigured.

Possible workarounds for the issue:

  • some registry hacking in the right place could reset the corrupted settings. (what's the right place?)
  • deleting the problem monitor's device entry from Device Manager and rebooting might force Windows to reset the corrupted settings.
share|improve this answer
    
posted as community wiki so that others can add to or correct this post. a lot of this is speculation; the "answer" was given by the original poster in comments. –  quack quixote Feb 19 '10 at 1:47

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.