Dear all, We have a Windows 7 Professional SP1 x86 and few user names that are connecting to it through Remote Desktop. Sometimes after one username logs off remote desktop is not working anymore - logging in does not work: it asks for password then attempts to log in but it dissapears with no error. The only solution that we found to this is rebooting the machine. There seems to be no error in the logs. Any suggestion on how to fix / debug this issue ? Regards, Dragos

I did searched better and I found this in the logs: Application Information: The Desktop Window Manager was unable to start because a composited theme is not in use. and few System Information logs probably from reboots: The Remote Desktop Services UserMode Port Redirector service entered the running state. The Remote Desktop Configuration service entered the running state. Any ideas ?

I did searched better and I found this in the logs: Application Information: The Desktop Window Manager was unable to start because a composited theme is not in use. and few System Information logs probably from reboots: The Remote Desktop Services UserMode Port Redirector service entered the running state. The Remote Desktop Configuration service entered the running state. Any ideas ?

I suggest you turn off Auto-Tuning since your network device may not work properly with it. Disable TCP/IP “Auto Tuning” in windows 7/vista/windows 2008 R2 http://techibee.com/windows-7/disable-tcpip-auto-tuning-in-windows-7vistawindows-2008-r2/956Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

I suggest you turn off Auto-Tuning since your network device may not work properly with it. Disable TCP/IP “Auto Tuning” in windows 7/vista/windows 2008 R2 http://techibee.com/windows-7/disable-tcpip-auto-tuning-in-windows-7vistawindows-2008-r2/956 Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ” Dear Arthur, I disabled TCP auto tuning but the result is still the same: I can connect the first time, after log off it authenticates but does not log in and closes with no warning. Should I try to disable TCP scaling heuristics as I read on as related ?

I suggest you turn off Auto-Tuning since your network device may not work properly with it. Disable TCP/IP “Auto Tuning” in windows 7/vista/windows 2008 R2 http://techibee.com/windows-7/disable-tcpip-auto-tuning-in-windows-7vistawindows-2008-r2/956 Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ” Dear Arthur, I disabled TCP auto tuning but the result is still the same: I can connect the first time, after log off it authenticates but does not log in and closes with no warning. Should I try to disable TCP scaling heuristics as I read on as related ?

Problem seems to be solved by disabling TCP/IP autotuning and TCP heuristics. netsh interface tcp set global autotuning disabled netsh interface tcp set heuristics disabled I also run Wireshark and noticed that in TCP sequence 27 the Window size is not scaled anymore. Maybe there should be an article about this issue on Technet! The system worked well for over an year and suddenly this error appeared - most probably triggered by an update.

The problem is not solved unfortunately. It worked well for few hours and then the old behavior occurred. What else can I try ? I am open to suggestions. Now I strongly believe that this might be a bug in the Remote Desktop Services.

The problem is not solved unfortunately. It worked well for few hours and then the old behavior occurred. What else can I try ? I am open to suggestions. Now I strongly believe that this might be a bug in the Remote Desktop Services.

Working well for a few hours then reverting to previous behavior is (usually) a solid indicator that group policy is coming back around to refresh policy, and the features you changed are being reset. In my domain every 90 to 120 minutes policies will be applied/reapplied. DAS

Working well for a few hours then reverting to previous behavior is (usually) a solid indicator that group policy is coming back around to refresh policy, and the features you changed are being reset. In my domain every 90 to 120 minutes policies will be applied/reapplied. DAS

Try running "Fix this problem" on the link below http://support.microsoft.com/kb/934430

The problem is solved after Windows performed this May updates: KB2585542, KB2621440, KB2633873, KB2641653, KB2645640, KB2653956, KB2654428, KB2656373, KB2665364, KB2667402, KB2675157 One of them fixed the issue, probably: KB2667402. The error was triggered by running software from SolidWorks. Thank you all for your help.