How to Use Quick Assist in Windows 10 Pro
Quick Assist is a built-in Windows tool that lets one person view or control another person’s screen over the internet. It is useful when a colleague, friend, or family member needs help with settings, updates, software errors, or unfamiliar Windows features. The helper can see the remote desktop and, with permission, interact with it using their own mouse and keyboard.
The process is designed for ordinary Windows users. The person requesting help generates a temporary security code, while the helper enters that code in Quick Assist on their computer. The connection is created only after the receiving user approves it, so another person cannot access the desktop simply by knowing the user’s email address or computer name.
Before starting, both computers should have a reliable internet connection and a supported version of Windows 10. If you need broader assistance with installation media, updates, or system settings, the Windows 10 guidance on Windows10Pro.net provides related step-by-step information.
What Quick Assist Does
Quick Assist uses a one-time connection code to link two Windows computers. The person offering assistance is called the helper, and the person receiving assistance is the sharer or recipient. The helper can usually view the screen first, while the recipient decides whether to grant full control.
Screen viewing is suitable when the helper only needs to explain which button to select or identify an error message. Full control is more convenient when the helper must change settings, remove a troublesome application, run a repair command, or guide a complicated Windows Update process. The recipient remains involved and can end the session at any time.
Quick Assist is different from a permanent remote desktop arrangement. It does not create an always-on account, publish a fixed access address, or give the helper ongoing access after the session ends. A new code and approval are required for a later connection.
Prepare Both Windows Computers
Ask the helper and recipient to sit at their computers before beginning. The recipient should close private documents, banking pages, password managers, and other windows that should not be visible. Saving open work is also sensible because troubleshooting may involve restarting the computer or closing an unresponsive application.
Quick Assist may already be installed on Windows 10, but some systems require the app to be updated or installed through the Microsoft Store. Open the Start menu and search for Quick Assist. If it does not appear, open the Microsoft Store, search for the official Microsoft Quick Assist app, and install or update it. Use a trustworthy internet connection and avoid downloading similarly named remote-access programs from unfamiliar websites.
Both users should agree on the support session before the code is created. A person who unexpectedly calls, sends a code, or pressures someone to open Quick Assist may be attempting a technical-support scam. Microsoft support representatives do not generally request unsolicited remote access through random phone calls or pop-up messages.
Create And Enter The Security Code
The helper starts Quick Assist and selects Help someone. Depending on the app version, the helper may need to sign in with a Microsoft account. Quick Assist then displays a temporary six-digit security code. The helper should give this code directly to the recipient through a trusted channel, such as a phone conversation with a known contact.
The recipient opens Quick Assist and selects Get assistance. After entering the six-digit code, the recipient selects Submit or continues to the next screen. The code expires after a limited period, so it may be necessary to generate a new one if the connection process takes too long.
The recipient then sees a permission prompt showing the helper’s name or account information. Check this information carefully before selecting Allow. If the name is unfamiliar, the request was unexpected, or the code came from a suspicious message, select the option to decline and close Quick Assist.
| Stage | Person responsible | What happens |
|---|---|---|
| Open the app | Both users | Each person launches Quick Assist on their Windows computer |
| Generate code | Helper | The helper selects Help someone and receives a temporary code |
| Enter code | Recipient | The recipient selects Get assistance and submits the code |
| Approve connection | Recipient | The recipient reviews the helper information and allows the session |
| View the screen | Helper | The helper can inspect the desktop and explain what to do |
| Grant control | Recipient | The recipient approves mouse and keyboard control if required |
| End access | Either user | The connection stops when either person selects the end-session control |
Share The Screen Safely
After the recipient approves the connection, the helper can view the Windows desktop. The recipient should describe the problem while the helper observes the screen. For a display issue, for example, the helper might ask the recipient to open Settings and inspect Display or Windows Update options without taking control.
If direct interaction is needed, the helper can request control using the relevant Quick Assist button. The recipient must approve this second permission request. Once approved, the helper can move the pointer, select menus, type commands, and open applications on the remote computer.
The recipient can watch the helper’s actions throughout the session. If something unexpected happens, move the mouse, close Quick Assist, or select the control that ends the connection. The helper should explain each significant action before changing security settings, deleting files, uninstalling software, or modifying system configuration.
Some Windows security prompts may interrupt remote interaction. A User Account Control screen can appear on a protected desktop that Quick Assist cannot fully control. In that situation, the recipient may need to confirm the prompt locally. Never approve an elevation request without understanding what action it authorizes.
End The Session And Protect Your Computer
When the problem is resolved, either user can select the button to end or leave the Quick Assist session. The recipient should confirm that the helper’s pointer and screen view have disappeared. Closing the app is an additional way to make sure the temporary connection is no longer active.
The recipient should then review any changes made during support. Check newly installed programs, modified settings, startup items, and downloaded files. If the helper used Command Prompt or PowerShell, ask what commands were run and why. A legitimate helper should be willing to explain the work and leave the computer in a known state.
Quick Assist is intended for supervised support, not for handing over unrestricted access to an unknown person. Do not share passwords, recovery codes, payment details, or personal identification documents while the screen is visible. If a helper asks for those items, terminate the session and change any credentials that may have been exposed.
Fix Common Quick Assist Problems
If Quick Assist cannot connect, check that both computers are online and that Windows is not blocking the app with a firewall or security product. Restarting Quick Assist on both sides can clear a temporary connection error. The helper can generate a new code, and the recipient should enter it exactly as displayed without extra spaces.
An app that will not open may need an update or repair. Open Settings, choose Apps, locate Quick Assist in the installed apps list, and review the available advanced options. Depending on the Windows 10 build, you may see Repair or Reset. Repair attempts to correct the installation while preserving app data; Reset removes local app data and may require the process to be started again.
If the Microsoft Store is unavailable, install pending Windows updates, restart the computer, and try opening Quick Assist from the Start menu again. Security software, work networks, VPNs, and strict firewall policies can also interfere with remote sessions. A network administrator may need to review those restrictions, but users should not disable security protections permanently just to make a remote session work.
When the screen appears black, frozen, or incorrectly scaled, ask the recipient to check the physical display, graphics driver, and Windows display settings locally. A restart may restore screen capture. If the helper can see the desktop but cannot control it, the recipient may not have approved the control request, or a protected User Account Control prompt may require local confirmation.
Good Habits For Remote Support
Use these practices whenever you share a Windows 10 Pro screen:
- Start Quick Assist only after confirming who the helper is and why access is needed.
- Hide private documents, browser tabs, passwords, and financial information before sharing.
- Read every permission request and grant full control only when screen viewing is insufficient.
- Stay near the computer and watch actions taken during the session.
- End Quick Assist immediately when the support task is complete, then review important changes.
Quick Assist works best when the helper and recipient communicate clearly. Describe the error, mention what changed before it appeared, and explain whether the issue affects one account or the entire computer. This information helps the helper choose a safer fix instead of making broad changes without context.
For recurring support, keep a short record of the date, problem, changes made, and whether Windows restarted successfully. That record can help identify patterns involving updates, drivers, applications, or system files. It also makes future troubleshooting faster without requiring unnecessary remote access.
Quick Assist provides a practical way to share a Windows 10 desktop without setting up a permanent remote-access service. Open the app, verify the other person, use the temporary code, approve only the access required, and remain present throughout the session. When the work is finished, end the connection and check the computer. These simple steps make remote troubleshooting more controlled, transparent, and secure.