A few days ago the Windows Updates made my Notebook unuseable ("Permanent boot loop" is the closest description I can find - thanks, Microsoft) so it had to be installed completely new.
Since then I encountered a problem I never had with VS before:
I'm coding in the VS source code editor without problems.
The coding is "completed" (Meaning there are no "incomplete" source code constructs).
I switch to another application, e.g. copy something to the clipboard or have a look at another document.
When I try to return to VS it is completely "locked" as if it was suddenly in read only mode or if an invisible modal dialog window was opened (No "VS is waiting for some process to be finished" message to be seen); I see the cursor blinking in the VS editor but it does not responsd to any key or mouse click.
Did anyone see such a behaviour before? I had it several times and I'm using Win 10 [10.0.17134.48], VS 2017 Enterprise 15.7.3 with X# 1.2.
My general advice to both my customers and the readers of the IDG articles I write is to postpone Microsoft updates as long as possible. From W10 Professional you can postpone feature updates a full year via Settings and you can postpone security updates a month. Unfortunately users experience more problems by always applying updates than by postponing them (a while).
The incident you both reported is once again a proof that postponing is a good strategy. Not only are most problems solved if you install feature versions later, but also the frequency of problem solving goes down from weekly to a few times a year (I apply the security updates once every 2-3 months).