Windows 7: Windows 7 and HTC touch pro

I cant seem to get my touch pro (sprint) to active sync using Windows mwdia device center. I was able to start WMDC but the phone driver is not installed I get the following error: Tried both 7068 and 7077. IN 7077, I cant even get the WMDC to start.
Please chk the attachment for a pic of the error. has anyone else tried to sync their TP with Windows 7?
Thanks

Make sure that when you connect the phone you choose ActiveSync on the menu on the phone and not mass storage device. I have no problems using WMDC and the HTC Diamond (basically the same device).

I have the same proble syncing my touch pro with windows 7 x64 RC1.

I have an HTC Pro and what you have to do is download the mobile device center 6.1 for vista: Page Link - http://www.microsoft.com/windowsmobi...-download.mspx

There is a 32 and 64 bit link on that page. It will give you the same error you got when you install it but when you plug your phone it all will be well and it works fine.

Hope this helps

I have performed this operation several times. I find it strange that ever since i migrated to Windows 7 x64, i have never been able to get it to work. Vista Ultimate x64 worked without any hassles. Searches on all the forums i can find reveal the same trend for a lot of people.

Included is a shot of the error i am getting.

One thing i forgot to add is that i am running bitdefender internet security 2009 on my computer. Could this firewall be blocking the UDP connection to port 990 used by WMDC?

also, check the usb connection settings. USB to PC, enable advanced network functionality. if it's checked, uncheck it. if it is unchecked, check it.

jd

Thanks for the assistance. I have done that too and got the same results. I am really stumped by this problem. I am at my wits end as to what to do here.

Find attached the screen shots of the different stages that i went through before getting the same error on Windows Mobile-Based Device.

I found my AVG firewall was getting in the way. Are you using a 3rd Party firewall?

If so you need to open up the following ports listed in this blog entry.

It looks like the person in this Technet thread had the same issue. I haven't tried the solution posted but you might give it a go.