How To Fix Quick Assist Not Working On Windows 11 (2026)
Quick Assist usually fails for one of a few reasons: a missing WebView2 component, a blocked Microsoft Store install, an old Windows build, or a network that blocks its servers.
This guide goes through each cause in the order Microsoft’s own pages suggest, starting with the numbered error codes.
Only use Quick Assist with someone you know, because Microsoft warns that tech support scammers ask people to open it.
Quick answer: match your symptom to a fix
| Symptom | Most likely cause | First fix |
|---|---|---|
| Quick Assist will not open | Edge WebView2 is missing or broken | Update Microsoft Edge, then install WebView2 |
| Message says WebView2 is not installed | WebView2 missing | Install WebView2 from Microsoft |
| Error 1001, 1002, 1003 or 1004 | Component or WebView2 problem | See the error code table below |
| Quick Assist is not in the Microsoft Store | Old Windows build or a managed PC | Install the latest Windows updates |
| Store install fails | Damaged Store cache, date, or region settings | Run wsreset.exe and check date and region |
| Cannot connect after the code is entered | Network blocks the service | Allow HTTPS on port 443 to Microsoft’s endpoints |
What Quick Assist error codes 1001 to 1004 mean
Microsoft lists four error codes that appear in a dialog box when Quick Assist cannot install or run.
| Code | Meaning |
|---|---|
| 1001 | Quick Assist could not initialize one of its internal components. |
| 1002 | Quick Assist could not load WebView2. |
| 1003 | Quick Assist could not install WebView2. |
| 1004 | Quick Assist could not update WebView2 because of a Microsoft Edge group policy setting. |
Microsoft gives no extra steps for 1004, so on a work or school PC the fix is to ask the IT administrator who manages Edge.
Fix 1: Make sure Microsoft Edge is installed and updated
Quick Assist uses the Edge browser control, so a working Edge install usually means Quick Assist will run.
- Confirm Microsoft Edge is installed on the PC.
- Update Edge to the latest version.
- Open Quick Assist again.
If it still will not start, or you see a message that WebView2 is not installed, move to the next fix.
Fix 2: Install Microsoft Edge WebView2
WebView2 should already be on Windows 11 and on any PC with Edge, so this fix mainly applies when it is missing.
- Download WebView2 from the consumer download page that Microsoft links from its Quick Assist troubleshooting article.
- Run the installer.
- Open Quick Assist again.
If WebView2 is missing, Quick Assist also tries to install it the first time you open the app, which can take longer than usual, so wait for it to finish.
Fix 3: Install or reinstall Quick Assist from the Microsoft Store
The current Quick Assist comes from the Microsoft Store.
- Select Start, then All apps, then Microsoft Store.
- Search for Quick Assist and select it.
- Select Get or Install, and allow it if prompted.
- Wait until the button changes to Open.
If the PC is managed by a workplace or school, a policy may block the install, and only the IT admin can change that.
Fix 4: When the Store install fails
- Press the Windows key + R to open the Run box.
- Type wsreset.exe and run it to reset the Store cache.
- Install the latest Windows updates.
- Check that your time and region settings are correct.
- Try the Store install again.
If network problems are behind the Store failing, our guide to resetting network settings in Windows 11 may help.
Fix 5: Update Windows if the Store version will not work
Microsoft says some older builds may not support the Store version of Quick Assist.
| Windows build | What Microsoft says |
|---|---|
| Windows 11 version 21H1 | May not support the Store version. |
| Windows 10 LTSC 2019 (1809), 20H2, 21H1, 21H2 | May not support the Store version. |
| Windows 10 builds below 15063 | Need an update before the Store version works. |
Installing the latest Windows updates can provide the original version of Quick Assist instead.
Fix 6: Try another way to open it
- Search the Start menu for Quick Assist.
- Press Ctrl + Windows key + Q.
- Select Start, then All apps, then Quick Assist.
The app uses a newer icon, so if an old shortcut with the previous icon keeps failing, remove it manually and use the new one.
Fix 7: Check the network and the sign-in
Quick Assist needs a connection that allows HTTPS on port 443 for both people.
The main service address is remoteassistance.support.services.microsoft.com, and traffic is encrypted with TLS 1.2.
| Endpoint Microsoft lists | Purpose |
|---|---|
| *.support.services.microsoft.com | Primary Quick Assist endpoint |
| *.trouter.skype.com and edge.skype.com | Chat and connection between the two people |
| remoteassistanceprodacs.communication.azure.com | Chat and connection between the two people |
| *.live.com | Microsoft account sign-in |
| login.microsoftonline.com | Microsoft sign-in service |
The helper must sign in with a Microsoft account or Microsoft Entra ID, while the person getting help does not have to sign in.
Local Active Directory sign-in is not supported.
Why Quick Assist may be blocked on a work PC
Organizations that prefer another remote support tool can disable Quick Assist by blocking the service address.
Microsoft warns that blocking it also breaks Remote Help, because both use the same endpoint.
If your employer manages the PC, ask the IT administrator instead of trying to work around the block.
Fix 8: Remove and reinstall Quick Assist
- Open Settings, then Apps, then Installed apps.
- Find Quick Assist, select the three dots, and select Uninstall.
- Install it again from the Microsoft Store.
Administrators can instead run Get-AppxPackage -Name MicrosoftCorporationII.QuickAssist | Remove-AppxPackage -AllUsers in an elevated PowerShell window.
When the session works but something feels wrong
A working connection does not mean the caller is genuine.
Microsoft says to let a helper connect only if you contacted Microsoft Support or your IT support staff yourself.
If you are unsure who is on the other end, select Leave, and read our guide to using Quick Assist safely on Windows 11.