How to Fix the “Minimum Security Standards Not Met” Error in Quick Assist on Windows 11

Quick Assist is a built-in Windows application that allows users to securely share their screen or provide remote assistance over the internet. It’s widely used by IT administrators, help desk teams, and individuals to troubleshoot Windows PCs without requiring third-party remote desktop software. However, some users encounter the “Minimum Security Standards Not Met” error when attempting to establish a Quick Assist session, preventing the connection from being completed.

This error typically indicates that one or both devices don’t meet Microsoft’s security requirements for Quick Assist. Common causes include outdated Windows versions, an obsolete Quick Assist app, incorrect system date and time settings, missing security updates, unsupported TLS protocols, firewall or proxy restrictions, or organizational security policies managed through Microsoft Intune or Group Policy. In enterprise environments, compliance policies may also prevent Quick Assist from connecting.

Fortunately, there are several troubleshooting methods that can help restore Quick Assist functionality. In this guide, we’ll show you how to fix the “Minimum Security Standards Not Met” error in Quick Assist on Windows 11.

How to Fix the “Minimum Security Standards Not Met” Error in Quick Assist

Before trying the solutions below, ensure that both the person providing assistance and the person receiving it are running supported versions of Windows with an active internet connection.

1. Update Windows 11

Quick Assist relies on modern Windows security features and protocols.

To update Windows:

1. Open Settings.
2. Go to Windows Update.
3. Click Check for updates.
4. Install all available security and feature updates.
5. Restart your computer.

Running the latest Windows version ensures compatibility with Microsoft’s current security requirements.

2. Update the Quick Assist App

The modern Quick Assist application is delivered through the Microsoft Store and receives updates independently of Windows.

To update it:

1. Open the Microsoft Store.
2. Select Library.
3. Click Get updates.
4. Update Quick Assist if an update is available.
5. Restart the application.

Using the latest version helps ensure compatibility with Microsoft’s remote assistance service.

3. Verify the Date, Time, and Time Zone

Incorrect system time can prevent secure authentication.

1. Open Settings > Time & language > Date & time.
2. Enable Set time automatically.
3. Enable Set time zone automatically, if available.
4. Click Sync now.
5. Restart Quick Assist.

Accurate date and time settings are essential for secure TLS connections.

4. Check Your Internet Connection

Quick Assist requires stable internet connectivity.

1. Open a web browser.
2. Confirm that websites load correctly.
3. Restart your router if needed.
4. Switch to another network if possible.
5. Try Quick Assist again.

A stable connection reduces the chance of authentication failures.

5. Sign Out and Sign Back Into Your Microsoft Account

Authentication issues with your Microsoft account can prevent Quick Assist from establishing a secure session.

1. Open Quick Assist.
2. Sign out of your Microsoft account.
3. Close the application.
4. Reopen Quick Assist.
5. Sign in again.
6. Generate or enter a new security code.

This refreshes your authentication session.

6. Repair or Reset the Quick Assist App

Corrupted application data may trigger security-related errors.

1. Open Settings > Apps > Installed apps.
2. Locate Quick Assist.
3. Select Advanced options.
4. Click Repair.
5. If the problem persists, select Reset.
6. Launch Quick Assist again.

Repairing or resetting the app restores its default configuration.

7. Verify Firewall and Proxy Settings

Network security software may block Quick Assist’s communication.

1. Open Windows Security.
2. Go to Firewall & network protection.
3. Ensure Quick Assist is allowed through the firewall.
4. Open Settings > Network & internet > Proxy.
5. Disable manual proxy settings temporarily, if appropriate.
6. Test the connection again.

If you’re on a corporate network, your IT administrator may need to allow the required Microsoft endpoints.

8. Enable TLS 1.2

Quick Assist uses modern encryption protocols to establish secure connections.

To verify TLS settings:

1. Open Control Panel.
2. Navigate to Internet Options.
3. Open the Advanced tab.
4. Scroll to the Security section.
5. Ensure Use TLS 1.2 is enabled.
6. Restart your computer.

Older TLS protocols may no longer meet Microsoft’s security requirements.

9. Check Device Compliance in Managed Environments

If your device is managed by an organization, compliance policies may block Quick Assist.

Review:

• Microsoft Intune compliance policies.
• Microsoft Entra ID device status.
• Conditional Access policies.
• Security baseline settings.

If the device isn’t compliant, contact your IT administrator to resolve the issue.

10. Temporarily Disable VPN Software

Some VPN services interfere with Quick Assist authentication.

1. Disconnect your VPN.
2. Close and reopen Quick Assist.
3. Attempt the connection again.

If Quick Assist works normally, configure your VPN to allow Microsoft remote assistance traffic.

11. Reinstall Quick Assist

If the application installation has become corrupted, reinstalling it may resolve the issue.

1. Open Settings > Apps > Installed apps.
2. Uninstall Quick Assist.
3. Restart your computer.
4. Open the Microsoft Store.
5. Reinstall Quick Assist.
6. Sign in and test the connection.

A fresh installation replaces damaged application files.

12. Verify Microsoft Service Availability

Occasionally, Microsoft’s cloud services may experience temporary issues.

If you’ve tried all other methods:

1. Check whether other Microsoft services are working normally.
2. Wait a short time and try again.
3. Retry the connection using a newly generated Quick Assist security code.

If the issue is caused by a temporary service outage, it will usually resolve once Microsoft’s services are restored.

Conclusion

The “Minimum Security Standards Not Met” error in Quick Assist usually indicates that one or both devices don’t satisfy Microsoft’s current security requirements. In most cases, updating Windows, installing the latest Quick Assist app, correcting your system time, enabling TLS 1.2, repairing the application, or checking firewall and network settings is enough to restore connectivity.If the issue occurs on a managed work or school device, organizational compliance policies or Conditional Access rules may be preventing the connection. By following the troubleshooting methods in this guide, you should be able to identify the underlying cause and get Quick Assist working again for secure remote support sessions on Windows 11.