Windows 10 remote assistance is totally borked

This one is a doozie. After the problem descriptions I've tried to spell out some fixes. Hopefully these will get back to MS.

First of all, Windows 7 will not connect to Windows 10 with remote assistance. Not with the helpdesk option by IP address and not with an invitation file. It gives the useless error below and dies.

Windows 7 works to Windows 8.1. I guess it was too much of a surprise to Microsoft that Windows 10 came out all of a sudden and they didn't have time to test it fully.
Problem: Windows 7 remote assistance will not connect to Windows 10
Possible Solutions:

1. Make it compatible *Recommended*
2. Put an error message in the program that will tell the frustrated users their versions are incompatible.

Not acceptable, but Microsoft does it anyway:

1. Cross fingers and hope it's compatible
2. Give a generic error message that doesn't help the user and let them figure it out by themselves. 

Second, once you get in with remote assistance (I did it by installing windows 10 in a virtual machine and using remote assistance from there) you won't be able to help because admin functions have been screwed up. Not disabled, but screwed up. Really.

I needed to remote into a family member's computer to put in the license key because he's not an admin on his domain-joined laptop. Now he's remote, so he connects to my network through a VPN -- and that means he has to stay logged in. If I use remote desktop the VPN connection will drop and I'll get disconnected. In the past (and win 8.1) when anything needed to be done I'd use remote assistance to give permission to install programs or whatever he needed. It worked well once group policy was applied to make the UAC window visible remotely.

You can't seem to elevate the default license key window from the GUI so in this case I needed to open an administrative command prompt to put in the command to change the license key. No big deal. I searched for command prompt, right clicked, and chose run as administrator. Windows presented the box where you would enter your admin credentials. I could see the box, but I couldn't click on it. When I clicked on it, nothing happened. I couldn't give the window focus nor anything within it. I had him click the user name box and that worked to give it focus. I could type in it so I thought the problem was solved. I entered my domain admin username and password and hit enter. Invalid password. Tried again, but had him hit the button, same thing. Tried using a local admin account instead of a domain one. Invalid password. Tried opening a regular command prompt and using runas with domain and local accounts. Invalid password. Finally I gave him the password and had him type it in. Worked first try. So windows either prevents remote users from using credentials on purpose, or it changes the password you enter. Isn't that the darndest thing you've ever heard of?  Let's have admins support users by giving the users admin passwords! Microsoft has done some stupid things but for this one I think they should be awarded a cake.

Once you've given away the admin credentials to the user, you still can't click on the elevated command prompt window to give it focus. They have to click it. Once they do, you can type in it.

Problem: Admins can't click on elevated permission windows
Solution: Fix the interface so admins can give focus to windows running with elevated permissions

Problem: Admins can't use their admin credentials, they have to give them to users to type in
Solution: Fix the interface so admins can type in their own credentials

Microsoft may have snowed the general public with their new half-baked OS but they haven't fooled me. This was my first interaction with windows 10 RTM, and it was miserable. They spend so much money hyping their new product, leverage geeks everywhere to test it for them, and it still turns out to be a broken mess. If only they had enough money to do it right! Oh wait a minute, they do! And that is why I hate Microsoft today. How about you?