Launch Remote Assistance on Windows 11 & 10 [Easy Steps]

In Windows 11, Windows Remote Assistance is not gone — it is just off by default and buried behind different wording than it used to have. Open Windows Search, type remote assistance, select Allow RemoteAssistance invitations to be sent from this computer, then use Invite someone to connect to your PC and help you, or offer to help someone else to send or accept an invitation. Here's the part that surprises people: this "legacy" tool is not abandoned code sitting untouched since Windows Vista. Microsoft patched a real security flaw inside Remote Assistance itself in January 2026, which means somebody at Microsoft is still actively maintaining a feature most guides describe as basically dead.

Jake had a customer standing at the counter with a laptop that wouldn't open his tax software. Jake could have fixed it in ninety seconds over a screen share — except the customer's PC had never had Remote Assistance turned on, and by the time Jake talked him through the settings over the phone, the customer had given up and walked to the shop two towns over. That's the whole problem with this feature in one sentence: it works fine once it's on, and almost nobody has it on.

This is a walkthrough of Remote Assistance specifically — the older, msra.exe-based tool that's been in Windows since Vista — not the newer Quick Assist app, even though Windows lumps them into the same search result. We'll cover turning it on, requesting help, giving help, running it from the command line, the Group Policy setup IT admins use for unsolicited sessions, the firewall rules it actually needs, what's different on Windows 10, and what to do when it flatly refuses to connect.

What Windows Remote Assistance actually is

Windows Remote Assistance lets someone you trust connect to your PC, see your screen, and — if you allow it — take control of your mouse and keyboard to fix a problem, all while you stay signed in and watch what they're doing. It's built into Windows 11 and Windows 10 as its own program, separate from both Quick Assist and Remote Desktop. It runs on a small executable called msra.exe, which is why you'll see that name in error messages, firewall lists, and command prompts throughout this post.

Microsoft's own support documentation still lists it as a current feature for both Windows 11 and Windows 10, and it explicitly notes you can also use Quick Assist for the same purpose. That "also" is doing a lot of work — Microsoft isn't hiding Remote Assistance, but it clearly isn't the tool being pushed anymore either.

Ethan's take: "Remote Assistance earns its keep in exactly one situation — when the person needing help has to stay logged into their own account the whole time, on their own network, with no code exchange and no Microsoft account involved. Outside of that, I tell people to stop fighting with it."

Turn on Remote Assistance in Windows 11 (do this first)

Remote Assistance is off by default on Windows 11. Whoever is going to receive help has to enable it before anyone can connect — there is no way around this step, and it's the single most common reason a session fails before it even starts.

1. Press Win, or click the search box on the taskbar, and type remote assistance.
2. Select Allow RemoteAssistance invitations to be sent from this computer from the results. (Yes, Microsoft's own search result runs "RemoteAssistance" together as one word — that's not a typo in this article, it's how the label actually reads.)
3. This opens the System Properties window on the Remote tab. Check the box for Allow Remote Assistance connections to this computer.
4. Select OK.

That's it — the computer can now both request and receive help. You don't need to repeat this for every session, only the first time (or after certain settings resets).

How to request help (get someone to connect to you)

Once access is turned on, here's how to actually invite someone.

1. Press Win or use the taskbar search box, and type remote assistance again.
2. Select Invite someone to connect to your PC and help you, or offer to help someone else.
3. Select Invite someone you trust to help you.
4. Choose Use Easy Connect if you've never used it before, or select your helper's name if you've used Easy Connect with them previously. To invite someone who isn't already a contact, select Invite someone to help you instead.
5. Follow the on-screen instructions to send the invitation, then wait for your helper to connect.

Ethan explains it to Jake this way: "Think of it like handing someone a spare key that only opens the door for a little while, and only after you've already agreed to let them in. You're not giving up your account — you're watching the whole time, and you can end it the second you're uncomfortable."

How to give help (offer remote assistance to someone else)

If someone has already sent you an invitation, or asked you to connect and help them, the process runs through the same search result.

1. Press Win or use the taskbar search, and type remote assistance.
2. Select Invite someone to connect to your PC and help you, or offer to help someone else.
3. Select Help someone who has invited you.
4. If it's your first time using Easy Connect, select Use Easy Connect. If you've helped this contact before, select their name from the list. To help someone new who isn't in your contacts, select Help someone new.
5. Follow the instructions to open their invitation and connect.

Once you're connected, you'll see their desktop in a window. You can chat with them, and if you need to actually operate their mouse and keyboard rather than just watch, you have to request control separately — the person you're helping always has to grant that permission themselves. Nothing takes over their PC without them clicking Yes.

Launching it from the Run box or Command Prompt

If you'd rather skip the search menu entirely, Remote Assistance has always been runnable straight from a command line, and this still works in Windows 11. Press Win + R to open the Run box, or open Command Prompt, and use msra.exe with a switch:

The /saveasfile option is the one small-business IT folks reach for most — you generate a ticket, drop it on a shared drive or send it over email, and the helper opens it with a matching /openfile command. There's no published, current Microsoft consumer reference that lists every switch for Windows 11 specifically, so it's worth testing the exact command on your build before you build a script or shortcut around it.

Windows 11 UI traps that make this harder than it should be

None of these are Remote Assistance bugs — they're just Windows 11 interface changes that trip people up while they're trying to find the feature.

Right-click menus are condensed

If you're trying to get to a desktop shortcut's Properties or use a legacy context-menu option while setting things up, Windows 11's right-click menu is shorter than it used to be. The classic full menu lives under Show more options, or you can skip straight to it with Shift + F10.

System Properties still lives in the classic dialog

The Remote Assistance toggle isn't in the redesigned Settings app at all — it opens the old-style System Properties window, the same one Windows has used for over a decade. That's normal; you haven't landed on the wrong screen.

Search result wording changed

Older guides tell you to search for "Allow Remote Assistance invitations." Current Windows 11 shows it as one word, "RemoteAssistance," with no space. If you type the old phrasing exactly and nothing comes up, that's why — search a shorter term like just "remote assistance" instead.

Setting up unsolicited Remote Assistance with Group Policy

Everything above is "solicited" Remote Assistance — someone has to invite you before you can connect. If you're supporting a small office and want to be able to jump into a coworker's PC without them sending anything first, that's "unsolicited" or "Offer" Remote Assistance, and it's configured through Group Policy, not the System Properties checkbox.

1. Open the Group Policy editor. On a domain, edit the relevant GPO; on a standalone Pro/Enterprise machine, run gpedit.msc.
2. Navigate to Computer Configuration → Administrative Templates → System → Remote Assistance.
3. Open Configure Offer Remote Assistance and set it to Enabled.
4. Choose whether helpers can only view the screen or can also take control, then click Show under Helpers and add the accounts or groups you want to permit, in the format domain\username or domain\groupname.
5. If you also want solicited invitations to work with a specific ticket lifetime, open Configure Solicited Remote Assistance, set it to Enabled, and set the Maximum ticket time value.

The firewall rules Remote Assistance actually needs

For basic, solicited Remote Assistance between two ordinary home PCs — the "invite someone to help you" flow most people use — Windows generally manages this without you touching a firewall setting, provided you haven't manually blocked msra.exe.

For the unsolicited, Group Policy–driven setup covered above, Microsoft's own policy documentation is specific: if you enable Configure Offer Remote Assistance, you also need a firewall exception on port 135 (TCP) that covers both %WINDIR%\System32\msra.exe and %WINDIR%\System32\raserver.exe, applied for the network profile the connection will use (typically the domain profile in a business network). Without that exception, offering help to a specific computer name or address will fail even though the Group Policy setting itself is configured correctly.

Remote Assistance on Windows 10 — what's different

The good news is that almost none of this changes on Windows 10 — the menu names, the search term, the System Properties checkbox, and the Group Policy path are all the same. Microsoft's current support page for this feature actively lists it as applying to both Windows 11 and Windows 10, and it hasn't split the instructions between the two.

The one thing worth saying plainly: Windows 10 reached the end of its free security update support on October 14, 2025. If the PC you're trying to connect to (or from) is still on 22H2 without Extended Security Updates enrollment, Remote Assistance itself will still run — but you're troubleshooting a machine that's no longer getting Microsoft's monthly fixes, which matters a lot for a feature that literally just had a security patch. If that machine still qualifies for one of Microsoft's free ESU enrollment paths, or if it's genuinely eligible for the free upgrade to Windows 11, that's worth handling before you spend more time on remote support tools.

Windows 11 Home vs. Pro: what actually changes

Jake sells mostly Home-edition laptops out of his shop, so this is the question he asks the most.

Everyday, invite-based Remote Assistance is a Home-edition feature just as much as a Pro one — it's not gated the way Hyper-V or domain join are. The gap only shows up if you're trying to set up unsolicited, IT-style access, since that path runs through Group Policy, and Home doesn't ship with the Group Policy Editor at all. There isn't a documented, consumer-facing registry workaround for the Offer Remote Assistance policy on Home the way there is for some other GPO settings, and it isn't something worth improvising — if you need unsolicited access at scale on Home machines, that's a job for a dedicated remote-support tool, not a registry hack.

When Remote Assistance won't send, connect, or open

This is the section most "how to enable Remote Assistance" posts skip entirely, and it's where readers actually spend most of their time.

Ethan puts it bluntly to Jake: "People assume a tool this old is just sitting there rotting. It got a security fix five months ago. That's not a corpse, that's a feature Microsoft still has to answer for when something's wrong with it."

Remote Assistance vs. Quick Assist vs. Remote Desktop

These three get confused constantly because Windows search sometimes surfaces all of them for similar terms.

Quick Assist's helper side requires signing in with a Microsoft account (or a Microsoft Entra ID in a work setting) before it generates the security code the other person types in. It runs over the internet through Microsoft's own service rather than a direct connection between the two PCs, which is part of why it needs no firewall configuration on either end. It's genuinely the simpler tool for most people reading this — Remote Assistance earns its place specifically when you don't want that Microsoft-account step, or you're the one setting up unsolicited access for an office.

Before you let anyone in

Microsoft's own support page for both Remote Assistance and Quick Assist carries the same warning, and it's worth repeating in plain terms: only let a helper connect if you contacted them, not the other way around. Tech support scams routinely open with an unsolicited call or pop-up telling you your PC is infected, then talk you into opening a remote-access tool so the scammer can "fix" it — and then take control of something they were never invited into.

Jake asks the question most readers are thinking but won't type into a search box: "What if I let the wrong person in and they mess something up before I notice?" Ethan's answer: end the session immediately — closing the Remote Assistance window disconnects the helper on the spot — and if you shared any passwords or clicked anything you didn't recognize while connected, change those passwords right after, from a different device if you can.

Frequently asked questions

Is Windows Remote Assistance still part of Windows 11?

Yes. Microsoft's current support documentation lists it as available on both Windows 11 and Windows 10. It isn't the tool Microsoft promotes first anymore — that's Quick Assist — but it hasn't been removed.

Why can't I find Remote Assistance in the Windows 11 Start menu?

There's no pinned shortcut for it by default. Search for it by typing "remote assistance" into Windows Search, which is the only reliable way to reach it on a fresh installation.

What's the real difference between Remote Assistance and Quick Assist?

Remote Assistance is the older, msra.exe-based tool that needs to be turned on ahead of time and doesn't require either person to sign in with a Microsoft account. Quick Assist is newer, needs no advance setup, but requires the helper to sign in and generates a one-time security code instead of an invitation file.

Do both people need a Microsoft account to use Remote Assistance?

No. Remote Assistance's basic invite flow doesn't require a Microsoft account on either side. That requirement belongs to Quick Assist's helper side, not to Remote Assistance.

Does Remote Assistance work on Windows 11 Home, or only Pro?

The basic invite-based version works fully on Home. The gap on Home is Group Policy: it doesn't include gpedit.msc, so setting up unsolicited (Offer) Remote Assistance for IT-style access isn't available the way it is on Pro.

Why do I get "Your offer to help could not be sent"?

This almost always means Offer Remote Assistance hasn't been enabled through Group Policy on the computer you're trying to reach, or the required firewall exception for port 135 and the msra.exe/raserver.exe programs isn't in place.

Can Remote Assistance work over the internet, or only on the same network?

The invite-based flow is built to work between two PCs regardless of network, using an invitation ticket that carries the connection details. The Group Policy-driven Offer/unsolicited flow is meant for a managed network, such as a domain, where the firewall and permissions are already handled centrally.

Which firewall ports does Remote Assistance need?

For Offer/unsolicited Remote Assistance specifically, Microsoft's policy documentation calls for a firewall exception on TCP port 135 covering msra.exe and raserver.exe. For the ordinary invite-based flow, most home setups don't require you to open anything manually.

How do I launch Remote Assistance from the Run box or Command Prompt?

Use msra.exe with a switch — /novice to request help, /expert to offer it, /saveasfile to create an invitation file, or /openfile to open one someone sent you.

Can I set up unsolicited Remote Assistance without a domain controller?

Group Policy for Offer Remote Assistance can be configured through the Local Group Policy Editor on an individual Pro/Enterprise machine, without a domain, though managing the Helpers list and firewall exceptions this way has to be repeated on every single computer since there's no central policy to push it out from.

Why is "Allow Remote Assistance connections to this computer" grayed out?

A Group Policy setting — specifically Solicited Remote Assistance — is being enforced on that machine, which locks the local checkbox and takes away the option to change it from System Properties directly.

Can the person helping me take control automatically, without asking?

No. Control has to be requested separately from viewing, and you have to approve it yourself before the helper can operate your mouse and keyboard.

Is it safe to let someone connect with Remote Assistance?

It's as safe as the person you're letting in. Only accept a connection from someone you contacted yourself — never from someone who called or messaged you first claiming your PC has a problem, which is a common tech support scam pattern that Microsoft itself warns about directly on its support pages.

How long does a Remote Assistance invitation file stay valid?

That's controlled by the Maximum ticket time value inside the Configure Solicited Remote Assistance Group Policy setting. Past that window, the invitation expires and a new one has to be created.

Did a Windows update actually break Remote Assistance in January 2026?

Microsoft's January 13, 2026 security update fixed a real flaw in Remote Assistance, tracked as CVE-2026-20824, which let an attacker bypass Mark of the Web protections. It was a security fix rather than a feature removal, and Remote Assistance itself remains part of Windows 11 and Windows 10.

Should I just switch to Quick Assist and forget Remote Assistance exists?

For most casual, one-time help calls, yes — Quick Assist is simpler on both ends. Keep Remote Assistance in mind for the specific cases where you don't want a Microsoft account involved, or where you're setting up unsolicited access across several machines you manage yourself.

Revision note. Written August 2026, covering Windows 11 (24H2/25H2) and Windows 10 22H2, both Home and Pro editions. This will need a fresh look whenever Microsoft renames the search result again or changes how Offer Remote Assistance is licensed. If you've been stuck on a grayed-out checkbox for the last hour, you're not missing something obvious — this feature genuinely hides its own settings better than it should.