Cumulative Servicing Release for Microsoft Visual Studio 2015 Update 3 (KB3165756)

Visual Studio 2015

This cumulative servicing release 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.

Download the Cumulative Servicing Release for Microsoft Visual Studio 2015 Update 3 (KB3165756) here

Issue 1

Visual C++ IntelliSense requests may fail in sections of code in which multiple namespaces that are opened by a single macro expansion are active.

To work around this issue, explicitly replace the macro with its expansion.

Issue 2

When you build multiple solutions in different instances of Visual Studio, false errors are sometimes reported in one of the instances.

Issue 3

Visual Studio may crash if you stop debugging and then resume debugging soon after.

Issue 4

Visual Studio may crash when you debug managed applications if IntelliTrace does not load.

Issue 5

When you upgrade the existing Extension SDK to a later version, the installation fails and you receive the following error message:

The method or operation is not implemented.

Issue 6

Provides improved XAML designer reliability.

Issue 7

Text Editor settings now persist as expected. In earlier updates to Visual Studio 2015, text editor settings frequently reverted automatically.

Issue 8

The data binding dialog box is now displayed correctly when you use third-party languages.

Issue 9

When you deploy Windows Universal apps to certain Windows devices, such as Xbox One or HoloLens, you may receive one of the following error messages if you deploy the app to the device on which it was previously deployed:

  • DEP2100 : Cannot copy the file "c:\users\SomeUser\documents\visual studio 2015\Projects\App5\App5\bin\x86\Debug\ilc\resources.pri" to the target machine "".

  • Unable to activate Windows Store app '134ebb6-879c-0483d-0bc130264_153eg2134dbg!App'. The activation request failed with error 'The package could not be installed because resources it modifies are currently in use'.

Issue 10

Reduces the memory footprint of Edit and Continue operations.

Issue 11

When you create a project that includes Application Insights by using Git, your CI build fails because the .gitignore file contains the ApplicationInsights.config file. To work around this issue, you can either run git add --force on ApplicationInsights.config, or you can remove the file from .gitignore. This update removes ApplicationInsights.config from .gitignore.

Issue 12

Visual Studio stamps the output of a PCL-targeting netstandard with a TargetFrameworkAttribute class that may generate MSBuild warnings when that PCL is referenced by other PCLs that target a profile. This warning is now removed by disabling the TargetFrameworkAttribute version check when another PCL references a PCL-targeting netstandard.

Issue 13

CodeLens uses excessive CPU when finding references for methods which implement common interfaces.

Issue 14

Fixed UI delay occurring occasionally after a build of certain Visual C++ projects.

Issue 15

In Visual Studio 2015 Update 3 with Windows 10 Tools 1.4.1, incremental deployment to same device will instead sometimes result in a full deployment.

Issue 16

This change addresses an issue in PCL targeting. The KB3165756 update (version 14.0.25425.01, released on August 2, 2016) introduced a change that addressed a problem that occurred when the Portable Class Library tooling targeted the .NET Framework 4.6, ASP.NET Core, or UWP 10.0. In this situation, the Portable Class Library tooling generated a project.json that used the "dotnet" TFM. The "dotnet" TFM is now obsolete and may no longer be supported by NuGet packages. The PCL tooling in the KB3165756 update was therefore changed to always target .NET Standard, even for specific target platforms. However, the fix in KB 3165756 was determined to be incomplete. Therefore, this update reverts the fix. Current versions of NuGet still check for obsolete TFMs and warn the user about them so that users can manually update the TFMs.

Issue 17

When you update some extensions in Visual Studio (including the Roslyn insiders extension), you may find that later instances of Visual Studio (after the immediate next instance) don't work. The fix was to update the Settings DLL that merges pkgdefs so that it matches what the devenv executable does. The workaround is to run devenv /updateConfiguration at a developer command prompt.

Issue 18

Fixes a bug that prevented Accelerated Massive Parallelism (AMP) from working in a multi-GPU environment when you use a Session 0 shell (such as in cluster nodes).

Issue 19

This fix makes sure that cleanup occurs between debug sessions and that you no longer have to wait between sessions.

Issue 20

Fixes a memory leak to increase designer stability.

Issue 21

Code that is generated for floating-point operations could be incorrect when it performs square-root calculations. This typically occurs in the following situations:

  • You compile by using the /fp:fast or /Qfast_transcendentals switch, and you use standard library functions to calculate the square-root.

  • You use the _mm_sqrt_sd/_mm_sqrt_ss intrinsic functions.

This problem prevents the upper part of an XMM register from being cleared. This could allow later instructions that use that register to operate on invalid values.

Issue 22

Fixes an issue that prevented extended popup editors, such as the brush editor, from being displayed when you arrange items in the XAML designer's properties tool window by name.

Issue 1

Resolves an ICE that occurs when you allocate an array of a __declspec(dllimport) class type that has a default constructor that has default arguments.

Issue 2

When it targeted the .NET Framework ASP.NET Core, or UWP frameworks, the Portable Class Library tooling generated a project.json that used the "dotnet" TFM. The "dotnet" TFM is now obsolete and may no longer be supported by NuGet packages. To avoid this issue in the future, the PCL tooling was changed to always target .NET Standard, even when it selects specific target platforms.

Issue 3

Potential miscompilation of code-calling functions that resemble std::min/std::max on floating point values.

Issue 4

Visual Studio crashes when you debug applications from Visual Studio on the Windows 10 Version 1607 update.

To work around the issue, update Visual Studio by installing the Windows 10 Version 1607 update of Windows SDK and tools. If that is not possible, go to Options/Debugging/General/"Enable UI Debugging Tools for XAML and clear the check box.

Issue 5

Improved debugging reliability when you debug Visual C++ or CLI code.

Issue 6

When you debug JavaScript eval code, if there are eval codes that have source maps that follow eval code that don't have source maps, the debugger crashes when it steps into eval code that does not have source maps.

Issue 7

After you revert MFC binary compatibility issues for runtime DLLs in Visual Studio 2015 Update 3, KB3165756 did not include MFC static libraries that matched the reverted code. This update includes MFC static libraries that were missed in the previous update.

Issue 8

Fixed implicit (group-based) permission handling when you use an AAD account during packaging.

Issue 9

Authored the resource DLL. Now customers can load the TestExplorer Window with localized strings.

Issue 1

An issue that affects inspecting local variables for code that's embedded in cshtml files occurs in ASP.NET Core applications.

Issue 2

FIX: This update enables you to permanently dismiss the Configuration CI banner in TestExplorer UI.

Issue 3

Package encryption contains an outdated flag.

Issue 4

Potential crashes occur when AAD users who have implicit permissions try to retrieve app names in the Packaging wizard.

Issue 5

After you install Windows updates, you may see various package load failures when you start Visual Studio. Although this update fixes this issue, you can also delete the ComponentModelCache folder as a workaround.

Issue 6

A regression in the MFC CMFCToolBarButton button prevents MFC apps from correctly working in Visual Studio 2015 Update 3.

Issue 7

Applications that use lots of async tasks can fail to display those tasks in the Tasks window.

Issue 8

Performance issue occur when Visual Studio is started by having the output window open.

Issue 9

A dialog box opens when you start the XAML designer in a Universal Windows Platform (UWP) app.

Issue 1

Visual Studio may leak memory when you use the editor light bulb to apply code actions to a C# or Visual Basic file.

Issue 2

Some large C# and Visual Basic projects that contain thousands of source files may experience memory and performance degradation because compilation symbols are unnecessarily realized.

Issue 3

Shared projects may report an error after they are unloaded and reloaded if some of their source files are open.

Issue 4

Visual Studio may crash and cause a stack overflow exception when it generates IntelliSense for some C# files that contain nested generic types.

Issue 5

In ASP.NET cshtml files, committing code completion after you type the full snippet may cause incorrect snippets to be added to the source file.

Issue 6

This fix addresses a memory leak in the StandardCollector.Service.exe process. You commonly encounter this leak when you debug managed code on Windows 7 that has Visual Studio 2015 Update 3 installed.

Issue 7

When you debug JavaScript files by using certain module configurations, the debugger might not load the correct source maps. This causes the program to crash. There is no known workaround for this bug other than to apply this KB3165756 update.

Issue 8

When you edit TypeScript build properties, the ourDir option does not save the changes that you made. After you make changes, the build properties page displays the previous state of outDir. As a workaround, you can add a tsconfig.json file that has the desired properties that match the current property configuration. Alternatively, you can manually edit the project file.

Issue 1

Visual Studio may crash when you close the Visual Studio IDE while C# and Visual Basic background operations are ongoing.

Issue 2

Visual Studio may crash if you update a solution while the C# or Visual Basic build is completing and reporting diagnostics.

After you add a Windows Communication Foundation (WCF) service reference to Silverlight projects, installing KB3165756 on Visual Studio 2015 Update 3 may cause an error and generate a warning message in the Error List window. To work around this issue, close and restart Visual Studio, reopen the project, right-click the new service reference in Solution Explorer, and then select Update Service Reference.

This Cumulative Servicing Release can be installed only on computers that have Visual Studio 2015 Update 3 installed. All fixes are cumulatively added to a single installer and cannot be installed individually.

The Cumulative Servicing Release may have been installed automatically together with Visual Studio 2015 Update 3. You can check by going to Help -> About Microsoft Visual Studio in Visual Studio. To ensure you have the latest fixes, you can download and install the Cumulative Servicing Release from this page. You do not have to uninstall previous versions to install the latest version.

You will not have to restart your machine after you install this Cumulative Servicing Release.

File details

VersionVisual Studio 2015
File nameVS14-KB3165756.exe
Date published09/14/2016
File size2.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 Cumulative Servicing Release are unchanged from Visual Studio 2015 System Requirements. For information about operating system compatibility, see the Visual Studio 2015 Compatibility page.

  • 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