How to fix this error in windows quick assistance: we ended the connection because teh minimum security requirements on the helper side were not met

Hello Robinson Lopera, thanks for posting this in the community.

This error usually appears when the device does not meet Microsoft’s security requirements during a Quick Assist session. Common causes include outdated or disabled TLS protocols, interference from VPNs or proxies, incorrect system time, corrupted Quick Assist app files, blocked access to Microsoft’s remote assistance servers, or restrictive Group Policy or enterprise settings.

One of the most important steps is to ensure your system clock is correct. Even a few minutes of difference can break the secure handshake required by Quick Assist. You can resync the time by going to Settings, opening the Time & language section, selecting Date & time, toggling the “Set time automatically” option off and then back on, and confirming that the timezone is set correctly.

Quick Assist also requires TLS 1.2 or TLS 1.3 to be enabled. If your organization has disabled these or is still enforcing older TLS versions through policies, the connection will fail. If you’re on a managed or corporate device, this may require your IT admin’s assistance.

You should also verify that your system can reach Microsoft’s Remote Assistance servers. Open PowerShell and run the following command:

Test-NetConnection -ComputerName remoteassistance.support.services.microsoft.com -Port 443

If the test fails, it means your firewall, network, ISP, or security software is blocking the connection.

If Quick Assist still fails, try repairing or resetting the app through Windows Settings. Open Settings, go to Apps, search for Quick Assist, open its Advanced Options page, select Repair, and if necessary, use Reset to fully refresh the app.

Make sure that all VPN services, proxy settings, secure DNS features (such as Cloudflare or Google DNS encryption), and corporate VPN clients are completely disabled. Many Quick Assist failures are caused by network routing through these services.

If the problem started recently, it could be caused by a Windows Update. You can check Windows Update history in Settings and uninstall the most recent update to see if the issue resolves.

Finally, test the connectivity again using the PowerShell command above to confirm that nothing on the network side is blocking access.

Hope this helps.

Kind regards,

John Oli