This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(153.6, 23%, 24%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ET%3C/text%3E%3C/svg%3E)
I do remote support for people, and in the past I've used Team Viewer. I just learned about Quick Assist, and would like to try it.
I first had to enable it as an optional feature since it was not for some reason. After that was done, I tried launching it, and am greeted with a white screen and spinning blue dots. The app sits here and never finishes loading.
I've tried selective startup with System Services only, and resetting Internet Explorer settings to defaults, neither of those options have worked. I did try making another user account on my PC which did work, however this isn't ideal and I'd like to understand why it isn't working on mine without having to do any sort of destructive resets.
I tried watching the process in Process Monitor, and it seems to get stuck directly after sending and receiving some data to a remote IP address. If there are any ideas on how I can troubleshoot this, I'd really appreciate it!
Current system: 20H2 Build 19042.985
References
HI
This is a quick note to let you know that I am currently performing research on this issue and will get back to you as soon as possible. I appreciate your patience.
If you have any updates during this process, please feel free to let me know.
Thank you!
HI tgp1994-1882,
"After that was done, I tried launching it, and am greeted with a white screen and spinning blue dots."
1.When this symptom happen?
after you click “assist another person” option like below picture?
after you just click "quick assist" in start menu?
2."white screen and spinning blue dots"
Is the symptom like below picture?
3.Did your current issue account in local administrators group of problematical win10?
4.Is current local issue computer and remote computer joined to the same AD domain?
1.When this symptom happen?
After opening the app, and a brief blue screen with spinning white dots. I'm not able to get the app to load at all.
Is the symptom like below picture?
Something like that. The spinning dots on my end have a fancier look that goes along with the more modern design style, maybe the screenshot here is a little older.
3.Did your current issue account in local administrators group of problematical win10?
The current issue occurs in an account that belongs to the Local Administrators. When I created a new Standard User, that one works ok.
4.Is current local issue computer and remote computer joined to the same AD domain?
Active Directory is not deployed in my network.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(265.6, 24%, 35%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ERB%3C/text%3E%3C/svg%3E)
I'm working this very issue with Quick Assist and security for internet zones. I've collected a list of sites to place in the Trusted sites list so scripts (guessing JavaScript) can be permitted. However, there is some script running (maybe locally?) that's still producing a dialog box to allow scripts to run.
What I've learned is, if you adjust your Internet zone to high, this disables scripts. For testing, I've used the Custom level... button to change scripts (7th from the bottom) to either allow or prompt. If allowed, it just works. If prompt, I get the box as expected and if I say yes, Quick Assist works.
HOWEVER! I've done as much scouring with GlassWire and ipconfig /displaydns as I can to reveal sites Quick Assist needs to run scripts for so they can be added to the list of Trusted sites where scripts are just allowed. I still get 1 script prompt when QA is launched to receive assistance and 6 more if I sign in to provide assistance totaling 7 prompts. Without these sites in Trusted, I can't even remember how many prompts I get but, IT'S A LOT! I can't for the life of me track down whatever it takes to make them all stop.
My list:
*.akadns.net
*.akamaiedge.net
*.akamaitechnologies.com
*.azure-api.net
*.azureedge.net
*.edgekey.net
*.gammacdn.net
*.live.com
*.lync.com
*.microsoft.com
*.microsoftonline.com
*.msauth.net
*.msecdn.net
*.msidentity.com
*.nsatc.net
*.onestore.ms
*.trafficmanager.net
Roy,
Thank you for posting that! My Internet zone defaults to medium-high, and when I checked the specific configuration items, all script options were set to either enabled or prompt. I tried going through the list and setting everything else to enabled or prompt, and later I just lowered the internet zone to it's lowest security level, "medium". Unfortunately none of these things changed the behavior of Quick Assist. It does look like, in my case, that there's something wrong with my user profile.
Do you have any sites in the Restricted sites list? If QA can't contact some of the sites I posted, you'll get this behavior. Also, many of these settings are Windows profile specific so another profile might not have the setting that's breaking QA.
No, nothing in restricted. I've reset my Internet Properties recently too, so that part should at least be as close to default as possible.
OK. Just so you know, resetting the properties doesn't change sites the registry dumps in there. It only changes the radio options selected. Sites in the zones list are unaffected by the reset.
Maybe see if you can ping all the domains in that list for the broken profile?
Good point about the site lists. I actually had to wipe some from my registry because I couldn't remove them myself from the Internet Properties window. Otherwise I just double checked that they're both empty.
Also great idea about pinging the names. I couldn't get most of them to resolve though, I think I might need a list of individual hosts that it attempts to contact. I capture the process operation and did a comparison of a good result vs. bad result in some other posts I made in this topic. I'm trying to find where it is but I'm not seeing it. To summarize, during a bad start, QA would try to reach out to a few different IPs over TCP then give up. I verified that they were reachable, so it almost seemed like there was something on my end confusing QA. Still a mystery to me - I've been pouring over the capture logs from ProcMon trying to figure out what's triggering this bug, but nothing has really jumped out at me. I can see QA querying different registry keys in my hive, but for the most part the results seem to be identical to the good profile. I wish I had access to the source of QA, unfortunately it looks like it's built in C/C++ so my usual .Net reverse engineering won't work here.
I want to just post an update here. At some point, the Quick Assist app has started working. I can't see any program versions so I don't know when it changed, but at any rate I can now use it on my main user account. Thank you @Andy YOU for all of your help!
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(3.2, 73%, 10%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EK%3C/text%3E%3C/svg%3E)
]