Overview
netsh.exe on Windows 11 will fail to run and crash if Windows Update KB2693643 (Remote Server Administration Tools for Windows 10) is installed.
Since the Windows SDP client requires netsh.exe to operate, this causes the SDP client to get stuck in the Connecting or Authenticating states.
Troubleshooting
- In the Event Viewer > Windows Logs > Application, search for netsh.exe crashes with Event ID 1000 or 1001.
-
Verify that Windows Update KB2693643 (Remote Server Administration Tools for Windows 10) is installed under Settings > Update & Security > Windows Update > Update History.
You can also check for the update using the PowerShell command
Get-Hotfix | findstr /i "2693643"If the update does exist, the output will be shown similarly in the example below.
PS C:\Users\UserX> Get-Hotfix | findstr /i "2693643"Example-PC Update KB2693643 Example-CATO-PC\cato 1/9/2023 12:00:00 AMIf the update doesn't exist, the command will return nothing.
Solution
The solution would be to uninstall Windows Update KB2693643.
This update causes netsh.exe, which the Windows SDP client requires to update network configuration during the connection, to crash on Windows 11.
You can uninstall the update from Settings > Update & Security > Windows Update > Update History > Uninstall Updates or by running the following Powershell command: wusa /uninstall /kb:2693643
Additional Notes
Starting with Windows SDP Client version 5.15, the client no longer depends solely on
netsh.exe. Instead, it first attempts to use Windows APIs to update network configurations, reducing the risk of encountering this issue.If you need to install Remote Server Administration Tools (RSAT) after removing this update, refer to the official Microsoft documentation:
Install RSAT on Windows 11
2 comments
Issue statement: The CATO SDP client is stuck in the Connecting state (version 5.11.9)
Solution: As per suggestion, we uninstalled the Windows update KB2693643 and it is working fine.
There is a change coming up in 5.14. With this change ENG-52846 Windows SDP client will not depend upon netsh.exe.
Please sign in to leave a comment.