Ever since I upgraded to the latest release on Windows, I’ve noticed some strange behaviour on my desktop. This behaviour manifested in intermittent and total loss of connectivity to network resources (proxy, internet, local network resources) from my PC.
A reboot fixed this. However, this issue began happening at least twice daily. Each time I would have Lens open.
Today it happened again and I noticed that one of the PIDs owned by Lens.exe was exhausting the entire ephemeral port range on Windows, starving other processes of ports for network communication.
As soon as Lens is closed, connectivity is restored and the port usage disappears. In my brief testing, I’ve seen with Lens open that the ports used tick up by approximately 60-70 additional ports per minute.
After 4-5 hours, the entire range is taken up by Lens.
Has anyone else experienced this? We’ve seen this on at least two desktops in my environment, running the latest Lens release.
Event viewer reports this as:
“A request to allocate an ephemeral port number from the global TCP port space has failed due to all such ports being in use.”
And with Get-NetTCPConnection in PowerShell you can see the PID using each port, the vast majority of which tie back to the Lens process.