On my new Windows 7 Ultimate 64-bit machine, I will get an occasional situation where my shift keys don't seem to work correctly in the RDP session, then the local system appears to lock up. Ctrl-Alt-Del to Task Manager, and the mstsc.exe process is eating up memory (can see it going from say 512MB on up to almost 2GB of RAM). CPU for the process is only about 1-2%, yet the entire system seems frozen. If I have a command prompt open, I can pskill the process from there to get back to normal. When this happens, I am doing an mstsc /admin to a Windows 2003 32-bit server. I usually have 2 or 3 RDP sessions open during the workday, and I'd say this bug pops up perhaps once every couple weeks. I've never had this issue doing remote desktop from Windows XP to the same servers.

Run VMMap [1] and look what memory type is used. [1] http://technet.microsoft.com/en-us/sysinternals/dd535533.aspx"A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/

I'm wondering if this is splwow64.exe related. I was having a lot of trouble with mstsc this afternoon and I noticed a process named splwow64.exe was running. Now I can't get mstsc to misbehave and I see that the splwow64.exe process is not running anymore. Edit to add another data point: The default printer on the 32-bit server side was a Xerox network printer that is no longer on the network. Not sure if this has anything to do with it...

Have you run VMMap?"A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/

Yes, but I can't get mstsc to fail.

I'm wondering if this is splwow64.exe related. I was having a lot of trouble with mstsc this afternoon and I noticed a process named splwow64.exe was running. Now I can't get mstsc to misbehave and I see that the splwow64.exe process is not running anymore. Edit to add another data point: The default printer on the 32-bit server side was a Xerox network printer that is no longer on the network. Not sure if this has anything to do with it... Based on my research, the hang occurs if the a 32bit service is started to run in 64bit Operating System, it seems that the printer triggers the splwow64.exe to run and treats it as an application which causes the hang. Although the printer is no longer on the network, but the default printer is stilled configured to use Xerox network printer, please remove the printer and uninstall the printer driver for Xerox on the Windows Server 2003. Best Regards DalePlease 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.