Update for Microsoft Visual Studio 2015 Update 3

Update for Microsoft Visual Studio 2015 Update 3

This is a cumulative servicing update that provides fixes to Microsoft Visual Studio 2015 Update 3. These fixes address high-impact bugs that were either found by the product team or reported by the community. This update will be released on a recurring basis as new bugs are found and fixed. (New fixes will be added to the previous fixes.)

Download information

This update is available for manual download and installation from the Microsoft Download Center.

Bugs that are fixed in version 14.0.25402.0, released on 06/07/2016

•Issue 1:
There are some instances in which Visual Studio extensions are not automatically updated if a computer is suspended or in hibernation when the task is scheduled to run. This fix changes the task to run as soon as possible after the scheduled start if the time is missed.

The workaround is to manually install the extension.

•Issue 2:
Customers who have Visual Studio 2013 and Visual Studio 2015 Update 2 installed on the same computer may experience issues with automatically updating extensions because of incorrect version targeting. This fix makes sure that the auto-update feature targets the correct version for each product.


Update information

This update can be installed only on computers that have Visual Studio 2015 Update 3 installed. All fixes are included in the one update installer and can't be installed individually.

This update (or an earlier version) may have been installed automatically together with Visual Studio 2015 Update 2 if you installed Update 2 after any release of this update. You can reinstall the update to get the later fixes that are provided in the subsequent releases. You do not have to uninstall the previous update to install a later version.

Update Details

Version: Visual Studio 2015 - File Name: VS14-KB3151378.exe - Date published: 06/07/2016 - File size: 2.4 MB

Installation Instructions

Click this link to start the download, and then use one of the following installation options to install over the Internet:
•Click Run to install now.
•To download an installer that you can run later, click Save. (When you install, the computer must be connected to the Internet.)
•To create a local copy to install offline, click Save, open a Command Prompt window at that location, and then run the .exe file by using the /layout switch.

System Requirements

The system requirements for this update are unchanged Visual Studio 2015 System Requirements. For information about operating system compatibility, see the Visual Studio 2015 Compatibility page.

More information

Prerequisites

To apply this update, you must have Visual Studio 2015 Update 3 installed.

Restart requirement

No restart is required after you install this update.



Applies to

•Visual Studio Professional 2015
•Visual Studio Enterprise 2015
•Visual Studio Community 2015
•Visual Studio Express 2015 for Web
•Visual Studio Express 2015 for Desktop
•Visual Studio Express 2015 for Windows 10

Visual Studio 2015 System Requirements.:

Visual Studio 2015 Compatibility page:

No words of dropping the telemetry in C++ compiler.

No words of dropping the telemetry in C++ compiler.

The so called "telemetry" was located in the CRT, not the C++ compiler and it's been removed in this update.

The so called "telemetry" was located in the CRT, not the C++ compiler and it's been removed in this update.

Of course, but new sources like Betanews, Softpedia, etc are referring to latter rather than CRT. This is why my question was like it was.

If I mentioned it, it would be appropriate to quote MS representative also (from Betanews, but they quoted also):

Our intent was benign -- our desire was to build a framework that will help investigate performance problems and improve the quality of our optimizer should we get any reports of slowdowns or endemic perf problems in the field.
We apologize for raising the suspicion levels even further by not including the CRT source, this was just an oversight on our part. Despite that, some of you already investigated how this mechanism works in nice detail. As you have already called out, what the code does is trigger an ETW event which, when it’s turned on, will emit timestamps and module loads events. The event data can only be interpreted if a customer gives us symbol information (i.e. PDBs) so this data is only applicable to customers that are actively seeking help from us and are willing to share these PDBs as part of their investigation. We haven’t actually gone through this full exercise with any customers to date though, and we are so far relying on our established approaches to investigate and address potential problems instead.