Thank you, that is good to hear. As far as I could see from the log message, it looked like both the 32-bit and 64-bit common controls were accidentally pulled in.
Latest 32-bit TCPView (v4.18) has a bad manifest
I updated to the latest Sysinternals Suite, as of April 3, 2023, and I noticed a message in my Application Event Log:
[249041] SideBySide
Type: ERROR
Computer: mycomputer
Time: 2023-04-04 20:17:18 ID: 78
Activation context generation failed for "C:\Program Files (x86)\SysinternalsSuite\Tcpview.exe".Error in manifest or policy file "?" on line ?.
A component version required by the application conflicts with another component version already active.
Conflicting components are:.
Component 1: C:\Windows\WinSxS\manifests\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.19041.1110_none_a8625c1886757984.manifest.
Component 2: C:\Windows\WinSxS\manifests\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.19041.1110_none_60b5254171f9507e.manifest.
This is about the 32-bit version of TCPView. In Explorer, the icon looks a little strange, since the normal little UAC 'shield' icon overlay is not shown. If you start the executable normally, it does not ask for elevation, and then gives an error that elevation is required. Note that the 64-bit version, TCPView64.exe, has no such issues: it shows the regular UAC icon overlay, and when you start it normally, it shows the UAC dialog as expected. There were no messages in my Event Log regarding the 64-bit executable.