Solution:
Root Cause: Web Account Manager (WAM) Token Broker Network Timeout
Executing the Activation Troubleshooter requires communication with Microsoft identity servers (
login.live.com and
activation.sls.microsoft.com). If local network proxy rules, modified
hosts files, or corrupted Web Account Manager (
TokenBroker.dll) packages prevent the troubleshooter from establishing a secure TLS handshake, the activation wizard fails to list linked account devices.
Diagnostic Verification:
1Open PowerShell as Administrator.
2Test network connectivity to Microsoft Activation Endpoints:
Test-NetConnection -ComputerName activation.sls.microsoft.com -Port 443
3If TcpTestSucceeded returns False, local network or firewall rules are blocking activation traffic.
Step-by-Step Fix:
1Reset Network Stack and WinHTTP Proxy Settings:
Open Command Prompt as Administrator and run: netsh winhttp reset proxy
netsh winsock reset
ipconfig /flushdns
2Clear Local Hosts File Modifications:
Check C:\Windows\System32\drivers\etc\hosts and ensure entries blocking microsoft.com or live.com are removed.3Re-register Web Account Broker Packages:
In administrative PowerShell, run: Get-AppxPackage -AllUsers *TokenBroker* | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml" -ForceApplicationShutdown}
4Re-run Activation Troubleshooter:
Reboot system (shutdown /r /t 0), open Settings > System > Activation, and click Troubleshoot.Prevention & Long-Term Monitoring:
Ensure third-party telemetry blocking tools or custom DNS sinks (e.g., Pi-hole) do not block official Microsoft licensing subdomains.