| Quick Assist | |
|---|---|
 | |
 Quick Assist inWindows 11 | |
| Developer | Microsoft |
| Stable release | |
| Operating system | Windows 10,11 |
| Type | Remote controlling feature |
Quick Assist is aMicrosoft Windows feature that allows a user to view or control a remote Windows computer over a network or theInternet to resolve issues without directly touching the unit.[2][3][4] It is based on theRemote Desktop Protocol (RDP). It is complemented byGet Help, a feature introduced in Windows 10 that enables the user to contact Microsoft directly but does not allow for remote desktoping or screen sharing.
Before Quick Assist was introduced in Windows 10, WindowsXP and later Windows versions offered a similar feature calledWindows Remote Assistance.
Helpers offering remote assistance can open multiple simultaneous sessions—one for each remote computer. However, users seeking assistance from helpers can have only one remote assistance session waiting for a connection. Connect invitations can be sent to multiple recipients—any of which may connect. All subsequent connect attempts will be blocked until the first helper disconnects, after which another helper may connect. If the user disconnects the session, the remote assistance application terminates and no further connections are allowed.
Quick Assist is installed by default on Windows clients, but is not available onWindows Server 2008 R2 servers.[5] The name of the tool differs depending on Windows language; a search for "Quick Assist" in the Start menu will locate the tool regardless of the language settings.
Quick Assist requests a code in order to match users to a session. This will allow the giver to access the computer of the receiver in Administrator mode while allowing the receiver to see the choices the giver made.
Quick Assist usesTCPport 443 and communicates with the following hosts:[6]
| Domain / Name | Description |
|---|---|
| *.support.services.microsoft.com | Primary endpoint used for Quick Assist application |
| *.resources.lync.com | Required for the Skype framework used by Quick Assist |
| *.infra.lync.com | Required for the Skype framework used by Quick Assist |
| *.latest-swx.cdn.skype.com | Required for the Skype framework used by Quick Assist |
| *.login.microsoftonline.com | Required for logging in to the application (MSA) |
| *.channelwebsdks.azureedge.net | Used for chat services within Quick Assist |
| *.aria.microsoft.com | Used for accessibility features within the app |
| *.api.support.microsoft.com | API access for Quick Assist |
| *.vortex.data.microsoft.com | Used for diagnostic data |
| *.channelservices.microsoft.com | Required for chat services within Quick Assist |
The Quick Assist binary is located at "C:\Windows\System32\quickassist.exe"
The feature was first introduced inWindows XP as Remote Assistance and based on Remote Desktop technologies.[7] Remote Assistance in Windows XP is integrated into the Help and Support Centre UI and allows sending invitations to the support person by email,Windows Messenger or saving the invitation as a file and transferring the file across through other methods.[7] The computer can be controlled by both, the support person connecting remotely as well as the one sending the invitation. Chat, audio-video conversations and file transfer are available.[7]
InWindows Vista, Remote Assistance is upgraded with a standalone user interface and based on RDP 6 andWindows Desktop SharingAPI.[8] Twosystems administrators can simultaneously connect to a single computer. Remote sessions automatically reconnect after restarting the computer. It also supports session pausing, built-in diagnostics, chat,file transfer andXML-based logging. It reducesbandwidth requirements for low-speed connections.NAT traversal allows a session to be established even if the user is behind aNetwork Address Translation (NAT) device, for example, a router in a home network. Remote Assistance is configurable usingGroup Policy and supportscommand-line switches so that custom shortcuts can be deployed.
InWindows 7, Remote Assistance is based on RDP 7. An extra option to connect usingPeer Name Resolution Protocol is added, calledEasy Connect if IPv6 connectivity is present.[9] WithEasy Connect, only a password needs to be shared instead of aninvitation file, and two computers can establish apeer-to-peer connection over thelocal area network (LAN) or the Internet without a relay server. However, Windows Remote Assistance does not support file transfer and clipboard sharing in Windows 7.[10][11]
Remote Assistance is installed by default on Windows clients, but must be added manually onWindows Server 2008 R2 servers.[12] Remote assistance sessions may be initiated using the Windows Remote Assistance application available on theStart menu under All Apps → Maintenance[13] or by invokingmsra.exe fromcommand-line interface.[14]
The original Remote Assistance is included on all releases ofWindows 10 as well, but since theWindows 10 Anniversary Update, its Start menu shortcut is removed, effectively hiding it from the user. Instead, a new app called Quick Assist is added.[15] It has mostly the same functionality and a similar user interface with buttons calledGet assistance andGive assistance. The design is likeUWP apps. Unlike Remote Assistant, Quick Assist requires the support person to sign in using aMicrosoft account before dispensing help.[16][17]
In November 2021, Microsoft announced a more business-friendly version of Quick Assist, called Remote Help.[18] While later versions of Windows 10 allowed users and technicians to authenticate against Azure Active Directory, this version includes new integrations such as:
While Remote Assistance establishes a Remote Desktop Protocol (RDP) connection to the end user's computer (requires TCP port 3389 to be opened on the client machine and the firewall/NAT/router behind which the machine is), Quick Assist is cloud-based and requires one outbound connection from the helper's PC to the cloud service/Microsoft server, and a separate connection from the cloud service to the machine of the person getting assistance. There are no ports opened on the client device's firewall.
| Feature | Windows Remote Assistance | Windows Quick Assist |
|---|---|---|
| Remote assistance for Windows devices | Yes | Windows 10/11 |
| Remote assistance for MacOS devices | No | No |
| Remote assistance for smartphones | No | No |
| Viewing through device camera | No | No |
| Support of multiple screens on the target machine | Yes (all the monitors or clicking Fit to the size and scroll to selected monitor) | Yes (viewing selected monitor or all of them at once) |
| Keyboard layout used when remotely controlling a machine (the helper needs the keyboard layout to match his/her own computer for efficient assistance) | Using target computer keyboard layout | Using helper's keyboard layout |
| Working with elevated privileges | No (the screen blacks-out and the user has to finish the action instead of the helper) | No[19] |
| Requirement for client software installation | No (installed in Windows by default) | No (installed in Windows by default) |
| Clipboard sharing (copy / paste text between helper's and end user's machine) | No (workaround: pasting via embedded chat window; limited number of characters) | No (workaround: pasting via embedded chat window; limited number of characters) |
| File transfer (between helper's and end user's machine) | No (workaround: via file share or file sharing cloud service) | No (workaround: via file share or file sharing cloud service) |
| Running scripts remotely (e.g. ipconfig) | No (workaround: scripts have to be copied to the remote machine first and executed from there) | No (workaround: scripts have to be copied to the remote machine first and executed from there) |
| Pausing remote control session by the end user (temporarily stopping screen sharing) | No (only cancelling the whole session) | Yes |
