Troubleshooting Guide: Error 710 – “TDI Event Done” (TDI Indication Completed Successfully)
Why This Error Happens
Error 710 with the message “TDI Event Done” is technically not a failure — it is an informational status code generated by the Transport Driver Interface (TDI), a legacy networking layer used by older network drivers and protocol stacks in Windows. This event fires when a TDI indication (a notification passed from a lower-level network driver up to a higher-level client, such as a status update about a connection or data availability) completes processing successfully. It typically appears in Event Viewer logs because a legacy driver, VPN client, antivirus network filter, or third-party network monitoring tool still relies on the deprecated TDI model instead of the modern Windows Filtering Platform (WFP), and it gets logged simply as a matter of driver verbosity or debug-level logging left enabled.
Step-by-Step Resolution Guide
-
Confirm it’s informational, not an active error
Open Event Viewer (eventvwr.msc) → navigate to Windows Logs > System, locate the Event ID 710 entry, and check the Level column. If it’s marked “Information,” no corrective action is required — this is expected TDI driver telemetry. -
Identify the source driver generating the event
In the event details pane, check the Source field (commonlytdi,tcpip, or a third-party driver name like a VPN or antivirus network filter). This tells you which legacy component is still using TDI hooks. -
Update or remove outdated legacy network drivers
- Open Device Manager (
devmgmt.msc) → expand Network adapters. - Right-click the relevant adapter or filter driver → Update driver → Search automatically for drivers.
- If the source is a third-party VPN/firewall/antivirus tool, visit the vendor’s website and install the latest Windows 11–compatible version, since older builds often still ship legacy TDI filter drivers.
- Disable legacy TDI filter drivers if no longer needed
- Press
Win + R, typencpa.cpl, and press Enter. - Right-click your active network adapter → Properties.
- Uncheck or uninstall any legacy “TDI Filter Driver” or outdated protocol entries no longer required (common with old VPN clients).
- Restart the PC to apply changes.
- Adjust Event Viewer logging level (optional)
If the informational logging is cluttering your logs and no functional issue exists, filter it out:
- In Event Viewer, right-click System log → Filter Current Log.
- Exclude Event ID 710 from the view to reduce noise without disabling the driver.
Alternative or Verification Steps
- Verify network functionality: Run
ping 8.8.8.8andipconfig /allin Command Prompt to confirm normal connectivity — since Event 710 is informational, your network should already be working fine. - Alternative fix: If a specific third-party application (VPN, antivirus, or monitoring tool) is the source, uninstall and reinstall it with the latest version to ensure it uses the modern Windows Filtering Platform (WFP) instead of the deprecated TDI architecture.