Here's what I want to know, and don't see in the blog post: Did they fix the problem that caused Visual Studio 2017 to literally not work at all in build 16257? After days of trying different workarounds, and suggestions from Visual Studio community, I ended up resetting 16257, reinstalling VS...