Remote Assistance failures look mysterious but are almost always one of five boring things: a switched-off setting, a blocked firewall exception, an expired invitation, a mistyped password, or a router standing in the way. Fix them in this order.
Before blaming Windows, remember how many small gates an MSRA connection must pass: the feature must be allowed on the helped PC, the firewall must let it through, the invitation must still be alive, the password must be exact, and both networks must let the two PCs meet. A failure at any gate produces the same dead end, which is why random clicking fixes nothing. Work through the gates in order — each step below either repairs the connection or proves which gate is closed.
Illustrative panel. The first four gates are settings you control; the fifth is the one that sometimes sends you to a relay-based tool.
This is the master switch and the most common culprit, especially on PCs that were "cleaned" or hardened by someone disabling remote features wholesale:
SystemPropertiesRemote and press EnterInvitations are tickets with a lifetime — up to 6 hours by default — and the system does not always say plainly that yours died. If a connection fails mysteriously after a delay, do not debug: create a new invitation, get a new password, and try again. For password failures, read the password aloud in groups over a call and type it exactly as shown. Nine out of ten "it just won’t connect" stories in this category end at this step.
Easy Connect is the option that skips the invitation file and uses a 12-character password instead. Under the hood it depends on IPv6 peer networking, which many home networks and ISPs still do not provide properly — so the option appears greyed out or fails instantly. Do not spend an evening repairing IPv6 for this. The invitation file route does the same job without it, and it is the method this whole guide is built on.
Be honest about what this pattern means: MSRA was designed in the LAN era and has no relay server. Between two PCs on one network it is rock solid. Across the open internet it must negotiate NAT on both ends, and modern realities like CGNAT — where your ISP puts hundreds of homes behind one public address — can make that impossible. Do NOT answer this by forwarding ports or disabling firewalls; that trades a small inconvenience for a real exposure. If cross-internet help is your regular need, use Quick Assist or AnyDesk, whose relays exist precisely to cross this ground.
The video builds the whole flow on a real machine — the fastest way to spot which of your settings differs from a working one.
▶️ Watch Full VideoNo. Invitations created in the modern format work between Windows 10 and Windows 11 machines in both directions. In the Advanced settings there is an option about invitations for older Windows versions — leave the modern default unless you are genuinely helping a very old PC.
Check the two boring gates first: the Allow Remote Assistance tick on the receiving PC, and whether that PC has labelled your home Wi-Fi as a Public network, which silently hardens the firewall. Also confirm the helped person still has their Remote Assistance window open and waiting — closing it quietly cancels the invitation.
It is still part of Windows 11 — start it by typing msra in the Run box rather than hunting through menus, because Microsoft no longer advertises it. If your organisation has removed or blocked it by policy, the supported modern route is Quick Assist from the Microsoft Store, which follows the same invite-and-approve spirit.