For the past year or two now, Quick Assist was my go to tool for helping family, friends with their Windows computers. I used it to fix email issues, guide people through updates, and troubleshoot problems without needing to be physically present. It was simple, reliable, and always there when I needed it.
Then some time last week, it suddenly stopped working.
Microsoft - Quick Assists App
Nothing I Tried Helped
Like most people, I assumed it was a temporary issue. But no, the problem persists leaving me unable to help anyone with this app.
I tried everything I could think of.
- I restarted Quick Assist on both computers
- I rebooted both systems
- I performed a Repair of the Quick Assist application
System -> Apps -> Installed apps -> Quick Assist -> … -> Advanced Options -> Repair - I Reset the Quick Assist application
System -> Apps -> Installed apps -> Quick Assist -> … -> Advanced Options -> Reset - I uninstalled and reinstalled the application
System -> Apps -> Installed apps -> Quick Assist -> … -> Uninstall
None of it made any difference. The error appeared instantly every single time. What made this more frustrating was that nothing had changed on my side. The same setup had worked perfectly for quite some time. All the PCs involved were running Windows 11, setup to automatically update themselves (so up-to-date), running TLS, no VPNs involved, no proxy servers involved, …
Moreover, if there was a ‘security’ issue on the helper side, why does it not get flagged when the application is launched? Why does it allow me to log in and generate a code for the other user? It isn’t until the other user enters the code and the 2 apps try to connect that the problem actually arises.
Also, when I reviewed the Event Logs of the helper PC, all the Quick Assist events display ‘The operation completed successfully’. Not one warning, not one error was listed. If there was an issue on the helper PC shouldn’t that PC be flagging that there’s a problem!
It’s all just odd.
Looking for Answers Online
After exhausting local troubleshooting, I searched online and quickly realized I was not alone. Many people were reporting the exact same issue, often while trying to help parents, grandparents, or coworkers.
One of the most relevant discussions I found was on Microsoft Learn, where multiple users described the same sudden failure and identical error message. You can find that discussion here.
What surprised me most was learning that this behavior appears to be intentional. According to responses from Microsoft representatives, this change is tied to increased security requirements rather than a traditional bug.
… However, this behavior is intentional and was introduced to enhance protection for users and organizations by enforcing stricter authentication and identity validation.
Microsoft (Daphne Huynh - Microsoft External Staff)
A Security Change Without Clear Guidance
From what I could gather, Microsoft has adjusted how Quick Assist validates secure connections. Unfortunately, the error message provides no guidance on what requirement is missing or how to fix it.
In several replies, Microsoft points users toward a different tool called Remote Help.
For a more secure, consistent, and supportable remote assistance experience, we recommend transitioning to Remote Help.
Because Quick Assist is no longer recommended for enterprise use in managed environments. Hence, this solution is designed specifically for enterprise scenarios and offers enhanced identity verification, improved session control, and seamless integration with Microsoft Intune.
Microsoft (Daphne Huynh - Microsoft External Staff)
The problem is that Remote Help requires managed devices and Intune, which makes it impractical for helping friends and family at home. InTune is an Enterprise Level feature and not one that consumer users will have.
Another useful article I came across was published on Windows Forum. It discusses possible causes and checks, though it also confirms that there is no guaranteed solution.
What I Learned Along the Way
While reading through community posts and troubleshooting guides, a few common themes kept appearing.
- VPN or proxy connections may interfere with Quick Assist
- Firewall or DNS filtering can block required Microsoft services
- Modern TLS is required (but this is already the case with Windows 10/11 systems)
- Incorrect system date or time can break secure connections
The biggest problem is that none of this is clearly explained by Microsoft within the application itself, none of it applied to my situation and/or none of it resolved the issue in the last 2 attempts I made of using Quick Assist.
Users are left guessing as to what the actual underlying issue is and how they can resolve it.
Where This Leaves Me
At this point, I no longer rely on Quick Assist. Not because I want to abandon it, but because it refuses to work when someone needs my help urgently.
It feels like Quick Assist is slowly being phased out in favor of enterprise focused tools, leaving everyday users behind without a clear replacement.
For now, I have been forced to turn towards third party remote support tools. Below are a few potential alternatives to Quick Assist (in no particular order):
- HoptoDesk: https://www.hoptodesk.com/
- AnyDesk: https://anydesk.com/
- RustDesk: https://rustdesk.com/
- Chrome Remote Desktop: https://remotedesktop.google.com/
- TeamViewer: https://www.teamviewer.com/
- Zoho Assist: https://www.zoho.com/assist/
- ConnectWise Control: https://www.screenconnect.com/
- LogMeIn Pro: https://www.logmein.com/
- Splashtop: https://www.splashtop.com/
- NoMachine: https://www.nomachine.com/
- tailscale: https://tailscale.com/
- UltraViewer: https://www.ultraviewer.net/
and there are other if your search online.
Some are completely free, some are free solely for personal use (paid for commercial usage), some are always paid; so take a moment to review each of their pricing & licensing pages.
Another alternative is you can also use a Microsoft Teams, start a meeting and have the other person share their screen. As long as they use the Desktop App, and not the web browser to make the connection, you can then request control and you will be able to remotely work on their device.
Final Thoughts
If you are seeing this message about minimum security requirements not being met, you are not alone and you are likely not doing anything wrong.
This does not feel like a simple configuration mistake. It feels like a quiet policy change that has made Quick Assist far less useful for personal support scenarios.
It’s sad that once again Microsoft seems incapable of outputting problem free software, nor providing clear and concise error messages that enable users to resolve the root problem. Even worse is how they seem to be completely ignoring the need for such a tool from basic home users whom do not have access to enterprise tools such as InTune.
I hope Microsoft restores Quick Assist as a reliable option for helping friends and family, but at least there are some alternatives.
Go figure?!
What has changed? I couldn’t tell you!