The subject error just pops up for a project that has been running fine for a long time. It comes from IIS Express when running a Web application in Visual Studio. I’m not sure what causes it, but it might have been a side-effect of debugging other errors with Hyper-V and VPN. Looking around, the advice for fixing this was sparse and/or the typical VS repair/rebuild recommendation. Figuring out how to run as Administrator isn’t a valid solution either because it’s less secure and these days I can ......