TTL expired in transit on Windows client

Normally I get speeds in excess of 100 Mbps on my home wifi on both uploads and downloads.

Speeds during normal operation

This morning, it was down to 6-10 Mbps and I couldn't figure out why. I tried connecting to my router's gateway at 192.168.1.1 but was unsuccessful.

Pinging it returned an odd TTL expired in transit error.

Strangely enough, other laptops and mobile devices on the network were having no problems at all. I tried connecting to another wifi network in my home (yes, I have 3 separate wifi networks with 3 separate routers, but that's a story for a different day), but the results were the same. I even tried restarting my laptop and resetting the Windows network settings, and neither helped. Clearly the problem had something to do with my laptop, not the network.

Online searches returned recommendations of doing a hard reboot of the router or removing the offending rule in the routing table.

I dumped the contents of the routing table via the route print command and compared the results on two separate laptops on the same network. Both were identical. So it wasn't a routing rule issue.

It was only when I did a tracert to the default gateway via tracert 192.168.1.1 did I immediately recognize the problem.

I had installed a Citrix client the day before, and apparently it had still been running and overridden some routing rules. Simply closing it took care of everything.

In the screenshot below, you can see the tracert results before killing the Citrix process and after.