- Apr 24, 2016
Mail from @danb :
Here is the latest VS, there were a couple of small refinements and it should be ready for public release. If we do not find any bugs we will be releasing it to the public early next week.
It might be a good time to mention something. Do you guys know how I have been preaching for years that VS protects thousands of vulnerable processes, including essentially all Windows processes? Follina demonstrated the efficacy of our mechanism, so all that hard work finally paid off.
In other words, there is no need to add msdt.exe to VS’s vulnerable processes, it is already protected, and has been since March 2015. Along with thousands of other vulnerable processes, all automatically, all with zero configuration.