I have windows 7 rc 64x installed, and RDtabs starts normally and works too.
However, when I open a few tabs to a few servers some do not respond normally,
and give black screens. I have to reconnect again, but when I switch to another server
and switch back, everything is black again on the desktop. When I connect to that
server with mstsc /admin everything works fast.

Have you tried it from a non-W7 machine?

Yeh sure... works great! Wanted to point out that W7 has a problem with RDtabs.. maybe you could fix it.
Tested on W7 with "remote desktop manager" and vRD 2009 and these 2 have no problem.
Now that "remote desktop manager" uses native mstsc 6.0/6.1

Since the release of RDP 6.1, RD Tabs uses the latest version of RDP it finds registered on the system. I'll wait until the RTM of W7 is released to TechNet before doing tests, in case its something addressed in the last batch of fixes. RDP was greatly updated in W7.

Can you post some screenshots?

RTM is already available on technet.

Would like to post some screenshot, but then I would post black screens.
When I open too much tabs, some servers produce black screens when I
first switch to another server and then back. So I choose a favorite, everything is
OK and I login, I switch to another tab, and then back and I get a black screen.
When I click in the left bottom corner I get start, when I are able to start a full screen
app like IE I get the whole screen again... but when I leave the tab again and return
everything is black again... strangely some tabs have these anomalies and some don't.

What UI are you using in W7? I mean are you using classic or Aero? I have a colleague using RD Tabs daily on W7 RC (with Aero) and he hasn't experienced this problem.

I didn't think RTM was available yet on technet. Last I read was something like middle of August. I'll check again to see.

I really want to crack this nut, so thanks for your help in the interim.

I have also seen this from Windows 7 x64 RC. Not only does it consume a lot of local resources but it seems the PC I'm remoted into gets hammered. I'm not sure this is an RD Tabs problem though. I've also seen the native RDP client spike CPU on the target, mostly Windows 2000 Server but some 2003. Also, there seems to be a problem if there is a Cisco router involved where the CPU on the router will be pegged. I'm still trying to troubleshoot different scenarios.


Here is a discussion on Technet to which I submitted my own experience but no new responses:

http://social.technet.mi...3-4eb9-92c3-12a843ce0e35 

That's very interesting. Please keep me updated on the progress. Just FYI, since I last posted, I'm using RD Tabs on W7 x86 and x64 with no problems at all. It's likely that since you discovered the native RDP has the same problem that it's something unrelated to RD Tabs (driver? plugin? something else?), but I'm still interested to see how this plays out. I'm sure you've seen me mention this before, but the RDP host used in RD Tabs is the same COM control that Microsoft uses in the official client and the "Remote Desktops" MMC. So, unfortunately, that also means that the same bugs present in the official app will probably present themselves in RD Tabs as well.

If it is discovered that there is some property/setting/whatever that can be set programmatically as a workaround, I am most willing to add it as a bug fix.