I've just noticed on a virtual machine I set up that when the invitation file is created it auto-generates the password, so perhaps the software that generates the password is flaky? Anyone know?

I've got various problems with Remote Assistance: If I try and create an invitation file either to send by e-mail or as a file I get: "A problem occurred that might prevent Remote Assistance from working. Try again or contact your system administrator." This is on a machine running Windows 7 x64 Professional SP1. It looks like something you'd get if the NTFS permissions weren't right but it definitely isn't that. Then another problem is opening an invitation file from another computer - I can open it but it won't accept the password, doesn't seem to matter what the password is. Remote desktop works fine, either to or from the PC. Also, if I offer remote assistance from a Vista machine using the IP address, that works. Not a network problem, I've turned off the firewalls, but I don't think it's a network issue anyway as I can't see what saving an invitation file has to do with the network. Anyone got any ideas?

Okay after trying other Windows 7 machines and logging on as different users I've narrowed this down to my user account on this one machine. It's some sort of file association problem I think with the way MSRA interacts with whatever generates the password. Obviously I've got a workaround by logging on as a different user but I'm not going to wipe and reinstall a machine just for this. Does anyone know what MSRA interacts with on the machine because it's probably just a case of changing a registry entry? There's nothing terribly exotic on this PC but I did use Windows Easy Transfer to go from Vista to it, so I'm thinking something that was moved over in the user profile buggered it up. I'll probably just end up re-creating my own user profile but it would be useful to know what the problem actually is.

Hi, Thanks for posting in Microsoft TechNet forums. Since this issue disappear in another user account, it indicates a faulty user profile and mostly refer to certain corrupt registry value. As you have a working profile, I suggest we compare the registry using Process Explorer and find the root cause. Pay attention to HKEY_Local_Machine\System\CurrentControlSet\Control\Terminal Server HKEY_Local_Machine\System\CurrentControlSet\Control\Remote Assistance Best Regards Magon Liu TechNet Subscriber Support in forum. If you have any feedback on our support, please contact tngfb@microsoft.com 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.

Hi, Thanks for posting in Microsoft TechNet forums. As this thread has been quiet for a while, we assume that the issue has been resolved. At this time, we will mark it as ‘Answered’ as the previous steps should be helpful for many similar scenarios. If the issue still persists, please feel free to reply this post directly so we will be notified to follow it up. You can also choose to unmark the answer as you wish. BTW, we’d love to hear your feedback about the solution. By sharing your experience you can help other community members facing similar problems. Thanks for your understanding and efforts. Best Regards Magon Liu TechNet Subscriber Support in forum. If you have any feedback on our support, please contact tngfb@microsoft.com 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.