I have a Visual Studio solution that\'s been around for years. The project is a Visual Studio 2010 project, and I\'ve been able to compile and run the project for years. T
though there is a small chance that IT has pushed a Windows Update
It isn't small. There were two security updates that patched mscomctl this year. Critical ones too, no IT department would skip them. MS12-027 was released in April, MS12-060 was released in August. Particularly the April update is significant, it changed the guids of the COM server. Which means that the interop library (aka wrapper assembly) is no longer valid.
Remove and re-add the dependency to fix.
Beware you might have some trouble with customers that skip these updates. You really should consider getting rid of the dependency. There's nothing in mscomctl that isn't ably wrapped in the .NET framework, all VB6 controls have good replacements.