Hello
Thank you for posting in Microsoft Community forum.
This issue is indeed a common bug, and many users have encountered curl-related errors while using Web Shield by Avast Antivirus. The error message indicates that curl failed when trying to initialize the security context because the certificate could not be checked for revocation status. This is usually due to Avast's Web Shield interfering with the normal operation of curl while handling SSL/TLS connections.
Solutions:
Use the --ssl-no-revoke flag: As you mentioned, this is a valid temporary solution. By adding this flag, curl will skip the certificate revocation check, thus avoiding errors. While this solves the problem, it does have a security impact, especially when dealing with sensitive data.
Disabling Avast's Web Shield: While this isn't an ideal solution, temporarily disabling Web Shield can avoid this problem when you need to update with curl or git.
Update Avast: Make sure your Avast Antivirus is up to date. Sometimes, a software update may fix compatibility issues with other apps.
Contact Avast Support: If this issue persists, it is recommended to report the issue to Avast's technical support. They may provide a more specific solution or fix this in a future update. Please refer to
Other suggestions:
Use a different antivirus: If this issue is seriously affecting your workflow, consider using another antivirus software that may have better compatibility.
Check your system settings: Make sure your Windows system and curl are up to date, sometimes system updates can affect SSL/TLS processing.
In conclusion, this issue is really annoying, especially when other applications that rely on curl are also affected. Hopefully, Avast will be able to address this issue in a future release.
I hope the information above is helpful.
If you have any questions or concerns, please feel free to let us know.
Regards,
Jill Zhou