Home » Windows Server » DebugDiag error “System.Exception: AutoUpdate failed”

DebugDiag error “System.Exception: AutoUpdate failed”

DebugDiag is one of the main tools to troubleshoot performance, memory, and crash related issues. While using this tool, you may run into a pop-up error saying “System.Exception: AutoUpdate failed“.

One or more errors occured
System.Exception: AutoUpdate failed. Please take steps to enable connectivity to the following URL in order to allow Automatic Update Notifications:
System.Net.WebException: The underlying connection was closed: An unexpected error occured on a send. System.IO.IOException: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host

System.Exception: AutoUpdate failed
DebugDiag update error

Solution for DebugDiag AutoUpdate failed error

DebugDiag AutoUpdate functionality checks if there is a new version. If there is, it provides you a link to download it.

For this functionality to work, you should whitelist the following URL in your firewall:

https://debugdiag.azurewebsites.net/

To download the latest version of DebugDiag: Download

You can use predefined rules to collect dump files. DebugDiag also allows you to collect a manual dump. If you notice a service in “Suspended” state after manual dump collection, check this post out: w3wp.exe is Suspended after dump collection

Ned Sahin

Blogger for 20 years. Former Microsoft Engineer. Author of six books. I love creating helpful content and sharing with the world. Reach me out for any questions or feedback.

Leave a Comment