Exploring what others said in this thread, I may have isolated my own cause of this problem.
A program that installed the .NET Framework 3.5 SP1 when it wasn't necessary. Restore Pointing before that instant seems to have 'solved' the problem, and since we lack any other way to repair a framework corruption in Windows 7, I guess that's all we have

.
It's an idea at least

.