Recent from talks
Nothing was collected or created yet.
Quick Assist
View on Wikipedia| Quick Assist | |
|---|---|
![]() Quick Assist in Windows 11 | |
| Developer | Microsoft |
| Stable release | 2.0.36.0
/ 16 April 2025[1] |
| Operating system | Windows 10, 11 |
| Type | Remote controlling feature |
Quick Assist is a Microsoft Windows feature that allows a user to view or control a remote Windows computer over a network or the Internet to resolve issues without directly touching the unit.[2][3][4] It is based on the Remote Desktop Protocol (RDP). It is complemented by Get 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, Windows XP and later Windows versions offered a similar feature called Windows Remote Assistance.
Overview
[edit]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 on Windows 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.
Connection
[edit]Quick Assist uses TCP port 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"
History
[edit]The feature was first introduced in Windows 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]

In Windows Vista, Remote Assistance is upgraded with a standalone user interface and based on RDP 6 and Windows Desktop Sharing API.[8] Two systems 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 and XML-based logging. It reduces bandwidth requirements for low-speed connections. NAT traversal allows a session to be established even if the user is behind a Network Address Translation (NAT) device, for example, a router in a home network. Remote Assistance is configurable using Group Policy and supports command-line switches so that custom shortcuts can be deployed.
In Windows 7, Remote Assistance is based on RDP 7. An extra option to connect using Peer Name Resolution Protocol is added, called Easy Connect if IPv6 connectivity is present.[9] With Easy Connect, only a password needs to be shared instead of an invitation file, and two computers can establish a peer-to-peer connection over the local 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 on Windows Server 2008 R2 servers.[12] Remote assistance sessions may be initiated using the Windows Remote Assistance application available on the Start menu under All Apps → Maintenance[13] or by invoking msra.exe from command-line interface.[14]
The original Remote Assistance is included on all releases of Windows 10 as well, but since the Windows 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 called Get assistance and Give assistance. The design is like UWP apps. Unlike Remote Assistant, Quick Assist requires the support person to sign in using a Microsoft 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:
- UAC Elevation
- Remote Assistance Sessions Reports
- Roles Based Authentication (RBAC)
- Management from Intune / the ability to launch from Intune
- Limiting sessions within the organization (Azure AD Tenant)
- Branding
- Conditional Access
- ADFS support
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.
Features comparison
[edit]
| 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 |
See also
[edit]References
[edit]- ^ "Quick Assist". Microsoft Apps. Retrieved 2025-04-16.
- ^ "Get help remotely with Quick Assist in Windows 10". Archived from the original on 2020-07-06. Retrieved 2020-04-09.
- ^ "Overview of Remote Assistance in Windows XP". support.microsoft.com.
- ^ "Windows XP Technical Overview". www.microsoft.com.
- ^ "Remote Assistance and Resulting Internet Communication in Windows 7 and Windows Server 2008 R2". TechNet. Microsoft.
- ^ "Use Quick Assist to help users - Windows Client Management". 4 June 2024.
- ^ a b c How to use remote assistance in Windows XP
- ^ "Writing a Desktop Sharing Application". Enterprise Mobility and Security Blog. Microsoft. 23 March 2007.
- ^ "Peer-To-Peer based Features in Win 7". Archived from the original on 2010-01-23.
- ^ "Improvements to Remote Assistance in Windows 7 - Windows 7 Tutorial". sourcedaddy.com. Archived from the original on 2025-06-14. Retrieved 2025-05-27.
- ^ "Why doesn't windows 7 Remote Assistance support sharing clipboard and file transfer? Are there any work arrounds? [sic]". Windows Client TechCenter. Microsoft TechNet Social. 2010-12-10. Archived from the original on 2012-03-23. Retrieved 2011-11-09.
- ^ "Remote Assistance and Resulting Internet Communication in Windows 7 and Windows Server 2008 R2". learn.microsoft.com.
- ^ "Windows help and learning". support.microsoft.com.
- ^ "Initiate Remote Assistance from a Command Line or a Script". learn.microsoft.com.
- ^ "Quick Assistance: Remotely Control Another's PC / Computer". Windows Call. Archived from the original on 2019-12-30. Retrieved 2019-09-09.
- ^ Popa, Bogdan (9 August 2016). "Microsoft Highlights Its Windows 10 Anniversary Update TeamViewer Killer". Softpedia. SoftNews SRL.
- ^ Srinivasan, Ramesh (2016-08-08). "Using Windows 10's New "Quick Assist" App (Walkthrough)". Winhelponline.
- ^ "Re: Remote help: A new remote assistance tool from Microsoft". 25 November 2021.
- ^ "Remotely assist mobile devices managed by Microsoft Endpoint Manager".
Further reading
[edit]- "Windows Desktop Sharing API". Enterprise Mobility + Security blog. Microsoft. 8 March 2007.
- Torre, Charles (16 October 2006). "Windows Vista Remote Assistance: Under the Hood". Channel 9. Microsoft.
- Tulloch, Mitch; Northrup, Tony; Honeycutt, Jerry (2010). "23: Support Users with Remote Assistance" (PDF). Windows 7 Resource Kit. Redmond, WA: Microsoft Press. ISBN 9780735627000.
Quick Assist
View on GrokipediaIntroduction
Overview
Quick Assist is a built-in Microsoft Windows feature designed for remote viewing and control of another Windows PC over the internet, primarily to facilitate troubleshooting of technical issues.[1] It enables a helper—such as a family member, friend, or IT support professional—to assist a sharer by sharing the sharer's screen and, with permission, taking optional control to diagnose and resolve problems interactively.[2] This tool leverages the Remote Desktop Protocol (RDP) as its underlying technology, secured through HTTPS encryption with TLS 1.2, to establish reliable remote connections.[2] As a default application in Windows 10 and Windows 11, Quick Assist is accessible directly from the Start menu, making it readily available without additional downloads for most users—though Windows 10 installations may prompt retrieval from the Microsoft Store if not pre-installed.[1] For connectivity, it requires an internet or network connection utilizing TCP port 443 for secure data transmission to Microsoft endpoints.[2]System Requirements
Quick Assist requires compatible operating systems: for the sharer, Windows 10 version 2004 (build 19041.1) or later, including all subsequent feature updates, as well as Windows 11 in its supported editions; for the helper, Windows 10/11 or a supported web browser (including on macOS via Microsoft Support).[6][2] It is not available on Windows Server editions, such as Windows Server 2019 or 2022.[7] Both participants must have internet access, but authentication differs by role: the helper must sign in using a Microsoft account (personal, work, or school) or a Microsoft Entra ID for secure session initiation, while the sharer does not require signing in.[2] No explicit hardware minimums are specified beyond the general requirements for the supported Windows versions, which include a 1 GHz or faster processor, 1 GB RAM for 32-bit systems or 2 GB for 64-bit systems, and a DirectX 9-compatible graphics device with WDDM 1.0 driver.[8] For optimal performance, particularly during control sessions, devices with at least 2 GB RAM are recommended to handle remote desktop protocol (RDP) overhead without lag. An internet connection with a minimum bandwidth of around 100 Kbps is sufficient for basic view-only sessions, though 1 Mbps or higher ensures smoother operation for full control and screen sharing.[9] The application depends on the Microsoft Edge WebView2 runtime, which is pre-installed on Windows 11 and most recent Windows 10 updates but may need manual installation on older setups via the official download page.[1] Users should ensure the latest version of Quick Assist is installed from the Microsoft Store; if absent, it can be downloaded directly.[2] Firewall configurations must permit outbound HTTPS traffic over TCP port 443 to Microsoft endpoints, including remoteassistance.support.services.microsoft.com and login.microsoftonline.com, to establish secure connections using TLS 1.2 encryption.[2] Quick Assist supports multi-monitor configurations on the sharer device, allowing the helper to select and view a specific monitor during the session, but it does not natively span the shared view across multiple helper-side monitors without manual window resizing, which may lead to suboptimal viewing if resolutions differ significantly.[10] On ARM-based Windows devices, such as those powered by Qualcomm Snapdragon processors, full support has been available since version 2.0.21.0 in 2023, though some emulated environments like virtual machines may encounter compatibility issues.[11]Usage
User Roles
In Quick Assist, sessions involve two distinct participant roles: the sharer, who is the user experiencing an issue and seeking remote assistance, and the helper, who provides support by connecting to the sharer's device. The sharer opens the Quick Assist app, selects the "Get help" option, enters a 6-digit security code provided by the helper, and explicitly approves the incoming connection via an "Allow" prompt to enable screen sharing.[1] Once connected, the sharer retains control over their device but grants the helper permission to view the screen in real time.[2] The helper role is assumed by the assisting user, who launches Quick Assist, chooses "Help someone," signs in with a Microsoft account, and generates a time-limited 6-digit security code (valid for 10 minutes) to share with the sharer via phone or messaging.[2] Upon successful connection, the helper gains a live view of the sharer's screen and can use basic tools for guidance, such as annotations or a laser pointer. To assume full control—allowing mouse, keyboard, and application interactions—the helper must send a specific request, which the sharer approves or denies through a dedicated dialog.[1] The helper's actions are always limited to the permissions of the sharer's user account on the device.[2] Quick Assist sessions operate in a unidirectional manner, with control flowing only from the helper to the sharer; role switching or bidirectional control is not possible during an active session.[2] Only a single helper can connect to one sharer at a time, ensuring one-on-one interactions without support for multiple concurrent helpers.[12] Consent forms a core security principle, requiring the sharer's affirmative approval for the initial connection and any subsequent control request to prevent unauthorized access.[1] This explicit permission model extends to all interactive features, emphasizing user autonomy. Either the sharer or helper can terminate the session immediately by selecting the "Stop sharing" or "Leave" option in the app interface.[1]Initiating and Connecting
To initiate a Quick Assist session, the person providing assistance (helper) starts by opening the Quick Assist app from the Start menu or by pressing Ctrl + Windows key + Q, then selects the "Help someone" option, which requires signing in with a Microsoft account for authentication.[2] The app then generates a 6-digit security code that is valid for 10 minutes and intended for single use, which the helper shares with the person needing assistance (sharer) via phone, email, or another secure method.[2] The sharer opens Quick Assist similarly, selects "Get help," enters the provided security code in the "Security code from assistant" box, and submits it to request the connection.[1] Upon submission, the sharer sees a prompt to allow screen sharing and must approve it; if the helper requests control, the sharer approves that separately.[1] This process aligns with defined user roles, where the sharer grants access and the helper provides support.[2] Once the code is entered and approved, the connection establishes via a Remote Desktop Protocol (RDP) tunnel over HTTPS on port 443, encrypted with TLS 1.2, supporting both direct local network connections and internet-based ones routed through Microsoft domains such as *.support.services.microsoft.com.[2] The session begins with the helper viewing the sharer's screen in real time. Common connection issues include code expiration after 10 minutes, which requires generating a new code; firewall or network blocks on port 443 or the required Microsoft endpoints, resolvable by checking firewall settings or ensuring internet access; mismatched app versions between devices, addressed by updating Quick Assist; and unexpected session endings due to enhanced security protocols as of mid-2025.[2][13][14] The Quick Assist executable is located at C:\Windows\System32\quickassist.exe, and the app receives automatic updates through the Microsoft Store to ensure compatibility and security.[2][15] Users can verify updates via Settings > Apps > Installed apps by searching for Quick Assist.[13]Features
Core Functionality
Quick Assist's core functionality centers on enabling real-time remote assistance through screen viewing and control once a connection is established with the sharer's explicit approval. The helper can view a live mirror of the sharer's display, which supports multi-monitor configurations via a monitor selector and automatically scales to match varying resolutions for seamless visualization. This mirroring allows the helper to observe the sharer's activities in detail without initial input capabilities.[1][16] Upon the sharer's consent, the helper gains full remote control, permitting keyboard and mouse inputs to interact directly with the remote PC as if operating it locally. Sessions can be paused temporarily by the helper without disconnecting, preserving the connection for interruptions or reviews. Basic interactions are streamlined, including the ability to initiate a reboot.[2][17] For administrative tasks requiring elevated privileges, Quick Assist does not provide native User Account Control (UAC) elevation; instead, the sharer must manually approve and respond to any UAC prompts on their device. Session management defaults to a view-only mode, which the helper can toggle to control mode with the sharer's permission, and includes real-time performance indicators such as connection quality metrics to monitor session stability.[2]Additional Tools
Quick Assist provides several supplementary tools that facilitate enhanced collaboration during remote support sessions, extending beyond core screen viewing and control functionalities. These features enable helpers to guide users more effectively and support diverse user needs. One key tool is the annotation capability, which allows the helper to draw arrows, circles, or add text directly on the sharer's screen to highlight specific elements or provide visual instructions. A laser pointer is also available for temporarily highlighting areas of interest. These annotations appear as temporary overlays that do not alter the underlying content and can be erased or cleared as needed during the session.[2][1] The in-app chat feature offers real-time text messaging between the helper and sharer, powered by Azure Communication Services, allowing for quick communication without interrupting the primary connection. This chat supports ongoing dialogue to discuss issues or next steps, enhancing the interactive nature of support sessions.[2] In 2024, Quick Assist received updates introducing dark mode support for better visibility in low-light environments, an improved chat interface for more intuitive messaging, and a streamlined connection flow to reduce setup time. A November 2024 cumulative update (KB5046613) addressed issues with admin launch and integration with Microsoft Teams. These enhancements aim to modernize the user experience while maintaining compatibility with existing workflows.[2][18][19] For accessibility, Quick Assist is compatible with screen readers such as Narrator, enabling visually impaired users to participate in sessions by having interface elements read aloud, thus ensuring inclusive remote support.[2][20] Device compatibility has been bolstered for Windows 11 environments, including improved support for multi-device setups where sessions can span multiple monitors or connected peripherals, and reboot functionality that pauses the session during restart, requiring the sharer to relaunch Quick Assist for reconnection.[2][17]History
Development Origins
Quick Assist evolved from the Windows Remote Assistance feature, which was first introduced in Windows XP in 2001 to enable invited remote connections over a network using the Remote Desktop Protocol (RDP) for troubleshooting and support.[21] This tool allowed a helper to view or control a user's screen after receiving an explicit invitation, typically shared via email or saved file, emphasizing secure, consent-based peer assistance.[22] Subsequent Windows versions refined Remote Assistance for better usability and performance. In Windows Vista, released in 2007, the feature was upgraded to support RDP 6.1, which introduced enhancements like improved multimedia redirection and network efficiency to handle remote sessions more effectively over varying connection qualities.[23] Windows 7, launched in 2009, further evolved the tool by adding Easy Connect, a peer-to-peer networking option that allowed name-based invitations without relying on email or file sharing, simplifying the connection process through global peer resolution.[22] The motivation behind Quick Assist stemmed from the need to streamline Remote Assistance's often cumbersome invitation workflows, providing a faster, code-generated alternative for immediate peer-to-peer support without legacy dependencies.[21] Planned as an integral part of the Windows 10 ecosystem starting in 2016, it aimed to phase out older tools by mandating Microsoft account authentication for enhanced security and seamless integration across devices.[21] This consumer-focused design later extended to enterprise needs with the introduction of Remote Help in 2021, which built on Quick Assist's framework to incorporate Mobile Device Management (MDM) integration, such as with Microsoft Intune, for supervised remote support in organizational environments.Version Updates
Quick Assist was initially released as a built-in application with the Windows 10 Anniversary Update (version 1607) in August 2016, providing screen sharing, remote viewing, and full remote control capabilities for troubleshooting.[5] The tool was designed as a simplified successor to Remote Assistance, requiring a Microsoft account for secure connections via a six-digit code.[24] By November 2021, Microsoft introduced Remote Help as a public preview feature within Microsoft Intune, leveraging Quick Assist's underlying technology to enable enterprise-grade remote assistance for Azure Active Directory-joined devices.[25] This integration supported role-based access controls and compliance logging, targeting IT support teams in organizational environments. In May 2022, the built-in Quick Assist app reached end-of-support, with Microsoft transitioning it to a Microsoft Store application to improve security and update delivery.[26] Addressing feedback on deployment challenges, particularly in enterprise settings, Microsoft rolled out enhancements via Windows quality updates starting in December 2022, aligning the original app's features with the Store version across Windows 10 versions 20H2 through 22H2 and Windows 11 version 21H2.[27] These updates ensured full compatibility with Windows 11, including seamless integration into the Start menu and hotkey access (Ctrl + Windows + Q).[1] Subsequent updates in 2024 focused on performance and accessibility, with the November Patch Tuesday release (KB5046613) resolving connectivity issues and launch bugs affecting administrative users on Windows 10 and 11.[19] Ongoing patches have continued to refine device compatibility and user interface elements, such as enhanced chat interfaces and interactive annotations, while maintaining backward support for older Windows builds. Windows 10 reached end of support on October 14, 2025, after which no further security or quality updates are provided for the OS, though the Microsoft Store version of Quick Assist remains available for Windows 11.[3] For enterprise use, Quick Assist has been increasingly supplemented by Intune's Remote Help, with integrations prioritizing managed environments by the mid-2020s to align with broader Microsoft Endpoint Manager strategies.[28]Comparisons
With Predecessor Tools
Quick Assist represents an evolution from Microsoft's earlier remote support tool, Windows Remote Assistance, with a narrower platform scope focused on modern operating systems. While Quick Assist is available exclusively on Windows 10 and Windows 11 for both the sharer and helper roles (with limited macOS support for helpers in Microsoft-specific scenarios), Remote Assistance provided broader legacy compatibility, supporting systems from Windows XP through Windows 11.[1][22] In terms of connection simplicity, Quick Assist streamlines the process using a temporary six-digit code shared between users, enabling rapid peer-to-peer connections without additional setup. In contrast, Remote Assistance relied on more cumbersome methods, such as generating invitation files via email or file transfer, or using Easy Connect names for DCOM-based linking, which often required firewall adjustments and user invitations.[2][22] Both tools share core limitations, such as the absence of elevated privilege escalation—remote sessions operate at the user's permission level without administrative bypass. However, Quick Assist introduces enhancements like session pausing, which temporarily halts screen sharing and control for privacy during breaks, a feature not present in Remote Assistance. Neither supports simultaneous multi-helper connections, though Quick Assist allows sequential handoffs more fluidly.[2][29] Performance-wise, Quick Assist leverages a modern peer-to-peer protocol over HTTPS to deliver improved responsiveness, including selectable multi-monitor viewing for remote machines with multiple displays. Remote Assistance, based on older RDP implementations (around version 5.2 to 8), offered basic single-screen handling and similar bandwidth requirements but lacked native multi-screen support, leading to less seamless experiences on contemporary hardware setups.[2][29]| Aspect | Quick Assist | Remote Assistance |
|---|---|---|
| Connection Method | Six-digit code (peer-to-peer) | Invitation file, email, or Easy Connect |
| Control Options | View, full control, annotation, pause, multi-monitor select | View, full control (basic, single-screen) |
| Discontinuation Status | Active and recommended | Legacy; not discontinued but replaced by Quick Assist |

