Windows Quick Assist steps before helping someone fix a computer remotely
Checking What Quick Assist Needs Before You Start
Both the helper and the person receiving assistance must run the same version of Windows 10 or Windows 11 with a working internet connection. To access the app, type Quick Assist into the Start menu search box and select the result. Each person needs to start the app and sign into a Microsoft account. The available connection options later depend on which type of Microsoft account the helper uses to sign in.
A connection attempt will fail when one person runs an older Windows version like Windows 8 or 7, as Quick Assist is not available there. When the app does not appear in search results, try the Microsoft Store for a download or consider a different remote support utility. Checking the Windows version and app availability first saves time and avoids a failed connection attempt later.
Generating and Sharing the Security Code Correctly
Once both Quick Assist windows are open, the helper selects Assist another person and then clicks Get a code. A six-digit security code appears on the helper’s screen, and this code expires within ten minutes. The helper must share this code with the person who needs help, usually by phone call, text message, or a separate messaging app. The person receiving help then enters the code into their Quick Assist window under Get assistance and clicks Next.

The security code is single-use and time-sensitive, so reading it back clearly matters. A fresh code is needed when the code expires before the other person enters it; the helper clicks Get a code again to generate one. Do not share the code through a public channel or social media post, because anyone with the code could request a connection. Keeping the code private and confirming it verbally reduces the risk of an unwanted remote session.
Confirming Connection Permissions and Screen Visibility
After the code is entered, the person receiving help sees a permission prompt asking them to allow the helper to view their screen. They must click Allow or Yes for the connection to proceed. On some Windows versions, a User Account Control prompt also appears, and the person being helped needs to confirm that prompt as well. The helper then sees the other person’s screen in the Quick Assist window and can request full control if needed.
A blank screen or an immediate connection drop usually points to a missed permission click or a firewall blocking Quick Assist. The person receiving help should check that Quick Assist is allowed through Windows Defender Firewall by going to Windows Security, Firewall & network protection, and confirming the app is not blocked. Restarting Quick Assist on both sides and repeating the code step often resolves temporary glitches without changing any system settings.

Ending the Session and Revoking Access Safely
When the helper finishes the remote fix, either person can end the session. The helper clicks the Stop sharing button in the Quick Assist toolbar, or the person receiving help clicks the red X in the Quick Assist notification area. Closing the Quick Assist window also disconnects the session. After the session ends, the helper can no longer see or control the other computer, and no background access remains. A practical habit after any remote help session is for the person who received assistance to restart their computer, especially if the helper made system changes or installed updates. The helper should also confirm that the problem is solved before disconnecting, because restarting Quick Assist requires a new code and full setup.
Teaching the other person how to reopen Quick Assist on their own gives them a repeatable way to request help again without relying on memory or written notes.