Yes, one thing to look for: there was a specific MS update (sorry , I don't have the exact KB # to reference at the moment) to .NET in January of this year that caused this mess on my system for a couple of days. I held off on the update for almost two months, then decided to install it, but had...