>Could or could not be coincidence. But good to know the fix is simple.

Because the configuration files apply to the VS environment and not to a specific project, all VS projects were not able to be loaded. So, when I searched for the error message, I found some details on how to resolve it. Viv also mentioned he faced a situation like this before. This is not the first time a situation like this is happening after an update.