We are looking to improve your experience on the Visual Studio Blog. It would be very helpful if you could share your feedback via this short survey that should take less than 2 minutes. Thanks!
Today we have several releases to talk about: there’s the release of Visual Studio 2017 version 15.3, the release of .NET Core 2.0, and a release of Visual Studio for Mac version 7.1. We’ll talk about them briefly in that order, but as always, there’s a lot more information in the release notes for each product. If you’d like to jump right in, download Visual Studio 2017 version 15.3, download .NET Core 2.0, and download Visual Studio for Mac. You can also access the latest Visual Studio 2017 product releases through an Azure virtual machine where we offer the recommended installation of the most popular workloads and components.
Visual Studio 2017 version 15.3
For Visual Studio 2017 version 15.3, we focused on improving accessibility, particularly using Visual Studio with the most popular screen readers. We made over 1,700 improvements and still have some work to do, but if you are using Visual Studio 2017 in a low-vision or no-vision mode, a lot has improved. Dante has a blog post on everything we’ve done and what’s more to come, but here I’ll call out a couple of the more major things we’ve improved.
- Debugging is much more accessible. Debugger windows like the Call Stack, Locals, Autos, and Watch windows were inaccessible to screen readers. That’s now fixed.
- The VS editor’s text adornments let developers know about features available at particular points on a line of code, such as breakpoints, lightbulbs, and error and warning “squiggles.” Customers can now discover and navigate between these adornments via the new “Show Line Annotations” command set, which you can find on the editor context menu.
In addition to accessibility, we have many fixes for reliability issues to improve performance, many of which you reported through report-a-problem. Here are some of the more notable ones that had high votes that we fixed:
- A crash that could occur in C# and VB projects when editing linked files, files in Shared Projects, or files used in projects targeting multiple runtimes.
- A race condition when debugging C# or VB projects that could cause Visual Studio to crash when ending the debugging session.
- A crash in C# or VB projects when malformed metadata is encountered in the code file.
- A crash that could occur when compiling a local function in C#.
We also improved many other experiences:
- Azure Functions Support. We added the tools for developing C# Azure Functions to the “Azure development” workload. The main feature change is that this update enables you to create pre-compiled C# Azure Functions, which start faster than script-based functions. For details see the Visual Studio 2017 Tools for Azure Functions blog post.
- Broad Azure sign-in support. VS 2017 15.3 also supports logging into not just Azure, but Azure Government and Sovereign cloud offerings, and Azure Stack.
- Improved container support. This release now supports the breadth of container development across existing .NET Framework apps with Windows Containers, to .NET Core with Windows, and Linux Support. Recent additions include support for your .NET Core applications in containers running Nano Server, as well as debugging improvements for .NET Framework applications in containers.
- Continuous Delivery Tools now included. We’ve moved the Continuous Deliver tools extension into the main product. You can configure continuous delivery for ASP.NET and ASP.NET Core projects targeting Azure App Service. This tooling will configure your continuous integration build using Visual Studio Team Services and configure your deployment to Azure App Service. Once configured, you can modify and extend the build and deploy process, customizing it to meet your exact needs.
For the full list of improvements check out the release notes for Visual Studio 2017 version 15.3.
.NET Core 2.0 Released
.NET Core 2.0 is also released today. This is the second major version of .NET Core and this release focuses on performance improvements and expanding the set of APIs available via .NET Standard 2.0. It includes the runtime and libraries for .NET Core as well as the tools for building, debugging and running .NET Core applications. There are some notable changes from .NET Core 1.1. There’s a full blog post on .NET Core 2.0, but here are some highlights:
- Live Unit Testing. You can use Live Unit Testing for .NET Standard, .NET Core, and ASP.NET Core projects. (Visual Studio Enterprise SKU only)
- References. You can now refer to .NET Core/.NET Standard libraries from .NET Framework projects and vice versa. No need to manually add interop NuGet packages – Visual Studio does this for you automatically.
- Containers with .NET Core and Nano Server. Support for containerizing ASP.NET Core apps as Nano Server images has been added and you can now select Nano Server as the container platform. You can do this under File->New Project for ASP.NET Core projects. For your existing projects, it can be added using the Project Context Menu.
- Support in Visual Studio for Mac. VS for Mac supports building .NET Core 2.0 applications, including libraries, console apps, as well as web applications and services with ASP.NET Core.
Note that the .NET Core 2.0 SDK needs to be installed via a separate download to enable .NET Core 2.0 development in Visual Studio 2017 version 15.3. You can get it at www.dot.net/core. Visual Studio enables side-by-side support of multiple .NET Core SDKs. This also means you can experiment with the latest daily build of the .NET Core SDK, while also developing with the latest public releases. See blog post for details.
Watch the .NET team demonstrate the new features of .NET Core, Visual Studio 2017 and Visual Studio for Mac! Learn what’s new and how to use the new tools.
Visual Studio for Mac version 7.1
Visual Studio for Mac version 7.1 is also available today. It adds support for .NET Core 2.0 targeting in console apps, web apps, and web services. It also enables creating .NET Standard 2.0 in library projects, to share more code across projects. Like Visual Studio 2017, a lot of the improvements in this update center on reliability. We’ve made strides in decreased memory usage, better performance, and decreased crashes. Many of these fixes have been made possibly by your feedback, so please keep that coming through the Developer Community.
Share Your Feedback
As always, we welcome your thoughts and concerns. For issues, let us know via the Report a Problem tool in Visual Studio. You’ll be able to track your issues in the Visual Studio Developer Community where you can ask questions and find answers. For suggestions, share with us through UserVoice.
 |
John Montgomery, Director of Program Management for Visual Studio @JohnMont John is responsible for product design and customer success for all of Visual Studio, C++, C#, VB, JavaScript, and .NET. John has been at Microsoft for 17 years, working in developer technologies the whole time. |
I have installed it, along with “Azure Development” workflow but there’s nothing in File > New Project for creating an Azure Function?
Look in your extensions and updates and see if there is an update available for “Azure Functions and Web Jobs Tools”. While included in the Azure workload, it’s delivered via the gallery so it’s possible that update hasn’t made it’s way to your machine yet.
Yep that was the solution, thanks!
“…hasn’t made ITS way…”
Per my instructions above, you can tell Visual Studio to update it on demand. If you haven’t cleared it there should be a notification in your notifications area (the flag icon in the top right) or by looking for updates in the Extensions and Updates manager
But in Visual F# : file Program.fs that it can’t use “Backspace” . I tried my best to can use it that you have to create a new file *.fs . But when I restart Visual Emprise , I still get errors as . Thank you to hear from me !
This sounds like a known issue in 15.3, that we addressed in the 15.3.1 update. Either:
1. Work around it in 15.3 by closing all documents after opening the solution, or
2. Update to 15.3.1 – launch the Visual Studio Installer and update to the latest version.
Hope this helps!
Having a tough time figuring out if 15.3 is an upgrade now, or still a separate install.
Ha. I tried updating to 15.2.(16) and got 15.3. Nice.
Visual Studio 2017 version 15.3 is an update to previous releases of Visual Studio 2017.
-Paul
VS Program Manager
I don’t see it in the Visual Studio 2017 “Tools > Extensions and Updates” menu. Should I expect that to change going forward?
AspNyc — Yes you can. We’ve moved to a gradual rollout so that we can better listen to and react to the feedback from our users. If you would like to upgrade to the latest today, please do so through the Visual Studio Installer, from VisualStudio.com, or if you are a Subscription customer, you can also do this from My.VisualStudio.com.
-Paul
Yep. This had me a bit confused too. I have Alt-T-U burned into my brain but it didn’t do anything! Finally ran across a note somewhere that said to run the Visual Studio Installer, and that did the trick.
It’s *super* annoying when companies do this… Announce that something has been released, but then don’t actually release it to everyone at the same time…
Perhaps if a user specifically went to the menu option Tools=>Extensions and Updates, that means they are interested in the latest update….
I agree, this was super confusing as well. I assumed I’d either be able to update from VS itself, or there’d be a file marked update. I wish there was a consistent way to update VS, it seems to change pretty often. Thanks for clarifying.
But in Visual F# : file Program.fs that it can’t use “Backspace” . I tried my best to can use it that you have to create a new file *.fs . But when I restart Visual Emprise , I still get errors as . Thank you to hear from me !
“If you’d like to jump right in, download Visual Studio 2017 version 15.3 (https://www.visualstudio.com/downloads/)”
That page doesn’t show any update links, but rather an installer link. Are we supposed to run that?
Do you see the confusion millions of users have? We could use some clarity.
For me, the installer ran an in place update of my existing VS 15.2 install.
I think running your original installer/uninstaller will also give the option to get the new updates.
If you already have Visual Studio 2017 installed, you can run the “Visual Studio Installer” already installed on your machine and click the Update button for the installer followed by the Update button for the Visual Studio edition you’ve got installed.
Alternately, you can run the installer linked in the blog post, which will also update your existing installation. Or, you can wait for the notification within Visual Studio to install.
-Paul
VS Program Manager.
But in Visual F# : file Program.fs that it can’t use “Backspace” . I tried my best to can use it that you have to create a new file *.fs . But when I restart Visual Emprise , I still get errors as . Thank you to hear from me !
stop posting your spam everywhere
Quick fix for you, you’ve duplicated:
“blog post on .NET Core 2.0, but here are some highlights:”
Thank you, Fixed It! 🙂
But in Visual F# : file Program.fs that it can’t use “Backspace” . I tried my best to can use it that you have to create a new file *.fs . But when I restart Visual Emprise , I still get errors as . Thank you to hear from me !
Is there going to be a Visual Studio 2017 15.4 soon or 15.3 is going to be a stick for a while?
I am asking this because our team is slow in adapting to a new release/update of VS and we don’t want to make the switch to a release that doesn’t needs an update very soon.
The VS 2017 release cadence is addressed here: https://www.visualstudio.com/en-us/productinfo/vs2017-release-rhythm. The 15.3 update is more significant than previous updates (15.1/15.2), so moving to it is likely worth your time especially if you are a C++ developer.
Anybody else seeing error “The SDK ‘Microsoft.NET.Sdk.Web’ specified could not be found” with netcoreapp1.1 Web and Console projects? Projects won’t load with 2017.3.
If I manually edit csproj file and change to then projects are loaded correctly
If I manually edit csproj file and change
Project Sdk=”Microsoft.NET.Sdk.Web”
to
Project Sdk=”Microsoft.NET.Sdk”
then projects are loaded correctly
We’ve seen this in two cases. The first is if an old preview of the 1.0 CLI is still installed on the machine. Please check to see if you have any old 1.x CLIs still installed. The second case is if the CLI is not correctly on the path. Please open a developer command prompt and inspect the PATH variable to make sure that “C:\Program Files\dotnet” appears on the path before any other entries that point to sub-directories of the “dotnet” folder.
Joe, I ran into the same issue. I had a old preview cli which I deleted. I also made sure that the path variable points to the dotnet folder. Still having issues with creating a new webapplication project with the same error mentioned by Sami Ovaska.
Pradeep, let me work with you off-line and see what is going on with your machine and will post back in this thread. Please shoot me an email at jomorris@microsoft.com
Finally found fix for this. I had SDK 1.0.0 in global.json, updated it to 1.1.0 fixed the problem.
This is a great release, and addresses some real needs. Do you know long we should expect it to take before it, and the associated SDKs (TypeScript 2.3, .NET Core 2, etc.) make it to the Team Services hosted build agents?
The updated image with 15.3 and dotnet 2.0 are being rolled out. Most of the accounts have the updates already. The rest will be completed over the next day or two.
Any updates as to if 15.3 has been released across all hosted VS 2017 agents?
Doesn’t run.
41
2017/08/14 19:09:42.893
Error
VisualStudio
Failed to process PkgDef file
8007001f
C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\Common7\IDE\Extensions\DSLTextTemplatingRegistry_x86.pkgdef
Hi Willard –
Please go to the Visual Studio Installer, click on Report a Problem in the upper right corner and provide specific details (like for example are you seeing this error in a window or in the activitylog file? The Report-A-Problem tool will also gather some additional information that we can use to investigate the issue.
Thank you for the new release. Unfortunately, a recurring issue is that we still have to fix the SDK headers to compile them with /permissive-:
wrl\implements.h
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.15063.0\winrt\wrl\implements.h(629): error C2187: syntax error: ‘identifier’ was unexpected here
Details::InterfaceTraits::Verify();
Has winrt\wrl been discontinued or what is the reason this does not get fixed/tested?
Thanks for the report Euclid.
This issue has been addressed in the next update to the Windows 10 SDK. You can obtain a copy through the Windows Insider Program.
https://www.microsoft.com/en-us/software-download/windowsinsiderpreviewSDK
Thanks
Could u pls tell me how to fix this? I am just a beginner of programming and have no idea how to fix it. THX 🙂
Wow, seriously?
Doesn’t that mean we need to wait until Fall Creators Update gets released?
*Sign* well at least it’s good to hear that it’s going to get fixed.
Could u pls tell me how to fix this? I am just a beginner of programming and have no idea how to fix it. THX 🙂
KUDO for the accessiblity features!
Visual Studio 2017 (community) just updated to 15.3. Now a simple .NET Core project does not build – all dependencies are broken – Microsoft.AspNetCore(1.1.2), Microsoft.EntityFrameworkCore(1.1.2), etc.
Says 1.1.2 is not compatible with netcoreapp1.1
The app (a simple ASP.NET Core API project) is targeting .NET Core 1.1
.csproj file:
netcoreapp1.1
Help! This project is now hosed, thanks to this upgrade (which I’m pretty sure I didn’t ask to be applied…)
I’m seeing the same after allowing my primary VS2017 instance to be updated to 15.3. I’ll let you know if I find any workarounds.
Ok, some progress – I made sure all SDKs were removed (as mentioned in posts above, 1.x SDKs can break things).
Installed dotnet core 2.0 SDK
Installed dotnet core 1.0.4 SDK (https://github.com/dotnet/core/blob/master/release-notes/download-archives/1.1.2-download.md)
Increased my global.json sdk versions from 1.0.0 to 1.0.4
Everything started working – the global.json increase was potentially all I needed 😉
Matt .. when you say remove older SDK’s do you mean just delete those folders from within c:\program files\dotnet ?
Also where do I find global.json please ?
I used Apps and Features to uninstall each of the older SDK MSIs.
global.json files were added manually to the root of the solution folder or source control repository. If you are struggling to find one, you may not have one. I have no idea which project templates automatically add global.json files (if any). Plenty of resources on the net about the topic though.
Honestly, since posting this earlier today, I’ve had a hard time getting VS2017.3 to consistently build my project. Often hitting build or run, Visual studio shows the build as running (you can cancel the build off the build menu) but nothing ever appears in the output window.
I would say that the instructions above got my solution to successfully load but that is only part of the story for resolving this for my team.
Good luck! If anyone has instructions for getting back to 2017.2 I’d love a link please!
I didn’t know there was a “dotnet core 1.0.4” out – I ended up having to update the project to dotnet core 2.0 – which by the way still wasn’t as easy as installing the SDK – I had to remove ALL of my package references, and replace it with just the one “microsoft.aspnetcore.all” package (or whatever the exact name is). You can’t just go into the package manager and click the “Upgrade” button next to your packages – it errors saying they are not compatible!
Would be really nice if there was documentation on how to upgrade existing projects. I’m going to have to make sure my work systems DO NOT UPDATE as we can’t afford to mass-upgrade the projects to 2.0 at this time. Again VC 2017 15.3 DOES NOT PLAY WELL with dotnet core 1!
Hi, see
https://docs.microsoft.com/en-us/aspnet/core/migration/1x-to-2x/
What the…. new splashscreen, and still old ugly icon that I can’t see on my desktop…. hate you.
Change (or make) the shortcut to VS to add the /nosplash switch – boom, never see the splash screen again. (seems to load faster, as it’s not pausing so you can admire the “beauty” of it 🙂
Icon dude…. icon
http://i.imgur.com/HulOkIt.png – default windows 7 wallpaper
http://i.imgur.com/rRnH8QH.png
https://blogs.msdn.microsoft.com/visualstudio/2017/03/08/iterations-on-infinity/
I think John Lea need another $1kk to make another icon that people can see
Simply use the beauty Visual Studio 2010 icon or previous versions icons of Visual Studio until Microsoft uglyfy all its software.
When will VS15.3 be available worldwide? I am in Greater Boston, and yet to receive the update.
You might not have been toasted yet but you should be able to get it anywhere by launching the “Visual Studio Installer”. It will give you an update button that let’s you install it anytime.
Thank you. Updating it now via VSI.
Really wish Microsoft could address the app publishing error “”Your package Microsoft.NET.Native.Framework.1.6 specifies version 1.6.25405.0, but 1.6.24903.0 is the minimum available version.” ( https://social.msdn.microsoft.com/Forums/windowsapps/en-US/d854ce93-ef54-4832-8d3a-e6f81ac0f1fa/uwp-error-your-package-microsoftnetnativeframework16-specifies-version-16254050-but?forum=windowsstore) before releasing this update. Users this VS update to publish serious apps should be a minimum assumption.
There is still a disturbing bug in 15.3.0 keeping the CPU running high (~30% on an i7-4770) after compiling a large C# (WPF) project file (>11k lines). In Preview 7.1, one could work around by scrolling the file content to the top, but this doesn’t seem to work in 15.3.0 RTM anymore. Thank you!
Same to me. After upgrading VS to 15.3 and loading my WPF app I have around 30% CPU usage for VS process. It stays at range 28-35% and doesn’t want to drop. At that time VS became super-unresponsive – every action take at least second or two to complete, even scrolling. Event more – VS starts to consume memory at the rate of ~2Mb/sec. I left VS at the background for several minutes and now it take > 1400 Mb.
So after update I have unusable laggy editor with terrible memory leak. Great.
Hi: Our dev team would like to investigate and see what is going on. For that we need a trace. When VS is in a bad state, launch the “Send Feedback” tool, either in the bad VS or another instance by clicking the “Send Feedback” icon present at the top right corner of VS and choosing “Report a Problem” icon and then following along with the wizard walk thru. Please let us know after you have done that so that we can look at the trace. If your repo is publicly sharable, even better, and please do share with me jomorris@microsoft.com
Hi, Joe. Thank you for feedback! It appears that the problem related to the “Navigate To” feature – https://developercommunity.visualstudio.com/content/problem/62042/visual-studio-2017-is-continuously-at-25-cpu-usage.html.
When I load solution CPU usage and memory consumption is okay. But when I hit Ctrl+T and start typing CPU for VS process immediately jumps up to 48% and the memory starts to grow forever. At this moment every action became terribly slow.
The issue from link marked as resolved but I still have this on 15.3 (I haven’t it in previous releases).
Allesad, apparently, you just have to deal with it as Microsoft provides no way to downgrade back to 15.2. Great that Microsoft didn’t have the foresight to think that maybe there could be bugs in the new version that could be show stoppers for people.
I agree with Jon’s comment below. I upgraded my VS 2017 and already got 2 crashes and the debugging became much harder for me instead of being easier 🙁
I also got a lot of performance issues since the 15.3 update. Visual Studio becomes pretty often unresponive after and while the debugging session for C#/WPF projects. So the only thing I could do was killing the process using the TaskManager. (4 times since tuesday 🙁 )
After installing, Visual Studio won’t run. It tells me setup is not complete and to run the installer again. I did, and it didn’t say anything was wrong. So, I selected repair. A few seconds in, there was an error. I’m now afraid to install 2017 updates on my work machine.
Here is the log.
“[0578:0004][2017-08-15T02:49:11] Error 0x80070005:
at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
at System.Threading.Mutex.MutexTryCodeHelper.MutexTryCode(Object userData)
at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)
at System.Threading.Mutex.CreateMutexWithGuaranteedCleanup(Boolean initiallyOwned, String name, Boolean& createdNew, SECURITY_ATTRIBUTES secAttrs)
at System.Threading.Mutex..ctor(Boolean initiallyOwned, String name, Boolean& createdNew, MutexSecurity mutexSecurity)
at System.Threading.Mutex..ctor(Boolean initiallyOwned, String name)
at Microsoft.VisualStudio.Setup.Utility.ProcessUtility.EnsureMutex(String name)
at Microsoft.VisualStudio.Setup.Validation.SetupRunning.Evaluate()
at Microsoft.VisualStudio.Setup.Engine.EvaluatePrechecks(String installationPath, Boolean isLayoutSet, InstallSize installSize, ExecuteAction bootstrapperAction, IEnumerable`1 evaluators, ISet`1& failedEvaluators, Boolean& anyFatalErrors, ITelemetryOperation operation, IQuery query)
at Microsoft.VisualStudio.Setup.Engine.c__DisplayClass154_0.b__0(MessageResult result)
at Microsoft.VisualStudio.Setup.Utility.MessageBusUtility.SendMessageUtil(IServiceProvider services, Func`2 doAction)
at Microsoft.VisualStudio.Setup.Engine.PreChecks(String installationPath, Boolean isLayoutSet, Product product, ExecuteAction bootstrapperAction, ITelemetryOperation operation, IQuery query)
at Microsoft.VisualStudio.Setup.Engine.Repair(CancellationToken token)Access to the path ‘Global\Devdiv’ is denied.
I had same issue , did windows 10 OS reset but while installing visual studio it crashed with blue screen of death errors.
I’m seeing the same issue here too. VS was working fine on Friday but this morning (Monday) it won’t load telling me that ‘The setup for this installation of Visual Studio is not complete. Please run the Visual Studio Installer again to correct the issue.’.
If I try to install the offered update to 15.3.1 (from 15.3.0) or repair my current install I get the following error:
[6338:0021][2017-08-21T10:06:11] Error 0x80070005:
at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
at System.Threading.Mutex.MutexTryCodeHelper.MutexTryCode(Object userData)
at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)
at System.Threading.Mutex.CreateMutexWithGuaranteedCleanup(Boolean initiallyOwned, String name, Boolean& createdNew, SECURITY_ATTRIBUTES secAttrs)
at System.Threading.Mutex..ctor(Boolean initiallyOwned, String name, Boolean& createdNew, MutexSecurity mutexSecurity)
at System.Threading.Mutex..ctor(Boolean initiallyOwned, String name)
at Microsoft.VisualStudio.Setup.Utility.ProcessUtility.EnsureMutex(String name)
at Microsoft.VisualStudio.Setup.Validation.SetupRunning.Evaluate()
at Microsoft.VisualStudio.Setup.Engine.EvaluatePrechecks(String installationPath, Boolean isLayoutSet, InstallSize installSize, ExecuteAction bootstrapperAction, IEnumerable`1 evaluators, ISet`1& failedEvaluators, Boolean& anyFatalErrors, ITelemetryOperation operation, IQuery query)
at Microsoft.VisualStudio.Setup.Engine.c__DisplayClass154_0.b__0(MessageResult result)
at Microsoft.VisualStudio.Setup.Utility.MessageBusUtility.SendMessageUtil(IServiceProvider services, Func`2 doAction)
at Microsoft.VisualStudio.Setup.Engine.PreChecks(String installationPath, Boolean isLayoutSet, Product product, ExecuteAction bootstrapperAction, ITelemetryOperation operation, IQuery query)
at Microsoft.VisualStudio.Setup.Engine.Install(Product product, String destination, CancellationToken token)Access to the path ‘Global\Devdiv’ is denied.
First off, I am sorry to hear about the issues you are having. We are currently investigating this issue to get to a root cause of it. At this time, we do not have a clear indication of what changed such that we lost permissions to the registry value that controls the mutex behavior, but it is out top priority right now.
This is issue is currently tracked under the existing Developer Community ticket here: https://developercommunity.visualstudio.com/content/problem/95371/visual-studio-does-not-start.html
Please use that ticket for tracking of updates on this issue.
Hi Folks!
I have the same issue “Access to the path ‘Global\Devdiv’ is denied” and the problem was insufficient disk space.
How to use C# 7.1 features, it is giving me compiler error when tried using Async Main after updating to 15.3 & .Net framework 7
I had to change the project options (build / advanced) to enable C# 7.1 features, apparently it’s not the default to enable them.
Thanks got it, so need to explicitly set Language Version to C#7.1 instead of default or set “7.1” in csproj. Should have enabled by default.
7.1
After update to 15.3, I use CMake 3.8.2 creating a c++ solution, and open a cpp file in the solution, the IDE is crash.
I am sorry for your experience. We would like to investigate this crash as soon as possible.
Can you open a developercommunity.visualstudio.com ticket and ideally attach to it a crash dump of devenv.exe? If you have any trouble collecting the crash dump or opening the ticket, just send me a short email at mluparu at microsoft dotcom and we can take it from there.
Thanks!
Marian
Encoding chaos on Visual C++ desktop (formerly Win32) template
https://developercommunity.visualstudio.com/content/problem/84279/encoding-chaos-on-visual-c-desktop-formerly-win32.html
Thanks for opening a developercommunity ticket to track this issue. Can you tell us what version of Visual Studio you are currently on? With the final release of 15.3, this issue should already be fixed.
In 15.3.0 final release there still is.
not fixed in 15.3.0 final release.
Thanks for letting me know. I’m following up on this
@abc, FYI, Raul is looking at this issue and followed up with a few questions: https://developercommunity.visualstudio.com/content/problem/84279/encoding-chaos-on-visual-c-desktop-formerly-win32.html
Kudos to team for making it faster! ☺
I updated to VS2017 15.3 today and now every C++ Project property page says “There are no property pages for the selection.”
There’s no way to access them, I’ll have to hand edit the xml!
Sorry to hear about this issue.
As a workaround, can you check that the property page selection (i.e. Platform and Configuration drop-downs) doesn’t have an invalid project configuration selected by default?
Can you open a developercommunity.visualstudio.com ticket (via Report a Problem in VS) for us to track this bug?
Thanks,
Marian
Same here…
What about the TFS development? It seems, that even MS is abandon TFS for git.
Working with TFS is like a punishment if you know git and its nice features and performance.
hi Daniel. We have 2 version control systems in TFS/VSTS. One is Team Foundation Version Control (TFVC) and the other is git. We are committed to both version control systems. Many teams at Microsoft have made the decision to standardize on git. You should be able to choose which one works best for your organization. You can even start to use git from within a TFVC project if you want.
I have VS 2017 v15.2 installed. Is it possible to upgrade it to v15.3 ? Do i need to install fresh?
You will get a toast in Visual Studio at some point. Or you if you want to update faster you can launch the “Visual Studio Installer” which will prompt you to upgrade.
@MS team: You ask for feedback about the blog on the top. The first question in the survey is:
>> How would you rate this blog post, Visual Studio 2017 Version 15.3 Released?
and the possible answers are 1 to 5. So what’s the scale? 5 is the best? Quite ambiguous 😉
I’m pretty sure you can assume 5 means best.
This is fixed. Thanks for calling it out.
Good to see an update, sadly it did not fix the broken XAML designer 🙁
Still more or less broken with hangs and crashes
Hi Valdimar.Thor
Could you please log this issue on https://developercommunity.visualstudio.com so that our engineering team can investigate.
Many thanks, Deniz
When is there going to be a template for Integration Services (2016) released for VS 2017?
Hi Bob
Thanks for getting in contact. A preview release with SSIS support will be available soon.
Cheers
Deniz
Sorry to rain on your parade: is there a way to downgrade from 15.3 to 15.2?
WPF project that compiles in 15.2 fails in 15.3 with
C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\MSBuild\15.0\Bin\Roslyn\Microsoft.CSharp.Core.targets(84,5): error MSB6006: “csc.exe” exited with code -2146232797.
It ruined whole day and still not a single clue which file makes compiler unhappy.
Sorry to hear that is happening.
Would you be able to share out the project that is causing problems? Or send us a stack trace of the crash so we can figure out what is going on here?
My email is jaredpar@microsoft.com.
That’s great, but, the question is how to downgrade to 15.2? Is there no way to go back to an old version?
Email sent, thank you for trying to help!
As a temporary solution i’ve installed “Microsoft.Net.Compilers 2.2.0” package into the project and it compiles again with older version. However, this is a temporary solution only.
Microsoft:
How do I downgrade back to 15.2? I am having major problems with 15.3. I installed the update. Now it keeps giving me an unrecoverable error when I load up my .NET Framework projects and exits. I tried doing a repair and then an uninstall and reinstall and the problem persists. I also tried doing a system restore from about a week ago. I couldn’t get Visual Studio to even open when I did that. Now, I undid the system restore. I am dead in the water. I want to downgrade back to 15.2. Where do I get the installer for 15.2?
The following is the error I’m getting. I can’t do anything until I get this resolved. How do I revert back to the old version?
Application: devenv.exe
Framework Version: v4.0.30319
Description: The application requested process termination through System.Environment.FailFast(string message).
Message: System.InvalidOperationException: This operation cannot be performed on a default instance of ImmutableArray. Consider initializing the array, or checking the ImmutableArray.IsDefault property.
at System.Collections.Immutable.ImmutableArray`1.ThrowInvalidOperationIfNotInitialized()
at System.Collections.Immutable.ImmutableArray`1.System.Collections.Generic.IEnumerable.GetEnumerator()
at System.Linq.Enumerable.WhereSelectEnumerableIterator`2.MoveNext()
at System.Collections.Immutable.ImmutableDictionary`2.AddRange(IEnumerable`1 items, MutationInput origin, KeyCollisionBehavior collisionBehavior)
at System.Collections.Immutable.ImmutableDictionary`2.AddRange(IEnumerable`1 pairs, Boolean avoidToHashMap)
at System.Collections.Immutable.ImmutableDictionary`2.AddRange(IEnumerable`1 pairs)
at System.Collections.Immutable.ImmutableDictionary.ToImmutableDictionary[TSource,TKey,TValue](IEnumerable`1 source, Func`2 keySelector, Func`2 elementSelector, IEqualityComparer`1 keyComparer, IEqualityComparer`1 valueComparer)
at System.Collections.Immutable.ImmutableDictionary.ToImmutableDictionary[TSource,TKey](IEnumerable`1 source, Func`2 keySelector)
at Microsoft.VisualStudio.LanguageServices.Implementation.DesignerAttribute.DesignerAttributeIncrementalAnalyzer.d__8.MoveNext()
— End of stack trace from previous location where exception was thrown —
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.VisualStudio.LanguageServices.Implementation.DesignerAttribute.DesignerAttributeIncrementalAnalyzer.d__7.MoveNext()
— End of stack trace from previous location where exception was thrown —
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.CodeAnalysis.SolutionCrawler.SolutionCrawlerRegistrationService.WorkCoordinator.IncrementalAnalyzerProcessor.c__DisplayClass31_1`1.<b__0>d.MoveNext()
— End of stack trace from previous location where exception was thrown —
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.CodeAnalysis.SolutionCrawler.SolutionCrawlerRegistrationService.WorkCoordinator.IncrementalAnalyzerProcessor.d__33`2.MoveNext()
Stack:
at System.Environment.FailFast(System.String, System.Exception)
at Microsoft.CodeAnalysis.FailFast.OnFatalException(System.Exception)
at Microsoft.CodeAnalysis.ErrorReporting.FatalError.Report(System.Exception, System.Action`1)
at Microsoft.CodeAnalysis.SolutionCrawler.SolutionCrawlerRegistrationService+WorkCoordinator+IncrementalAnalyzerProcessor+d__33`2[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089],[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].MoveNext()
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(System.Threading.Tasks.Task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(System.Threading.Tasks.Task)
at Microsoft.CodeAnalysis.SolutionCrawler.SolutionCrawlerRegistrationService+WorkCoordinator+IncrementalAnalyzerProcessor+d__33`2[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089],[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].MoveNext()
at System.Runtime.CompilerServices.AsyncMethodBuilderCore+MoveNextRunner.InvokeMoveNext(System.Object)
at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Runtime.CompilerServices.AsyncMethodBuilderCore+MoveNextRunner.Run()
at System.Threading.Tasks.AwaitTaskContinuation.RunOrScheduleAction(System.Action, Boolean, System.Threading.Tasks.Task ByRef)
at System.Threading.Tasks.Task.FinishContinuations()
at System.Threading.Tasks.Task.FinishStageThree()
at System.Threading.Tasks.Task.FinishStageTwo()
at System.Threading.Tasks.Task.Finish(Boolean)
at System.Threading.Tasks.Task`1[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].TrySetException(System.Object)
at System.Runtime.CompilerServices.AsyncTaskMethodBuilder`1[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].SetException(System.Exception)
at Microsoft.CodeAnalysis.SolutionCrawler.SolutionCrawlerRegistrationService+WorkCoordinator+IncrementalAnalyzerProcessor+c__DisplayClass31_1`1+<b__0>d[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].MoveNext()
at System.Runtime.CompilerServices.AsyncMethodBuilderCore+MoveNextRunner.InvokeMoveNext(System.Object)
at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Runtime.CompilerServices.AsyncMethodBuilderCore+MoveNextRunner.Run()
at System.Threading.Tasks.AwaitTaskContinuation.RunOrScheduleAction(System.Action, Boolean, System.Threading.Tasks.Task ByRef)
at System.Threading.Tasks.Task.FinishContinuations()
at System.Threading.Tasks.Task.FinishStageThree()
at System.Threading.Tasks.Task.FinishStageTwo()
at System.Threading.Tasks.Task.Finish(Boolean)
at System.Threading.Tasks.Task`1[[System.Threading.Tasks.VoidTaskResult, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].TrySetException(System.Object)
at System.Runtime.CompilerServices.AsyncTaskMethodBuilder`1[[System.Threading.Tasks.VoidTaskResult, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].SetException(System.Exception)
at Microsoft.VisualStudio.LanguageServices.Implementation.DesignerAttribute.DesignerAttributeIncrementalAnalyzer+d__7.MoveNext()
at System.Runtime.CompilerServices.AsyncMethodBuilderCore+MoveNextRunner.InvokeMoveNext(System.Object)
at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Runtime.CompilerServices.AsyncMethodBuilderCore+MoveNextRunner.Run()
at System.Threading.Tasks.AwaitTaskContinuation.RunOrScheduleAction(System.Action, Boolean, System.Threading.Tasks.Task ByRef)
at System.Threading.Tasks.Task.FinishContinuations()
at System.Threading.Tasks.Task.FinishStageThree()
at System.Threading.Tasks.Task.FinishStageTwo()
at System.Threading.Tasks.Task.Finish(Boolean)
at System.Threading.Tasks.Task`1[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].TrySetException(System.Object)
at System.Runtime.CompilerServices.AsyncTaskMethodBuilder`1[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].SetException(System.Exception)
at Microsoft.VisualStudio.LanguageServices.Implementation.DesignerAttribute.DesignerAttributeIncrementalAnalyzer+d__8.MoveNext()
at System.Runtime.CompilerServices.AsyncMethodBuilderCore+MoveNextRunner.InvokeMoveNext(System.Object)
at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Runtime.CompilerServices.AsyncMethodBuilderCore+MoveNextRunner.Run()
at System.Threading.Tasks.AwaitTaskContinuation.RunOrScheduleAction(System.Action, Boolean, System.Threading.Tasks.Task ByRef)
at System.Threading.Tasks.Task.FinishContinuations()
at System.Threading.Tasks.Task.FinishStageThree()
at System.Threading.Tasks.Task`1[[System.Collections.Immutable.ImmutableArray`1[[Microsoft.CodeAnalysis.DesignerAttributes.DesignerAttributeDocumentData, Microsoft.CodeAnalysis.Features, Version=2.3.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35]], System.Collections.Immutable, Version=1.2.1.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a]].TrySetResult(System.Collections.Immutable.ImmutableArray`1)
at System.Runtime.CompilerServices.AsyncTaskMethodBuilder`1[[System.Collections.Immutable.ImmutableArray`1[[Microsoft.CodeAnalysis.DesignerAttributes.DesignerAttributeDocumentData, Microsoft.CodeAnalysis.Features, Version=2.3.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35]], System.Collections.Immutable, Version=1.2.1.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a]].SetResult(System.Collections.Immutable.ImmutableArray`1)
at Microsoft.VisualStudio.LanguageServices.Remote.JsonRpcClient+d__4`1[[System.Collections.Immutable.ImmutableArray`1[[Microsoft.CodeAnalysis.DesignerAttributes.DesignerAttributeDocumentData, Microsoft.CodeAnalysis.Features, Version=2.3.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35]], System.Collections.Immutable, Version=1.2.1.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a]].MoveNext()
at System.Runtime.CompilerServices.AsyncMethodBuilderCore+MoveNextRunner.InvokeMoveNext(System.Object)
at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Runtime.CompilerServices.AsyncMethodBuilderCore+MoveNextRunner.Run()
at System.Threading.Tasks.AwaitTaskContinuation.RunOrScheduleAction(System.Action, Boolean, System.Threading.Tasks.Task ByRef)
at System.Threading.Tasks.Task.FinishContinuations()
at System.Threading.Tasks.Task.FinishStageThree()
at System.Threading.Tasks.Task`1[[System.Collections.Immutable.ImmutableArray`1[[Microsoft.CodeAnalysis.DesignerAttributes.DesignerAttributeDocumentData, Microsoft.CodeAnalysis.Features, Version=2.3.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35]], System.Collections.Immutable, Version=1.2.1.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a]].TrySetResult(System.Collections.Immutable.ImmutableArray`1)
at System.Runtime.CompilerServices.AsyncTaskMethodBuilder`1[[System.Collections.Immutable.ImmutableArray`1[[Microsoft.CodeAnalysis.DesignerAttributes.DesignerAttributeDocumentData, Microsoft.CodeAnalysis.Features, Version=2.3.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35]], System.Collections.Immutable, Version=1.2.1.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a]].SetResult(System.Collections.Immutable.ImmutableArray`1)
at StreamJsonRpc.JsonRpc+d__63`1[[System.Collections.Immutable.ImmutableArray`1[[Microsoft.CodeAnalysis.DesignerAttributes.DesignerAttributeDocumentData, Microsoft.CodeAnalysis.Features, Version=2.3.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35]], System.Collections.Immutable, Version=1.2.1.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a]].MoveNext()
at System.Runtime.CompilerServices.AsyncMethodBuilderCore+MoveNextRunner.InvokeMoveNext(System.Object)
at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Runtime.CompilerServices.AsyncMethodBuilderCore+MoveNextRunner.Run()
at System.Threading.Tasks.AwaitTaskContinuation.RunOrScheduleAction(System.Action, Boolean, System.Threading.Tasks.Task ByRef)
at System.Threading.Tasks.Task.FinishContinuations()
at System.Threading.Tasks.Task.FinishStageThree()
at System.Threading.Tasks.Task`1[[System.Collections.Immutable.ImmutableArray`1[[Microsoft.CodeAnalysis.DesignerAttributes.DesignerAttributeDocumentData, Microsoft.CodeAnalysis.Features, Version=2.3.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35]], System.Collections.Immutable, Version=1.2.1.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a]].TrySetResult(System.Collections.Immutable.ImmutableArray`1)
at System.Threading.Tasks.TaskCompletionSource`1[[System.Collections.Immutable.ImmutableArray`1[[Microsoft.CodeAnalysis.DesignerAttributes.DesignerAttributeDocumentData, Microsoft.CodeAnalysis.Features, Version=2.3.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35]], System.Collections.Immutable, Version=1.2.1.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a]].TrySetResult(System.Collections.Immutable.ImmutableArray`1)
at StreamJsonRpc.JsonRpc+c__DisplayClass63_1`1[[System.Collections.Immutable.ImmutableArray`1[[Microsoft.CodeAnalysis.DesignerAttributes.DesignerAttributeDocumentData, Microsoft.CodeAnalysis.Features, Version=2.3.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35]], System.Collections.Immutable, Version=1.2.1.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a]].b__0(StreamJsonRpc.JsonRpcMessage)
at StreamJsonRpc.JsonRpc+d__71.MoveNext()
at System.Runtime.CompilerServices.AsyncTaskMethodBuilder.Start[[StreamJsonRpc.JsonRpc+d__71, StreamJsonRpc, Version=1.1.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a]](d__71 ByRef)
at StreamJsonRpc.JsonRpc.HandleRpcAsync(System.String)
at StreamJsonRpc.JsonRpc+c__DisplayClass70_0+<b__0>d.MoveNext()
at System.Runtime.CompilerServices.AsyncTaskMethodBuilder.Start[[StreamJsonRpc.JsonRpc+c__DisplayClass70_0+<b__0>d, StreamJsonRpc, Version=1.1.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a]](<b__0>d ByRef)
at StreamJsonRpc.JsonRpc+c__DisplayClass70_0.b__0()
at System.Threading.Tasks.Task`1[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].InnerInvoke()
at System.Threading.Tasks.Task.Execute()
at System.Threading.Tasks.Task.ExecutionContextCallback(System.Object)
at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.Tasks.Task.ExecuteWithThreadLocal(System.Threading.Tasks.Task ByRef)
at System.Threading.Tasks.Task.ExecuteEntry(Boolean)
at System.Threading.Tasks.Task.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
at System.Threading.ThreadPoolWorkQueue.Dispatch()
at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback()
@Jon try installing “Microsoft.Net.Compilers 2.2.0” NuGet package into the project, that helped me to get it back to work.
Thanks. However, Visual Studio fails and exits on me before I can do anything. It appears to do it for any project. Even for newly created simple projects such as a hello world console application. The only thing I’ve been able to get to work is going back to 15.0. However, I’ve been using .NET Framework 4.7 and support for that wasn’t added until 15.1. As far as I know, there is no way to update 15.0 without having it update all the way to 15.3. Microsoft: please provide an installer for 15.2. You have the 15.3 installer on MSDN. Why no publish the installers for 15.1 and 15.2? I’m stuck and cannot do any work until I get this resolved. If I go back to 15.0. Then, I get to go through the fun of having to downgrade all my projects of which there are many back to an older version of .NET Framework and then have to deal with the mess that that will cause with NuGet hell.
I found out what the problem was. There was a Newtonsoft Json assembly installed in the GAC. It was overriding what VS needed. I found the app that installed the DLL in the GAC and uninstalled it. That fixed the problem. Thanks to Jared from Microsoft and a few others who helped me with this. I still think Microsoft should provide installers for previous updates such as for 15.2, but, greatly appreciate Microsoft’s help getting me backup and running again.
I upgraded today and now having hard time debugging. I no longer see variables and their properties normally, I have to do some extra clicks in order to see properties of my variables. I got several crashes already trying to see the properties. How can I get my “normal” debugging back (e.g. ability to see variables with all their properties without a need for extra clicks)?
I got more crashes 🙁 I can not easily debug my code anymore.
@Naomi, Sorry that you are running into crashes. We are here to help and would love more information about what you are experiencing. Please email us at debugger[at]microsoft[dot]com with a detailed description of your scenario and any steps you take to reproduce the problem.
Hi Kaycee,
I emailed. I don’t know if the description I provided is enough, the crashes happen when I try to examine variables while debugging.
Hi Kaycee,
I generated the dump file according to the great instructions in this blog post http://blogs.msdn.com/b/debugger/archive/2009/12/30/what-is-a-dump-and-how-do-i-create-one.aspx
I only tried to debug 4 or 5 times since I installed this update and every single time I got a crash when I tried to examine variables. I’m waiting for the next response of Tom or someone else. Thanks.
I found a workaround for the debugger issue because it was seriously impacting my ability to work, too.
Go into Tools | Options | Environment | General.
Uncheck “Automatically adjust visual experience based on client performance” and uncheck “Use hardware graphics acceleration if available”.
In my experience, it is unfortunately very frequently a fix for all kinds of display crash bugs in Visual Studio. Previously I’ve only encountered them with the WPF designer and a couple of other designers. VS 2017 has been working so well with it checked for months that I almost forgot I’d checked it again. But it was my go-to culprit when I started getting crashes in my debugger when trying to use the hover debug tools and I saw missing glyphs and corrupted UI.
Thanks a lot, will do! I also uploaded my dump to diagnostics site.
Hi, when cancelling an update (eg from VS 15.2 to 15.3), do you have to reinstall the entire product? After cancelling, the “Update” button is replaced by a “Modify” button, which then leads to the workloads screen. My “update” now sits at 11.6GB.
Is this normal behaviour for the VS installer?
It’s normal, albeit confusing.
If you hit modify (which shows the details screen) and then install, it will continue with where it left off.
We’re actively looking into ways to clarify the user experience here. We understand this is not optimal. Thanks.
ver 15.3 is not an automatic update for vs2017? is this a “beta” release?
or now we all need to manually apply update?
>or now we all need to manually apply update?
Considering how MANY people ask for way to go back to 15.2 it would be VERY nice NOT to update automatically 🙂
Once per 1-3 months to do it manually – not a big deal. But updating automatically and breaking your whole work process – is BIG deal! … I think 😉
“Considering how MANY people ask for way to go back to 15.2”
why?
I would +1 an option to go back to 15.2. A solution that compiles and runs just fine in 15.2 is broken in 15.3:
System.IO.FileLoadException: ‘Could not load file or assembly ‘System.Net.Http, Version=4.1.1.1, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a’ or one of its dependencies. The located assembly’s manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)’
Lots of broken assembly references, but nothing in the project structure has changed – just the upgrade to 15.3. Since I can’t go back to 15.2, I’m dead in the water until I get to the root cause.
Thank you for the feedback. Please try the solution I posted at https://developercommunity.visualstudio.com/content/problem/95070/could-not-load-file-or-assembly-systemruntime-vers.html
But in Visual F# : file Program.fs that it can’t use “Backspace” . I tried my best to can use it that you have to create a new file *.fs . But when I restart Visual Emprise , I still get errors as . Thank you to hear from me !
How to turn off the function, which automatically set font size to 8 of any method, whose name is longer than 15 chars?
Hey Pavel – you may want to check your extensions to see if this behavior is caused by one of them. I don’t believe we have anything in the box that does this. Is this for C++ or a different language?
I upgraded to VS 2017 15.3, but .NET Core related templated missed in the installed project template.
Got Not Responding issues while trying to open existing .Net Core application.
Hi Jayakumar: I would like to investigate and figure out what is going on with your PC. I am not able to repro this. Can you please get in touch with me? jomorris@Microsoft.com. Please note that, .NET Core SDK 2.0 doesn’t come in-box with VS and you have to install it separately from https://www.microsoft.com/net/core. If you did not that step, please do that. And if you still have the issue, please follow-up with me
Setup operation failed
Log information:
Package ‘Microsoft.VisualStudio.WebDeploy.Msi,version=15.0.26711.1,chip=x64’ failed to install.
Search URL
https://aka.ms/VSSetupErrorReports?q=PackageId=Microsoft.VisualStudio.WebDeploy.Msi;PackageAction=Install;ReturnCode=30001
Details
MSI: C:\ProgramData\Microsoft\VisualStudio\Packages\Microsoft.VisualStudio.WebDeploy.Msi,version=15.0.26711.1,chip=x64\webdeploy_x64.msi, Properties: REBOOT=ReallySuppress
Return code: 30001
Return code details: Setup failed to detect shared configuration.
Log
C:\Users\rr194421\AppData\Local\Temp\dd_setup_20170816195213_001_Microsoft.VisualStudio.WebDeploy.Msi.log
Impacted workloads
.NET Core cross-platform development (Microsoft.VisualStudio.Workload.NetCoreTools,version=15.0.26720.2)
.NET desktop development (Microsoft.VisualStudio.Workload.ManagedDesktop,version=15.0.26606.0)
ASP.NET and web development (Microsoft.VisualStudio.Workload.NetWeb,version=15.0.26724.1)
Impacted components
ASP.NET and web development tools (Microsoft.VisualStudio.Component.Web,version=15.0.26606.0)
ASP.NET and web development tools (Microsoft.VisualStudio.ComponentGroup.Web,version=15.0.26606.0)
Azure Cloud Services core tools (Microsoft.VisualStudio.Component.Azure.Waverton,version=15.0.26208.0)
Cloud Explorer (Microsoft.VisualStudio.Component.CloudExplorer,version=15.0.26711.1)
Web Deploy (Microsoft.VisualStudio.Component.WebDeploy,version=15.0.26208.0)
Windows Communication Foundation (Microsoft.VisualStudio.Component.Wcf.Tooling,version=15.0.26606.0)
Hi Jayakumar: Please see my earlier comment. I think both issues are connected. So please work with me off-line to help me get a repro and investigate
Jayakumar – WebDeploy does not support Shared Configuration in IIS. Please turn off Shared Configuration in IIS and repair your VS instance. Thanks.
The other possibility is that IIS is denying VS Setup permissions to query shared configuration. You can verify this by trying to open IIS Manager and see if you can connect to the local machine without getting prompted for credentials . If you do get prompted for credentials, then you need to uninstall and reinstall IIS with the same account that you’re installing VS 2017 with.
Arghhh! Still no Live Unit Testing for UWP. Please don’t miss this out on the roadmap!
Live Unit Testing support for additional frameworks are in the to-do list and UWP is in that list. Thanks for the feedback.
Hi, my C++ application builds fine (Debug mode) with 15.3, but crashes as soon as I start it with the error:
Exception thrown at 0x017DDCB9 in myapp.exe: 0xC00000FD: Stack overflow (parameters: 0x00000000, 0x01C52000).
Going deeper, I see that the main thread crashes in the function __alloca_probe, called at the very beginning of my constructor.
011C24A0 push ebp
011C24A1 mov ebp,esp
011C24A3 push 0FFFFFFFFh
011C24A5 push 1842E36h
011C24AA mov eax,dword ptr fs:[00000000h]
011C24B0 push eax
011C24B1 mov eax,251FD10h
011C24B6 call __alloca_probe (010831ECh) <– crashes here
011C24BB push esi
011C24BC push edi
011C24BD push ecx
In this constructor, I allocate (in the heap) 3000 objects, so I expect to use 3000*4 = 12KB for the pointers in the stack.
Considering that 251FD10h (37MB) is the size passed via eax to __alloca_probe, I tried to increase the stack allocation size (/STACK linker option) to a larger size (48MB) and… my application stopped crashing!
Now I’d like to know why my 3000 pointers suddenly require that much memory in the stack. Note that my application has been working fine with all the previous versions of VS, from 10.0 to 15.2.
Thanks.
Cyril,
Could you please send me a direct email? My email address is firstname.lastname@microsoft.com. One of our code generation devs wants to chat with you.
Also, it would be really helpful if you could provide a preprocessed file. There are instructions at https://aka.ms/CompilerCrash.
Thank you!
Andrew
Hi Cyril,
I’m just a casual observer, but there are a couple of things about your question.
You say you alloca() in a constructor. Alloca is on the stack right, not the heap. You also sometimes say objects and sometimes say pointers. It might just be a clarification needed in your post.
Of course that doesn’t explain why it is 37MB vs 12K but it does rather sound like you are allocating objects not pointers.
Print out the value you are passing to alloca.
And if it is in a constructor, remember, that memory is going to disappear as soon as the ctor scope exits. It isn’t on the heap.
I assume you know what you are doing if you are using alloca but even the best of us make mistakes.
It is also possible that the language semantics may have subtly changed between versions, so really worth checking exactly how many bytes you are asking for.
Best
-chris
Is there someplace which explains all the interrelationships of the .NETs across different project types and builds?
Strictly for example, UWP seems to use .NET Core for Debug and then .NET Native(?) for Release. That’s something I had to stumble upon learning. Then I later stumbled upon learning that some .NET Core APIs can run faster, and even significantly faster, than their .NET Native counterparts.
However UWP apps released through the Store must be .NET Native(?) and NOT .NET Core. So this creates the VERY UNUSUAL concept of an app possibly actually running faster under a Debug build than its final Release build. Let’s face it, that is NOT something a developer would normally expect to happen.
But my question isn’t about the details I’ve mentioned. It’s about a “bigger picture” explanation of the .NET interrelationships across project types and builds so that I can stuff my brain with the knowledge it needs to better guestimate why some bug, quirk, etc, might be popping up in an app. That would be far better than my “stumbling upon learning” something important that would have been far better to plan for earlier in the development cycle.
I just hope you aren’t the person responsible for the 640MB PDF reader in the Windows Store…
That was a joke, I’m sure you aren’t.
The build variants certainly are complex at this point that is for sure. Maybe this is why this post is so chock full of issues, I don’t envy the VS team having to keep on top of all this stuff, it is insane.
I spent a good few hours recently understanding the versioning schemes for .Net and I agree, it really isn’t pretty.
At least I couldn’t find a central page that competently describes all the variations.
I thought the idea of .Net was one framework that runs everywhere. Need to keep a track on that ball.
Currently The definition of .Net is looking more similar to a quantum wave packet.
We used VS 2017 v15.2 to write some R codes. Everything is OK and the performance of editing code in R interactive is perfect.
We upgraded VS from v15.2 to v15.3 yesterday, and the speed of typing R code in R interactive became some slowly,,, it always takes about 2 or more seconds to show the intellisense panel. the same thing also happened when trying to edit a R code file. I had tried in several physical machines, and all machines installed the v15.3 have the same issue, while the machines with v15.2 are OK. We even try the way to uninstall the components related to R and reinstall it again, but nothing happened.
So we are wondering whether there is some change which has confliction with the R tools… Please kindly let us know if there are some tips to solve this issue. Thanks!
Hi netexplorer. Thanks for reporting this issue. We’ve already made a fix and have it queued up for the next servicing update to 15.3. So next time you see the notification pop up, make sure you grab the update and it should be fine.
On C++ projects and file, when renaming something with the refactoring tool (ctrl+R) the focus is lot to output window after changes are applied. Is it possible to revert back to the old behaviour (that is, the focus is reverted back to the code)?
Hello Allesio, thank you for reporting this issue. We are tracking this on our backlog as a bug, and it will be addressed in a future update to Visual Studio.
with the latest update of VS2017 15.3 my project (Xamarin.Forms with UWP and Android) is unable to compile.
Im using .NETStandard1.4 projects, using a lot of NuGet-Packages, like Xamarin.Forms etc.
To get this working in the project.json files it’s nessassary to do this:
“frameworks”: {
“netstandard1.4”: {
“imports”: “portable-net45+win8+wpa81+wp8”
}
everything worked fine, but after the VS update:
Error NU1202 Package MvvmLightLibs 5.3.0 is not compatible with netstandard1.4 (.NETStandard,Version=v1.4). Package
I can’t switch to .NETStandard2.0, because UWP isn’t ready for this, as I understand….
So I’m stuck…..
Same exact issue here! I’m now stuck and waiting…
Hi S. Ullrich, thanks for reporting this issue.
Would you please try adding following two lines are in your .NETStandard1.4 .csproj file?
netstandard1.4
$(PackageTargetFallback);portable-win+net45+wp8+win81+wpa8
This may solve you issue.
Kyle
The comment system must remove some formatting for security reasons. The two lines should be:
https://gist.github.com/kdubau/434be26266c613ff4f82b09eb2c30507
Hi Kyle,
with the PackageTargetFallback entry in the project file the solution compilies again. Thank you.
My Xamarin Forms app with .Net Standard 1.4 libraries doesn’t compile anymore! C’mon Microsoft !! I’m now stuck.
+1 Microsoft we need a downgrade path!
Hi folks,
Thanks for reporting the issue. Please try the solution posted above in response to the same issue.
https://blogs.msdn.microsoft.com/visualstudio/2017/08/14/visual-studio-2017-version-15-3-released/#comment-279876
We definitely need a way to get back to 15.2. As it is today, 15.3 is completely broken. So broken, my team can’t continue using it. We NEED a way to get back to 15.2.
The first thing that hits you after upgrading is how absurdly slow it is. At first we thought it could be some incompatibility with ReSharper, but for once ReSharper was innocent. I tried stripping VS down to only the web development tools and using professional instead of enterprise. Nope, this thing is slow.
The second thing is that it goes crazy with the references. Our project is an ASP.NET Core 1.1 app running on .NET 4.6.2. Some assemblies references .NET Standard 1.6.1 and the references brought in by this NuGet package gets screwed up. VS marks them with yellow triangles and claim they can’t be found. It does build though and the assemblies it “can’t find” are brought in to the bin folder. Although it brings in the .NET Standard 2.0 version. For example System.Runtime is referenced as 4.1.1 (4.3.0) from the NuGet package and the app.config has been updated by NuGet/VS to with binding redirects for 4.1.1. Although when VS/msbuild builds it brings in 4.1.2… and we have a runtime error. We can make it run by updating the app.configs to redirect to the versions in .net standard 2.0, but why does this happen. We have tried with SDK 1.1.0 and 1.0.4 in global.json, but the behavior is the same.
We need to go back to 15.2.
Note that when I talk about app.config, that is in our unit test projects. The web application itself runs, but the unit tests fail with can’t load assemblies. Unless we update the binding redirects with the wrong versions, the ones we don’t reference, our test projects fail to run. We had to use ilspy to get the version to use in the app.config. The csproj says 4.1.1 and the app.config said 4.1.1. The file on the other end of the hint path is 4.1.1, but he one ending up in the bin folder is 4.1.2…
Hi Halstein: Sorry to hear about the troubles you are experiencing after the upgrade. I want to help you out. From our side of validation, we are not able to repro this. Could you please work with me off-line to help investigate what is going on? jomorris@microsoft.com
+1 Microsoft for downgrade path!!!
After the upgrade to 15.3, I’m stuck with a broken Qt build (see https://developercommunity.visualstudio.com/content/problem/76198/vs-2017-compiler-creates-broken-debug-build-using.html ). I have no solution because of an VC++ bug (see https://connect.microsoft.com/VisualStudio/feedback/details/3136520/regression-static-initialisation-not-performed-for-types-with-constexpr-constructors).
It looks like there should be a way to fresh install 15.2 (I’m desperate) using https://docs.microsoft.com/en-us/visualstudio/install/use-command-line-parameters-to-install-visual-studio somehow, but there is no documentation on how to do it.
Can someone from Microsoft please comment on this?
For anyone who wishes to downgrade.
I was able to downgrade to 15.0 by downloading the 15.0 installer from https://my.visualstudio.com .
I uninstalled VS2017 15.3 completely and then installed 15.0.
For all – like me and my team – that need to go back to Visual Studio 2017 15.2 please vote here:
I suggest you provide an option to install Visual Studio 2017 15.2 or make it possible to update from 15.0 to 15.2
https://visualstudio.uservoice.com/forums/121579-visual-studio-ide/suggestions/31014391-provide-an-option-to-install-visual-studio-2017-15
Afraid I’ll lose everything when I OK this “An exception has been encountered. This may be caused by an extension.” (not an extension, just typing, copy/paste, then BAM!)
1426
2017/08/17 23:34:40.867
Error
Editor or Editor Extension
System.ArgumentException: The collections refer to different snapshots. at Microsoft.VisualStudio.Text.NormalizedSnapshotSpanCollection.Overlap(NormalizedSnapshotSpanCollection left, NormalizedSnapshotSpanCollection right) at
Microsoft.VisualStudio.UI.Text.Wpf.View.Implementation.Selection.HighContrast.HighContrastSelectionTagger.<InnerGetTags>d__17.MoveNext() at Microsoft.VisualStudio.Text.Tagging.Implementation.TagAggregator`1.<GetTagsForBuffer>d__39.MoveNext()
You should be alright hitting okay on that dialog, it’s usually shown when we handle an exception from an editor extension (either an external extension, or internal one). In this case, it’s an internal one. We’ll follow up and get a fix. Appreciate you reporting this!
Yay for the update, booh on it hanging every 2nd or 3rd time I try to open a studio.
Nothing happens, except that there is a devenv process eating 3mb of memory. Is this the splash screen malfunctioning?
Hi Drak
We’d like to understand your issue further. Could you please log it at https://developercommunity.visualstudio.com so we can investigate?
Cheers, Deniz
The Pen support is broken and crashes VS randomly every few minutes, but I already posted about this on that issue ticket.
I fixed that by disabling pen support as suggested.
Two more problems I am seeing though.
1) The output window, error window etc seem to want to jump to all kinds of different docking locations. Even worse, source files open in the same docking areas as the output window tab groups for no apparent reason. I tried resetting the window layout lots of times but it still does it. I have to manually restock the status windows pretty much every time I restart VS.
2) I added a new project to an existing dotnetcore solution, then added references to two of the other assemblies in the project then tried to build. It couldn’t find one of the DLL’s. So I poked around in the SLN file and apparently the GUID for the newly added project didn’t match the old ones. I fixed it manually and then the project built.
Btw. As I mentioned in that bug report, devenv.exe doesn’t say 15.3, it says 15.2.xxx. Odd.
It certainly isn’t “grammar.h” this time guys 😛
Looks like you have your hands full.
Cheers from Amsterdam 🙂
-chris
xxx
I wouldn’t count on them providing the download for 15.2. I always recommend that people keep the previous versions of things that tend to be flaky in new releases. For Visual Studio, I’ve personally kept the previous releases, but didn’t push others do it, because it was mostly stable. But as you’ve discovered, VS 2017 is vastly buggy and unstable compared to 2015 or 2013….click one thing here and there and it crashes. I actually went back to VS 2015 because 2017 crashed way too often for me.
Great tool, great share.
After the update, in many instances breakpoints will not be hit. The IDE reports that “The breakpoint will not currently be hit. The source code is different from the original version”. There is a workaround to force the breakpoint to be hit event when the sources are different, this was not the case prior to updating.
The application is simple asp.net core (.net core) webapi application, not using any special technique, migrated from 1.x to 2.0. The problem happens in multiple computers, all updated from VS15.2 to VS15.3. Cleaning and rebuilding has no effect.
Hi Alireza, We have a similar issue reported on the Developer Community at https://developercommunity.visualstudio.com/content/problem/97445/vs2017-the-breakpoint-will-not-currently-be-hit-no.html
We are currently investigating the problem and will post updates to the Developer Community site as we learn more.
For us, the solution was to choose “Delete all breakpoints” menu option.
Apparently, this clears some internal file.
Impossible to use it, my solution based on an Orchard CMS 1 fork is totally broken. The IDE starts wait loops after 2 or 3 actions then it crashes, automatically restarts and recrashes after some minutes.
Seems a badly tested work, certainly good ideas for azure behind. Killer on the bad way.
I will try one days to find a solution. Lost time. Tehn try to go back to prev version.
It seems that the auto-save is crashing…
c++ developers – avoid until heavily patched IMO. The 2017.2 version was finally working smoothly. With this one – extremely slow compilation times, build on solution folders doesn’t work any more, random crashes when parsing c++ files… These are just from the first few minutes. And I can’t roll back to 2017.3 because M$ doesn’t provide non-online installer… Great, I have serious project to work on, and I feel like a better tester…
*beta
Even Ctrl-F7 is broken again… It doesn’t compile the currently opened file. I remember this bug in a similar bad release, then it was fixed, and here it is again…
I’m not having any trouble with 2017.3 using the Enterprise version, however I am getting the same problem you have with Ctrl-F7, but weirdly I have the same setup at work and that one works fine.
On this PC I tried selecting another shortcut, but it also won’t initiate a compile so I think it is the Build.Compile command that is broken
Hello JJ99 and Stone Free,
Thank you for sharing your feedback. Not all user profiles have Ctrl+F7 defined to Compile. Please make sure that the keyboard shortcut is set to the desired “Build.Compile” command.
If this suggestion doesn’t work, we will be glad to work with you after submitting a “Report a Problem” via the link above.
Thanks
Felix Huang
VC++ Project and Build
Driver development?
We will be providing an installation experience for driver developers in the next release. The WDK installer will still be separate but the C++ tools for building drivers will be available inside Visual Studio 2017.
After installing 15.3.1 my projects no longer compile. The error is
“csc.exe” exited with code -2146232797
Ever since I started using local functions, I was getting occasionally this error for some local function, but when I converted them to Action or Func, they were working fine. I guess the new update further broken the local functions functionality. I’m wondering if there is a way to uninstall this update.
Great!, please keep it up
Being burned in the past by VS updates introducing bugs and crashes with our existing code base, I gave 15.3.0 / 15.3.1 a try on a physical test machine:
– XAMP Editor is still crashing all the time
– Navigating in WPF applications brings up CPU load to 30-50% and it never goes back again
– Existing WPF solutions fail to compile with obscure csc.exe errors
– native C/C++ debugger crashes all the time
– CTRL + F7 to compile C/C+ files does not work
– Random crashes at opening solutions
– Random crashes when compiling C++/CLI builds are broken
– And still NO WAY BACK to the previous version without a complete uninstall/install
I it looked up at user voice, and yes, all the problems above are already filed, among the over 600(!) bug reports already filed against 15.3. I can repeat myself: Do not install this on your productive system without pretesting your existing solutions on a test machine. If the new versions borkes your productive VS2017 installation, there is now way back, except a complete uninstall/reinstall!
Integration of .Net Core 2.0 is very appreciated, but obviously the WPF/native parts of VS have are suffering badly by all those changes.
I’m really starting the get angry, we pay a lot of money for VS, and we keep getting official updates ridden with bugs crashes.
This is the new Microsoft quality as a service first, mobile first, cloud first, telemetry first, ads first, and desktop never again.
Yep, that’s pretty accurate.
After an upgrade most of New Item templates are missing. Only some Code Analysis Rule Set etc are left. Can not create new c# or c++ source files.
https://i.gyazo.com/686d449c7723910d7b68a576f39b3590.png
Hello Igor, so if I am understanding things correctly, when you do Add > New Item on a .NET project, you do not get any options to add .NET source files, and if you do so on a C++ project, you do not get any options to add C++ source files, since updating to 15.3?
Hello, because of problems with installation of Visual Studio Professional 2017 15.3.1 update from 15.2 we need an official way to go back to 15.2, please tell me.
Kind Regards, Andreas.
Does this update contain any changes to system libraries like urlmon.dll? I’m asking because I use Igor Tandetnik “Passthrough APP” and after the update I suddenly got assertions in the default implementations of methods like IWinInetHttpInfo::QueryInfo.
Does this release support Crystal Reports yet?
No response? Must mean that the wizards at MS don’t realize the importance of legacy apps running in user environments and are totally focused on Azure.
Hi Dave
Thanks for asking. Visual Studio no longer supports Crystal Reports out of the box; please see our support article on this: https://support.microsoft.com/en-us/help/317789/support-for-crystal-reports-for-visual-studio; however, the following links from SAP and StackOverflow may help. Please note that these links and content within them are third party resources and are not authored or supported by Microsoft:
SAP – Crystal Reports, Developer for Visual Studio Downloads: https://wiki.scn.sap.com/wiki/display/BOBJ/Crystal+Reports%2C+Developer+for+Visual+Studio+Downloads
StackOverflow – How to integrate SAP Crystal Reports in Visual Studio 2017 https://stackoverflow.com/questions/42902740/how-to-integrate-sap-crystal-reports-in-visual-studio-2017
Hope this helps,
Deniz
Our TFS solution builds are now broken. The private TFS agent does not see the VS2017 install, and the workarounds for adding user capabilities are not working for us.
MSBuild steps will work if you explicitly point the step to the msbuild 15 exe on the filesystem.
We hit the same problem. Is there a fix for this? We’ve tried updating our build agents, but that didn’t help.
A couple of months ago we started to install Visual Studio 2017 from the downloads. After the installation many updates (with admin rights) where needed. After one week i recognized it was a preview release.
And now, once again, not one word it is a preview release!
Why didn’t you mention it is a preview release?
One thing which bothers me since I use .Net Core, is that you can not increment releases or patch releases.
Everything release needs something like version-rc-number, or version-preview-number, or other strange numbering schemes, hope this get cleared once in the future, because I am fed up googling around to understand with what i work.
Is it still necessary to have administrative permissions in order to create an offline installer via the /layout Switch?
This was a massive showstopper for us. Is it fixed?
Unfortunately, at this time the bootstrapper still requires admin privileges, even for the /layout operation. This is under consideration to be addressed in an upcoming release of Visual Studio.
How are we supposed to create an offline installer package to create a offline package which can be distributed within our company?
We are working in a highly regulated industry and we can get either internet access or admin permission – but never ever both.
We addressed the issue when the first version of VS 2017 was released and now the problem still exists.
We are stuck with VS 2015 U3.
Is support for crystal reports included?
No response? Must mean that the wizards at MS don’t realize the importance of legacy apps running in user environments and are totally focused on Azure.
Visual Studio hasn’t been bundled with Crystal Reports for years. It’s up to SAP to integrate with Visual Studio. According to a recent reply from Don Williams, SP21 will support VS2017 and will be out next week:
https://answers.sap.com/answers/292258/view.html
Hi, I installed Visual Studio 15.3 in order to get an update of CMake. When I open the folder it doesn’t detect CMakeFiles.txt and if I look in:
Common7\IDE\CommonExtensions\Microsoft
there is no CMake Folder.
Is there something special I need to do?
It sounds like the CMake tools component may have been unselected somehow in the installer. Can you double check the “Individual Components” tab in the Visual Studio Installer and see if “Visual C++ tools for CMake” is selected. The CMake tools are under the “Compilers, build tools, and runtimes” section.
If it is already selected, I would recommend repairing the installation. If that still doesn’t fix the issue please open a feedback ticket with the Report a Problem tool (https://docs.microsoft.com/en-us/visualstudio/ide/how-to-report-a-problem-with-visual-studio-2017).
This isnt an update, its a full install.
Thiks program seems to be getting less tested and more buggy as time goes on. This .3 version wouldnt even install, but it had no problem with destroying my existing working 15.2.
I got a current sum result of “run windows update” from support. You need to provide a rollback plan for when these “updates” dont work. Its not OK to leave customers in an unworkable state without any recourse.
After VS 2017.3 update TFS 2017 stops building projects
Why Razor intellisense for custom tag helpers does not works any more.
When VS2017 initially was released, razor intellisense for custom Tag Helpers did not worked.
After installing Razor Language Services extension it started working
Whit this release it stops again.
My razor Language Services is now at version 15.3.30918
And I am using custom tag helpers created by this nuget
https://www.nuget.org/packages/jQWidgets.AspNetCore.Mvc.TagHelpers/1.1.0
Hi Admir,
Sorry this isn’t working for you. There’s an issue caused by installing VS 15.3 on top of the early versions of the Razor Language Services that we uploaded to the VS Gallery.
Unfortunately the only fix for this is to repair Visual Studio. You can find some more details here https://github.com/aspnet/Razor/issues/1628
These features are now included with 15.3 and an additional download is no longer required.
Hi,
As we know, there is a unavoidable trade-off between releasing a product regularly to reflect user needs vs. testing the product thoroughly and making it stable.
It appears that the recent VS 2017 releases is notably sacrificing the product stability and usability due to continual releases. Adding to this, the lack of off-line installer (of course there is “vs_community.exe –layout” but is not as convenient and portable as an downlable ISO) and no support for downgrading!
We are a team of C#/C++ developers and have been waiting for VS 2017 since first days of 2017. We have tried and enjoyed the new features in VS 2017 releases on a test workstation. However, our team cannot switch to VS 2017 because of mentioned issues. I wonder how well VS 2017 is accepted and adopted internally among Microsoft teams.
I hope the upcoming releases of Visual Studio focus more on the stability and reliability.
Visual Studio 2017 Version 15.3 Released.This blog is the very helpful for work and the gain the information.And the Shear image is very helpful and the gain the information.
Thank you
Hi,
VS2017 not longer works with winobjc after the latest updates, can 15.2 be released so I can roll back
thanks
Sorry that this happened. We are engaged on this issue. Please see https://github.com/NuGet/Home/issues/5815 for the latest status.
It’s great to use the new visual studio 2017 features, but I’m afraid my computer is not up to the task of upgrading this version.
For all – like me and my team – that need to go back to Visual Studio 2017 15.2 please vote here:
I suggest you provide an option to install Visual Studio 2017 15.2 or make it possible to update from 15.0 to 15.2
https://visualstudio.uservoice.com/forums/121579-visual-studio-ide/suggestions/31014391-provide-an-option-to-install-visual-studio-2017-15
That’s it. We stopped our VS 2017 experiments and go back to VS2015. We will also not renew our MSDN subscriptions and stick with 2015. It costs a lot of money, and all we get is a row of buggy updates breaking our workflows.
Report back when you are ready to treat us as paying customers. No we won’t help you to fix your official releases wasting many developer hours we can’t charge to anyone.
Sorry for being harsh, but this is embarrassing.
getting Can not find compilation library location for package error after i installed 15.3. The solution completely works in 15.0 version,
is 15.3 causing this error??
Is it there a timeframe to make ASP.NET Core VB project templates available on VS 2017?
I am in the process of “updating” from 15.2 to 15.3
It’s now “updating” for more than 12 hours and it still shows only 82% “Acquiring Microsoft Visual Studio…” but it is not stalled and continues to work.
I have asked this question before and never got an answer (it is not the first time: what is the purpose of the blog if you refuse to anwer? why waste your “customers” time?): why does it take more than 12hrs to update your product while all your competitors can do it in between 1mn and 5 mn ?
I have tried to think about all scenarios and can’t find any possible reason:
a) your are hashing all the file of my computer: your built-in windows anti-virus already does that and there is no need to repeat it.
b) you are transmitting all our files to your servers: even if you would be doing this (which is probably what you are not doing though we are talking about Microsoft here, so anything is thinkable), it would not take that long given the computer we are using for this download sufficient big files.
Given that your product is sub-par, it STILL does not c++ compliance no where at the level of your competitors, it is super slow to compile, etc, so they should in theory be less to donwload and install, I’ll repeat AGAIN my question:
What is the reason that it takes > 12 hours to install … an UPDATE !!!!!
Hi @programmer, thanks for the comment – and I’m sorry for your frustration with the updater. 12 hours is certainly far from the norm – not that it helps you, but average update times for this feature update are in the 10-20 minute range.
Visual Studio is made up of hundreds of individual components: the core shell, Roslyn, language services, Windows SDKs, and other frameworks, tools and runtimes. At a high level, during the update we compare the component versions on your machine with the version in the manifest for the update and download any later versions. In parallel, we uninstall outdated components and install newer components that have been downloaded. In short, the process is very similar to how most package managers operate. For the avoidance of doubt, we don’t hash all the files on your computer nor transfer downloaded components back to our servers.
As to your machine, we’d need to look at the logs to figure out what’s going on. The logs are stored in the %TEMP% folder, and if you look for the most recent file named dd_setup_[TIMESTAMP].log, you’ll be able to see a blow-by-blow account of what it has been doing. My speculation is that you had difficulties downloading an updated component, whether because of internet issues or something else – but of course, that really is speculation. If you see something that looks like a bug on our side, please feel free to file a feedback ticket using the Submit a Problem button in the title bar of the Visual Studio Installer, and someone will take a look.
Lastly, I’m not an expert on C++ standards conformance, but I know the team has invested heavily in the latest releases and the Visual Studio 2017 compiler is now complete for features added in the C++14 Standard, with significant improvements in C++17 support in the 15.3 release. More details here: https://docs.microsoft.com/en-us/cpp/cpp-conformance-improvements-2017
Hopefully that helps a little – and apologies for your sub-par experience.
Warm wishes, Tim Sneath | Visual Studio Team
There are lots of files in the %TEMP% directory
The first one is titled
dd_setup_20170906142022_001_Microsoft.VisualStudio.Web.Mvc.Common.log
modified time: 9/6/2017 14:20pm EST
The last one is:
dd_setup_20170906142022_185_Microsoft.VisualStudio.XamlShared.Resources
modified time: 9/7/2017 9:21am EST
Then fully fed up I cancelled. So only 7h to installed 82% of the… update!
There are no errors in the logs.
Example of 3 randomly selected log file:
FILE 1
=== Verbose logging started: 9/6/2017 19:45:59 Build type: SHIP UNICODE 5.00.7601.00 Calling process: C:\Program Files\Microsoft Visual Studio\Installer\resources\app\ServiceHub\Hosts\Microsoft.ServiceHub.Host.CLR\vs_installerservice.exe ===
MSI (c) (2C:04) [19:45:59:781]: Resetting cached policy values
MSI (c) (2C:04) [19:45:59:781]: Machine policy value ‘Debug’ is 0
MSI (c) (2C:04) [19:45:59:781]: ******* RunEngine:
******* Product: {D48B2CE7-F6B3-4BDD-B9D9-91DEE8668314}
******* Action:
******* CommandLine: **********
MSI (c) (2C:04) [19:45:59:786]: Client-side and UI is none or basic: Running entire install on the server.
MSI (c) (2C:04) [19:45:59:790]: Grabbed execution mutex.
MSI (c) (2C:04) [19:46:00:822]: Cloaking enabled.
MSI (c) (2C:04) [19:46:00:822]: Attempting to enable all disabled privileges before calling Install on Server
MSI (c) (2C:04) [19:46:00:824]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (F4:3C) [19:46:01:326]: Running installation inside multi-package transaction {D48B2CE7-F6B3-4BDD-B9D9-91DEE8668314}
MSI (s) (F4:3C) [19:46:01:326]: Grabbed execution mutex.
MSI (s) (F4:0C) [19:46:01:632]: Resetting cached policy values
MSI (s) (F4:0C) [19:46:01:632]: Machine policy value ‘Debug’ is 0
MSI (s) (F4:0C) [19:46:01:632]: ******* RunEngine:
******* Product: {D48B2CE7-F6B3-4BDD-B9D9-91DEE8668314}
******* Action:
******* CommandLine: **********
MSI (s) (F4:0C) [19:46:01:632]: Machine policy value ‘DisableUserInstalls’ is 0
MSI (s) (F4:0C) [19:46:01:746]: SRSetRestorePoint skipped for this transaction.
MSI (s) (F4:0C) [19:46:01:746]: End dialog not enabled
MSI (s) (F4:0C) [19:46:01:746]: Original package ==> C:\Windows\Installer\3dac471.msi
MSI (s) (F4:0C) [19:46:01:746]: Package we’re running from ==> C:\Windows\Installer\3dac471.msi
MSI (s) (F4:0C) [19:46:01:746]: APPCOMPAT: Uninstall Flags override found.
MSI (s) (F4:0C) [19:46:01:746]: APPCOMPAT: Uninstall VersionNT override found.
MSI (s) (F4:0C) [19:46:01:746]: APPCOMPAT: Uninstall ServicePackLevel override found.
MSI (s) (F4:0C) [19:46:01:749]: APPCOMPAT: looking for appcompat database entry with ProductCode ‘{D48B2CE7-F6B3-4BDD-B9D9-91DEE8668314}’.
MSI (s) (F4:0C) [19:46:01:749]: APPCOMPAT: no matching ProductCode found in database.
MSI (s) (F4:0C) [19:46:01:778]: MSCOREE not loaded loading copy from system32
MSI (s) (F4:0C) [19:46:01:922]: Note: 1: 2205 2: 3: MsiFileHash
MSI (s) (F4:0C) [19:46:01:922]: Machine policy value ‘DisablePatch’ is 0
MSI (s) (F4:0C) [19:46:01:922]: Machine policy value ‘AllowLockdownPatch’ is 0
MSI (s) (F4:0C) [19:46:01:922]: Machine policy value ‘DisableLUAPatching’ is 0
MSI (s) (F4:0C) [19:46:01:922]: Machine policy value ‘DisableFlyWeightPatching’ is 0
MSI (s) (F4:0C) [19:46:02:003]: APPCOMPAT: looking for appcompat database entry with ProductCode ‘{D48B2CE7-F6B3-4BDD-B9D9-91DEE8668314}’.
MSI (s) (F4:0C) [19:46:02:003]: APPCOMPAT: no matching ProductCode found in database.
MSI (s) (F4:0C) [19:46:02:003]: Transforms are not secure.
MSI (s) (F4:0C) [19:46:02:003]: PROPERTY CHANGE: Adding MsiLogFileLocation property. Its value is ‘C:\Users\iguazu_w7_32\AppData\Local\Temp\dd_setup_20170906142022_155_Microsoft.DiagnosticsHub.Collection.Service.log’.
MSI (s) (F4:0C) [19:46:02:003]: Command Line: REBOOT=ReallySuppress ARPSYSTEMCOMPONENT=1 VSEXTUI=1 VSFOLDER=C:\Program Files\Microsoft Visual Studio\Shared IGNOREDEPENDENCIES=ALL REMOVE=ALL CURRENTDIRECTORY=C:\Program Files\Microsoft Visual Studio\Installer\resources\app\ServiceHub\Hosts\Microsoft.ServiceHub.Host.CLR CLIENTUILEVEL=3 MSICLIENTUSESEXTERNALUI=1 CLIENTPROCESSID=3372
MSI (s) (F4:0C) [19:46:02:003]: PROPERTY CHANGE: Adding PackageCode property. Its value is ‘{EC392FC9-CE28-4B6E-8632-F511B57B5626}’.
MSI (s) (F4:0C) [19:46:02:003]: Product Code passed to Engine.Initialize: ‘{D48B2CE7-F6B3-4BDD-B9D9-91DEE8668314}’
MSI (s) (F4:0C) [19:46:02:003]: Product Code from property table before transforms: ‘{D48B2CE7-F6B3-4BDD-B9D9-91DEE8668314}’
MSI (s) (F4:0C) [19:46:02:003]: Product Code from property table after transforms: ‘{D48B2CE7-F6B3-4BDD-B9D9-91DEE8668314}’
MSI (s) (F4:0C) [19:46:02:003]: Product registered: entering maintenance mode
MSI (s) (F4:0C) [19:46:02:003]: Determined that existing product (either this product or the product being upgraded with a patch) is installed per-machine.
MSI (s) (F4:0C) [19:46:02:003]: Product {D48B2CE7-F6B3-4BDD-B9D9-91DEE8668314} is admin assigned: LocalSystem owns the publish key.
MSI (s) (F4:0C) [19:46:02:003]: Product {D48B2CE7-F6B3-4BDD-B9D9-91DEE8668314} is managed.
MSI (s) (F4:0C) [19:46:02:003]: MSI_LUA: Credential prompt not required, user is an admin
MSI (s) (F4:0C) [19:46:02:003]: PROPERTY CHANGE: Adding ProductState property. Its value is ‘5’.
MSI (s) (F4:0C) [19:46:02:004]: PROPERTY CHANGE: Adding ProductToBeRegistered property. Its value is ‘1’.
MSI (s) (F4:0C) [19:46:02:004]: Note: 1: 1402 2: HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer 3: 2
MSI (s) (F4:0C) [19:46:02:004]: Package name retrieved from configuration data: ‘Microsoft.DiagnosticsHub.Collection.Service.Msi.msi’
MSI (s) (F4:0C) [19:46:02:004]: Note: 1: 2205 2: 3: Error
MSI (s) (F4:0C) [19:46:02:087]: Note: 1: 2262 2: AdminProperties 3: -2147287038
MSI (s) (F4:0C) [19:46:02:087]: Machine policy value ‘DisableMsi’ is 0
MSI (s) (F4:0C) [19:46:02:087]: Machine policy value ‘AlwaysInstallElevated’ is 0
MSI (s) (F4:0C) [19:46:02:087]: User policy value ‘AlwaysInstallElevated’ is 0
MSI (s) (F4:0C) [19:46:02:087]: Product {D48B2CE7-F6B3-4BDD-B9D9-91DEE8668314} is admin assigned: LocalSystem owns the publish key.
MSI (s) (F4:0C) [19:46:02:087]: Product {D48B2CE7-F6B3-4BDD-B9D9-91DEE8668314} is managed.
MSI (s) (F4:0C) [19:46:02:087]: Running product ‘{D48B2CE7-F6B3-4BDD-B9D9-91DEE8668314}’ with elevated privileges: Product is assigned.
MSI (s) (F4:0C) [19:46:02:087]: PROPERTY CHANGE: Adding REBOOT property. Its value is ‘ReallySuppress’.
MSI (s) (F4:0C) [19:46:02:087]: PROPERTY CHANGE: Adding ARPSYSTEMCOMPONENT property. Its value is ‘1’.
MSI (s) (F4:0C) [19:46:02:087]: PROPERTY CHANGE: Adding VSEXTUI property. Its value is ‘1’.
MSI (s) (F4:0C) [19:46:02:087]: PROPERTY CHANGE: Adding VSFOLDER property. Its value is ‘C:\Program Files\Microsoft Visual Studio\Shared’.
MSI (s) (F4:0C) [19:46:02:087]: PROPERTY CHANGE: Adding IGNOREDEPENDENCIES property. Its value is ‘ALL’.
MSI (s) (F4:0C) [19:46:02:087]: PROPERTY CHANGE: Adding REMOVE property. Its value is ‘ALL’.
MSI (s) (F4:0C) [19:46:02:087]: PROPERTY CHANGE: Adding CURRENTDIRECTORY property. Its value is ‘C:\Program Files\Microsoft Visual Studio\Installer\resources\app\ServiceHub\Hosts\Microsoft.ServiceHub.Host.CLR’.
MSI (s) (F4:0C) [19:46:02:087]: PROPERTY CHANGE: Adding CLIENTUILEVEL property. Its value is ‘3’.
MSI (s) (F4:0C) [19:46:02:087]: PROPERTY CHANGE: Adding MSICLIENTUSESEXTERNALUI property. Its value is ‘1’.
MSI (s) (F4:0C) [19:46:02:087]: PROPERTY CHANGE: Adding CLIENTPROCESSID property. Its value is ‘3372’.
MSI (s) (F4:0C) [19:46:02:087]: Machine policy value ‘DisableAutomaticApplicationShutdown’ is 0
MSI (s) (F4:0C) [19:46:02:096]: PROPERTY CHANGE: Adding MsiRestartManagerSessionKey property. Its value is ’60fa6cd20dcbbe4b84d6a46443a93edc’.
MSI (s) (F4:0C) [19:46:02:100]: RESTART MANAGER: Session opened.
MSI (s) (F4:0C) [19:46:02:100]: TRANSFORMS property is now:
MSI (s) (F4:0C) [19:46:02:100]: PROPERTY CHANGE: Adding PRODUCTLANGUAGE property. Its value is ‘1033’.
MSI (s) (F4:0C) [19:46:02:100]: PROPERTY CHANGE: Adding VersionDatabase property. Its value is ‘300’.
MSI (s) (F4:0C) [19:46:02:106]: SHELL32::SHGetFolderPath returned: C:\Users\iguazu_w7_32\AppData\Roaming
MSI (s) (F4:0C) [19:46:02:112]: SHELL32::SHGetFolderPath returned: C:\Users\iguazu_w7_32\Favorites
MSI (s) (F4:0C) [19:46:02:112]: SHELL32::SHGetFolderPath returned: C:\Users\iguazu_w7_32\AppData\Roaming\Microsoft\Windows\Network Shortcuts
MSI (s) (F4:0C) [19:46:02:112]: SHELL32::SHGetFolderPath returned: C:\Users\iguazu_w7_32\Documents
MSI (s) (F4:0C) [19:46:02:112]: SHELL32::SHGetFolderPath returned: C:\Users\iguazu_w7_32\AppData\Roaming\Microsoft\Windows\Printer Shortcuts
MSI (s) (F4:0C) [19:46:02:112]: SHELL32::SHGetFolderPath returned: C:\Users\iguazu_w7_32\AppData\Roaming\Microsoft\Windows\Recent
MSI (s) (F4:0C) [19:46:02:117]: SHELL32::SHGetFolderPath returned: C:\Users\iguazu_w7_32\AppData\Roaming\Microsoft\Windows\SendTo
MSI (s) (F4:0C) [19:46:02:118]: SHELL32::SHGetFolderPath returned: C:\Users\iguazu_w7_32\AppData\Roaming\Microsoft\Windows\Templates
MSI (s) (F4:0C) [19:46:02:118]: SHELL32::SHGetFolderPath returned: C:\ProgramData
MSI (s) (F4:0C) [19:46:02:118]: SHELL32::SHGetFolderPath returned: C:\Users\iguazu_w7_32\AppData\Local
MSI (s) (F4:0C) [19:46:02:118]: SHELL32::SHGetFolderPath returned: C:\Users\iguazu_w7_32\Pictures
MSI (s) (F4:0C) [19:46:02:118]: SHELL32::SHGetFolderPath returned: C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Administrative Tools
MSI (s) (F4:0C) [19:46:02:121]: SHELL32::SHGetFolderPath returned: C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Startup
MSI (s) (F4:0C) [19:46:02:127]: SHELL32::SHGetFolderPath returned: C:\ProgramData\Microsoft\Windows\Start Menu\Programs
MSI (s) (F4:0C) [19:46:02:142]: SHELL32::SHGetFolderPath returned: C:\ProgramData\Microsoft\Windows\Start Menu
MSI (s) (F4:0C) [19:46:02:163]: SHELL32::SHGetFolderPath returned: C:\Users\Public\Desktop
MSI (s) (F4:0C) [19:46:02:174]: SHELL32::SHGetFolderPath returned: C:\Users\iguazu_w7_32\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Administrative Tools
MSI (s) (F4:0C) [19:46:02:175]: SHELL32::SHGetFolderPath returned: C:\Users\iguazu_w7_32\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup
MSI (s) (F4:0C) [19:46:02:177]: SHELL32::SHGetFolderPath returned: C:\Users\iguazu_w7_32\AppData\Roaming\Microsoft\Windows\Start Menu\Programs
MSI (s) (F4:0C) [19:46:02:252]: SHELL32::SHGetFolderPath returned: C:\Users\iguazu_w7_32\AppData\Roaming\Microsoft\Windows\Start Menu
MSI (s) (F4:0C) [19:46:02:310]: SHELL32::SHGetFolderPath returned: C:\Users\iguazu_w7_32\Desktop
MSI (s) (F4:0C) [19:46:02:312]: SHELL32::SHGetFolderPath returned: C:\ProgramData\Microsoft\Windows\Templates
MSI (s) (F4:0C) [19:46:02:312]: SHELL32::SHGetFolderPath returned: C:\Windows\Fonts
MSI (s) (F4:0C) [19:46:02:312]: Note: 1: 2898 2: MS Sans Serif 3: MS Sans Serif 4: 0 5: 16
MSI (s) (F4:0C) [19:46:02:367]: MSI_LUA: Setting AdminUser property to 1 because the product is already installed managed and per-machine
MSI (s) (F4:0C) [19:46:02:367]: MSI_LUA: Setting MsiRunningElevated property to 1 because the install is already running elevated.
MSI (s) (F4:0C) [19:46:02:367]: PROPERTY CHANGE: Adding MsiRunningElevated property. Its value is ‘1’.
MSI (s) (F4:0C) [19:46:02:367]: PROPERTY CHANGE: Adding Privileged property. Its value is ‘1’.
MSI (s) (F4:0C) [19:46:02:367]: Note: 1: 1402 2: HKEY_CURRENT_USER\Software\Microsoft\MS Setup (ACME)\User Info 3: 2
MSI (s) (F4:0C) [19:46:02:367]: PROPERTY CHANGE: Adding USERNAME property. Its value is ‘iguazu_w7_32′.
MSI (s) (F4:0C) [19:46:02:367]: Note: 1: 1402 2: HKEY_CURRENT_USER\Software\Microsoft\MS Setup (ACME)\User Info 3: 2
MSI (s) (F4:0C) [19:46:02:367]: PROPERTY CHANGE: Adding Installed property. Its value is ’00:00:00’.
MSI (s) (F4:0C) [19:46:02:367]: PROPERTY CHANGE: Adding DATABASE property. Its value is ‘C:\Windows\Installer\3dac471.msi’.
MSI (s) (F4:0C) [19:46:02:367]: PROPERTY CHANGE: Adding OriginalDatabase property. Its value is ‘C:\Windows\Installer\3dac471.msi’.
MSI (s) (F4:0C) [19:46:02:367]: Machine policy value ‘MsiDisableEmbeddedUI’ is 0
MSI (s) (F4:0C) [19:46:02:367]: EEUI – Disabling MsiEmbeddedUI due to existing external or embedded UI
MSI (s) (F4:0C) [19:46:02:367]: EEUI – Disabling MsiEmbeddedUI for service because it’s not a quiet/basic install
MSI (s) (F4:0C) [19:46:02:660]: Note: 1: 2205 2: 3: PatchPackage
MSI (s) (F4:0C) [19:46:02:661]: Machine policy value ‘DisableRollback’ is 0
MSI (s) (F4:0C) [19:46:02:661]: User policy value ‘DisableRollback’ is 0
MSI (s) (F4:0C) [19:46:02:661]: PROPERTY CHANGE: Adding UILevel property. Its value is ‘2’.
=== Logging started: 9/6/2017 19:46:02 ===
MSI (s) (F4:0C) [19:46:02:664]: PROPERTY CHANGE: Adding Preselected property. Its value is ‘1’.
MSI (s) (F4:0C) [19:46:02:666]: PROPERTY CHANGE: Adding ACTION property. Its value is ‘INSTALL’.
MSI (s) (F4:0C) [19:46:02:666]: Doing action: INSTALL
MSI (s) (F4:0C) [19:46:02:666]: Note: 1: 2205 2: 3: ActionText
Action start 19:46:02: INSTALL.
MSI (s) (F4:0C) [19:46:02:672]: Running ExecuteSequence
MSI (s) (F4:0C) [19:46:02:672]: Doing action: FindRelatedProducts
MSI (s) (F4:0C) [19:46:02:672]: Note: 1: 2205 2: 3: ActionText
MSI (s) (F4:0C) [19:46:02:672]: Skipping FindRelatedProducts action: not run in maintenance mode
Action start 19:46:02: FindRelatedProducts.
MSI (s) (F4:0C) [19:46:02:673]: Doing action: LaunchConditions
MSI (s) (F4:0C) [19:46:02:673]: Note: 1: 2205 2: 3: ActionText
Action ended 19:46:02: FindRelatedProducts. Return value 0.
Action start 19:46:02: LaunchConditions.
MSI (s) (F4:0C) [19:46:02:673]: Doing action: ValidateProductID
MSI (s) (F4:0C) [19:46:02:673]: Note: 1: 2205 2: 3: ActionText
Action ended 19:46:02: LaunchConditions. Return value 1.
Action start 19:46:02: ValidateProductID.
MSI (s) (F4:0C) [19:46:02:675]: Skipping action: BlockInstallIfNotInBundle (condition is false)
MSI (s) (F4:0C) [19:46:02:675]: Doing action: CostInitialize
MSI (s) (F4:0C) [19:46:02:675]: Note: 1: 2205 2: 3: ActionText
Action ended 19:46:02: ValidateProductID. Return value 1.
MSI (s) (F4:0C) [19:46:02:675]: Machine policy value ‘MaxPatchCacheSize’ is 10
MSI (s) (F4:0C) [19:46:02:676]: PROPERTY CHANGE: Adding ROOTDRIVE property. Its value is ‘C:\’.
MSI (s) (F4:0C) [19:46:02:676]: PROPERTY CHANGE: Adding CostingComplete property. Its value is ‘0’.
MSI (s) (F4:0C) [19:46:02:676]: Note: 1: 2205 2: 3: Patch
MSI (s) (F4:0C) [19:46:02:676]: Note: 1: 2205 2: 3: PatchPackage
MSI (s) (F4:0C) [19:46:02:676]: Note: 1: 2205 2: 3: MsiPatchHeaders
MSI (s) (F4:0C) [19:46:02:676]: Note: 1: 2205 2: 3: __MsiPatchFileList
MSI (s) (F4:0C) [19:46:02:676]: Note: 1: 2205 2: 3: PatchPackage
MSI (s) (F4:0C) [19:46:02:676]: Note: 1: 2228 2: 3: PatchPackage 4: SELECT `DiskId`, `PatchId`, `LastSequence` FROM `Media`, `PatchPackage` WHERE `Media`.`DiskId`=`PatchPackage`.`Media_` ORDER BY `DiskId`
MSI (s) (F4:0C) [19:46:02:676]: Note: 1: 2205 2: 3: Patch
Action start 19:46:02: CostInitialize.
MSI (s) (F4:0C) [19:46:02:676]: Doing action: FileCost
MSI (s) (F4:0C) [19:46:02:676]: Note: 1: 2205 2: 3: ActionText
Action ended 19:46:02: CostInitialize. Return value 1.
MSI (s) (F4:0C) [19:46:02:679]: Note: 1: 2205 2: 3: MsiAssembly
MSI (s) (F4:0C) [19:46:02:681]: Note: 1: 2205 2: 3: Class
MSI (s) (F4:0C) [19:46:02:681]: Note: 1: 2205 2: 3: Extension
MSI (s) (F4:0C) [19:46:02:681]: Note: 1: 2205 2: 3: TypeLib
Action start 19:46:02: FileCost.
MSI (s) (F4:0C) [19:46:02:684]: Doing action: CostFinalize
MSI (s) (F4:0C) [19:46:02:684]: Note: 1: 2205 2: 3: ActionText
Action ended 19:46:02: FileCost. Return value 1.
MSI (s) (F4:0C) [19:46:02:691]: PROPERTY CHANGE: Adding OutOfDiskSpace property. Its value is ‘0’.
MSI (s) (F4:0C) [19:46:02:691]: PROPERTY CHANGE: Adding OutOfNoRbDiskSpace property. Its value is ‘0’.
MSI (s) (F4:0C) [19:46:02:691]: PROPERTY CHANGE: Adding PrimaryVolumeSpaceAvailable property. Its value is ‘0’.
MSI (s) (F4:0C) [19:46:02:691]: PROPERTY CHANGE: Adding PrimaryVolumeSpaceRequired property. Its value is ‘0’.
MSI (s) (F4:0C) [19:46:02:691]: PROPERTY CHANGE: Adding PrimaryVolumeSpaceRemaining property. Its value is ‘0’.
MSI (s) (F4:0C) [19:46:02:696]: Note: 1: 2205 2: 3: MsiAssembly
MSI (s) (F4:0C) [19:46:02:696]: Note: 1: 2228 2: 3: MsiAssembly 4: SELECT `MsiAssembly`.`Attributes`, `MsiAssembly`.`File_Application`, `MsiAssembly`.`File_Manifest`, `Component`.`KeyPath` FROM `MsiAssembly`, `Component` WHERE `MsiAssembly`.`Component_` = `Component`.`Component` AND `MsiAssembly`.`Component_` = ?
MSI (s) (F4:0C) [19:46:02:696]: PROPERTY CHANGE: Adding DiagnosticsHub_Collection_SubFolder_x86 property. Its value is ‘C:\Program Files\Microsoft Visual Studio\Shared\Common\DiagnosticsHub.Collection.Service\x86’.
MSI (s) (F4:0C) [19:46:02:696]: PROPERTY CHANGE: Adding DiagnosticsHub_Collection property. Its value is ‘C:\Program Files\Microsoft Visual Studio\Shared\Common\DiagnosticsHub.Collection.Service’.
MSI (s) (F4:0C) [19:46:02:699]: Note: 1: 2205 2: 3: Patch
MSI (s) (F4:0C) [19:46:02:700]: Note: 1: 2205 2: 3: Condition
MSI (s) (F4:0C) [19:46:02:702]: PROPERTY CHANGE: Adding TARGETDIR property. Its value is ‘C:\’.
MSI (s) (F4:0C) [19:46:02:702]: PROPERTY CHANGE: Modifying VSFOLDER property. Its current value is ‘C:\Program Files\Microsoft Visual Studio\Shared’. Its new value: ‘C:\Program Files\Microsoft Visual Studio\Shared\’.
MSI (s) (F4:0C) [19:46:02:702]: PROPERTY CHANGE: Adding VSCommon property. Its value is ‘C:\Program Files\Microsoft Visual Studio\Shared\Common\’.
MSI (s) (F4:0C) [19:46:02:702]: PROPERTY CHANGE: Modifying DiagnosticsHub_Collection property. Its current value is ‘C:\Program Files\Microsoft Visual Studio\Shared\Common\DiagnosticsHub.Collection.Service’. Its new value: ‘C:\Program Files\Microsoft Visual Studio\Shared\Common\DiagnosticsHub.Collection.Service\’.
MSI (s) (F4:0C) [19:46:02:705]: PROPERTY CHANGE: Modifying DiagnosticsHub_Collection_SubFolder_x86 property. Its current value is ‘C:\Program Files\Microsoft Visual Studio\Shared\Common\DiagnosticsHub.Collection.Service\x86’. Its new value: ‘C:\Program Files\Microsoft Visual Studio\Shared\Common\DiagnosticsHub.Collection.Service\x86\’.
MSI (s) (F4:0C) [19:46:02:705]: Target path resolution complete. Dumping Directory table…
MSI (s) (F4:0C) [19:46:02:705]: Note: target paths subject to change (via custom actions or browsing)
MSI (s) (F4:0C) [19:46:02:705]: Dir (target): Key: TARGETDIR , Object: C:\
MSI (s) (F4:0C) [19:46:02:705]: Dir (target): Key: WindowsFolder , Object: C:\Windows\
MSI (s) (F4:0C) [19:46:02:705]: Dir (target): Key: ProgramFilesFolder , Object: C:\Program Files\
MSI (s) (F4:0C) [19:46:02:705]: Dir (target): Key: VSFOLDER , Object: C:\Program Files\Microsoft Visual Studio\Shared\
MSI (s) (F4:0C) [19:46:02:705]: Dir (target): Key: VSCommon , Object: C:\Program Files\Microsoft Visual Studio\Shared\Common\
MSI (s) (F4:0C) [19:46:02:705]: Dir (target): Key: DiagnosticsHub_Collection , Object: C:\Program Files\Microsoft Visual Studio\Shared\Common\DiagnosticsHub.Collection.Service\
MSI (s) (F4:0C) [19:46:02:705]: Dir (target): Key: DiagnosticsHub_Collection_SubFolder_x86 , Object: C:\Program Files\Microsoft Visual Studio\Shared\Common\DiagnosticsHub.Collection.Service\x86\
MSI (s) (F4:0C) [19:46:02:705]: PROPERTY CHANGE: Adding INSTALLLEVEL property. Its value is ‘1’.
Action start 19:46:02: CostFinalize.
MSI (s) (F4:0C) [19:46:02:709]: Doing action: MigrateFeatureStates
MSI (s) (F4:0C) [19:46:02:709]: Note: 1: 2205 2: 3: ActionText
Action ended 19:46:02: CostFinalize. Return value 1.
MSI (s) (F4:0C) [19:46:02:711]: Skipping MigrateFeatureStates action: not run in maintenance mode
Action start 19:46:02: MigrateFeatureStates.
MSI (s) (F4:0C) [19:46:02:711]: Doing action: InstallValidate
MSI (s) (F4:0C) [19:46:02:711]: Note: 1: 2205 2: 3: ActionText
Action ended 19:46:02: MigrateFeatureStates. Return value 0.
MSI (s) (F4:0C) [19:46:02:712]: PROPERTY CHANGE: Deleting MsiRestartManagerSessionKey property. Its current value is ’60fa6cd20dcbbe4b84d6a46443a93edc’.
MSI (s) (F4:0C) [19:46:02:712]: Note: 1: 2205 2: 3: Dialog
MSI (s) (F4:0C) [19:46:02:712]: Feature: DiagnosticsHub_Collection_Service; Installed: Local; Request: Absent; Action: Absent
MSI (s) (F4:0C) [19:46:02:712]: Component: DiagnosticsHub.StandardCollector.Host.Proxy.dll_x86; Installed: Local; Request: Absent; Action: Absent
MSI (s) (F4:0C) [19:46:02:712]: Component: StandardCollector.Service.exe_x86; Installed: Local; Request: Absent; Action: Absent
MSI (s) (F4:0C) [19:46:02:712]: Component: StandardCollector.Service.exe_Host_AppIDRegistration_x86; Installed: Local; Request: Absent; Action: Absent
MSI (s) (F4:0C) [19:46:02:712]: Component: StandardCollector.Service.exe_Host_CLSIDRegistration_x86; Installed: Local; Request: Absent; Action: Absent
MSI (s) (F4:0C) [19:46:02:712]: Component: __StandardCollector.Service.exe_Host_AppIDRegistration_x8665; Installed: Null; Request: Absent; Action: Absent
MSI (s) (F4:0C) [19:46:02:712]: Component: __StandardCollector.Service.exe_Host_CLSIDRegistration_x8665; Installed: Null; Request: Absent; Action: Absent
MSI (s) (F4:0C) [19:46:02:712]: Component: __DiagnosticsHub.StandardCollector.Host.Proxy.dll_x8665; Installed: Null; Request: Absent; Action: Absent
MSI (s) (F4:0C) [19:46:02:712]: Note: 1: 2205 2: 3: BindImage
MSI (s) (F4:0C) [19:46:02:712]: Note: 1: 2205 2: 3: ProgId
MSI (s) (F4:0C) [19:46:02:712]: Note: 1: 2205 2: 3: PublishComponent
MSI (s) (F4:0C) [19:46:02:712]: Note: 1: 2205 2: 3: SelfReg
MSI (s) (F4:0C) [19:46:02:712]: Note: 1: 2205 2: 3: Extension
MSI (s) (F4:0C) [19:46:02:712]: Note: 1: 2205 2: 3: Font
MSI (s) (F4:0C) [19:46:02:712]: Note: 1: 2205 2: 3: Shortcut
MSI (s) (F4:0C) [19:46:02:712]: Note: 1: 2205 2: 3: Class
MSI (s) (F4:0C) [19:46:02:712]: Note: 1: 2205 2: 3: Icon
MSI (s) (F4:0C) [19:46:02:712]: Note: 1: 2205 2: 3: TypeLib
Action start 19:46:02: InstallValidate.
MSI (s) (F4:0C) [19:46:02:712]: Note: 1: 2205 2: 3: _RemoveFilePath
MSI (s) (F4:0C) [19:46:02:712]: PROPERTY CHANGE: Modifying CostingComplete property. Its current value is ‘0’. Its new value: ‘1’.
MSI (s) (F4:0C) [19:46:02:712]: Note: 1: 2205 2: 3: BindImage
MSI (s) (F4:0C) [19:46:02:712]: Note: 1: 2205 2: 3: ProgId
MSI (s) (F4:0C) [19:46:02:712]: Note: 1: 2205 2: 3: PublishComponent
MSI (s) (F4:0C) [19:46:02:712]: Note: 1: 2205 2: 3: SelfReg
MSI (s) (F4:0C) [19:46:02:712]: Note: 1: 2205 2: 3: Extension
MSI (s) (F4:0C) [19:46:02:712]: Note: 1: 2205 2: 3: Font
MSI (s) (F4:0C) [19:46:02:712]: Note: 1: 2205 2: 3: Shortcut
MSI (s) (F4:0C) [19:46:02:712]: Note: 1: 2205 2: 3: Class
MSI (s) (F4:0C) [19:46:02:712]: Note: 1: 2205 2: 3: Icon
MSI (s) (F4:0C) [19:46:02:712]: Note: 1: 2205 2: 3: TypeLib
MSI (s) (F4:0C) [19:46:02:712]: Note: 1: 2727 2:
MSI (s) (F4:0C) [19:46:02:712]: Note: 1: 2205 2: 3: FilesInUse
MSI (s) (F4:0C) [19:46:03:260]: Note: 1: 2727 2:
MSI (s) (F4:0C) [19:46:03:260]: Doing action: InstallInitialize
MSI (s) (F4:0C) [19:46:03:260]: Note: 1: 2205 2: 3: ActionText
Action ended 19:46:03: InstallValidate. Return value 1.
MSI (s) (F4:0C) [19:46:03:260]: Machine policy value ‘AlwaysInstallElevated’ is 0
MSI (s) (F4:0C) [19:46:03:260]: User policy value ‘AlwaysInstallElevated’ is 0
MSI (s) (F4:0C) [19:46:03:260]: BeginTransaction: Locking Server
MSI (s) (F4:0C) [19:46:03:260]: SRSetRestorePoint skipped for this transaction.
MSI (s) (F4:0C) [19:46:03:260]: Server not locked: locking for product {D48B2CE7-F6B3-4BDD-B9D9-91DEE8668314}
MSI (s) (F4:0C) [19:46:04:056]: Note: 1: 2205 2: 3: ActionText
MSI (s) (F4:0C) [19:46:04:065]: Note: 1: 2205 2: 3: ActionText
MSI (s) (F4:0C) [19:46:04:092]: Note: 1: 2205 2: 3: ActionText
Action start 19:46:03: InstallInitialize.
MSI (s) (F4:0C) [19:46:04:251]: PROPERTY CHANGE: Deleting ProductToBeRegistered property. Its current value is ‘1’.
MSI (s) (F4:0C) [19:46:04:251]: Note: 1: 2205 2: 3: Icon
MSI (s) (F4:0C) [19:46:04:254]: Note: 1: 2228 2: 3: Icon 4: SELECT `Name`, `Data` FROM `Icon`
MSI (s) (F4:0C) [19:46:04:257]: Doing action: RemoveExistingProducts
MSI (s) (F4:0C) [19:46:04:257]: Note: 1: 2205 2: 3: ActionText
Action ended 19:46:04: InstallInitialize. Return value 1.
MSI (s) (F4:0C) [19:46:04:257]: Skipping RemoveExistingProducts action: current configuration is maintenance mode or an uninstall
Action start 19:46:04: RemoveExistingProducts.
MSI (s) (F4:0C) [19:46:04:260]: Doing action: ProcessComponents
MSI (s) (F4:0C) [19:46:04:260]: Note: 1: 2205 2: 3: ActionText
Action ended 19:46:04: RemoveExistingProducts. Return value 0.
Action start 19:46:04: ProcessComponents.
MSI (s) (F4:0C) [19:46:04:274]: Doing action: UnpublishFeatures
MSI (s) (F4:0C) [19:46:04:274]: Note: 1: 2205 2: 3: ActionText
Action ended 19:46:04: ProcessComponents. Return value 1.
Action start 19:46:04: UnpublishFeatures.
MSI (s) (F4:0C) [19:46:04:289]: Doing action: StopServices
MSI (s) (F4:0C) [19:46:04:289]: Note: 1: 2205 2: 3: ActionText
Action ended 19:46:04: UnpublishFeatures. Return value 1.
Action start 19:46:04: StopServices.
MSI (s) (F4:0C) [19:46:04:290]: Doing action: DeleteServices
MSI (s) (F4:0C) [19:46:04:293]: Note: 1: 2205 2: 3: ActionText
Action ended 19:46:04: StopServices. Return value 1.
Action start 19:46:04: DeleteServices.
MSI (s) (F4:0C) [19:46:04:311]: Doing action: RemoveRegistryValues
MSI (s) (F4:0C) [19:46:04:311]: Note: 1: 2205 2: 3: ActionText
Action ended 19:46:04: DeleteServices. Return value 1.
Action start 19:46:04: RemoveRegistryValues.
MSI (s) (F4:0C) [19:46:04:335]: Doing action: RemoveFiles
MSI (s) (F4:0C) [19:46:04:335]: Note: 1: 2205 2: 3: ActionText
Action ended 19:46:04: RemoveRegistryValues. Return value 1.
MSI (s) (F4:0C) [19:46:04:337]: Note: 1: 2205 2: 3: RemoveFile
Action start 19:46:04: RemoveFiles.
MSI (s) (F4:0C) [19:46:04:346]: Note: 1: 2205 2: 3: RemoveFile
MSI (s) (F4:0C) [19:46:04:346]: Doing action: InstallFiles
MSI (s) (F4:0C) [19:46:04:346]: Note: 1: 2205 2: 3: ActionText
Action ended 19:46:04: RemoveFiles. Return value 0.
MSI (s) (F4:0C) [19:46:04:358]: Note: 1: 2205 2: 3: Patch
MSI (s) (F4:0C) [19:46:04:358]: Note: 1: 2228 2: 3: Patch 4: SELECT `Patch`.`File_`, `Patch`.`Header`, `Patch`.`Attributes`, `Patch`.`Sequence`, `Patch`.`StreamRef_` FROM `Patch` WHERE `Patch`.`File_` = ? AND `Patch`.`#_MsiActive`=? ORDER BY `Patch`.`Sequence`
MSI (s) (F4:0C) [19:46:04:358]: Note: 1: 2205 2: 3: Error
MSI (s) (F4:0C) [19:46:04:358]: Note: 1: 2228 2: 3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1302
MSI (s) (F4:0C) [19:46:04:358]: Note: 1: 2205 2: 3: MsiSFCBypass
MSI (s) (F4:0C) [19:46:04:358]: Note: 1: 2228 2: 3: MsiSFCBypass 4: SELECT `File_` FROM `MsiSFCBypass` WHERE `File_` = ?
MSI (s) (F4:0C) [19:46:04:358]: Note: 1: 2205 2: 3: MsiPatchHeaders
MSI (s) (F4:0C) [19:46:04:358]: Note: 1: 2228 2: 3: MsiPatchHeaders 4: SELECT `Header` FROM `MsiPatchHeaders` WHERE `StreamRef` = ?
Action start 19:46:04: InstallFiles.
MSI (s) (F4:0C) [19:46:04:364]: Doing action: WriteRegistryValues
MSI (s) (F4:0C) [19:46:04:364]: Note: 1: 2205 2: 3: ActionText
Action ended 19:46:04: InstallFiles. Return value 1.
Action start 19:46:04: WriteRegistryValues.
MSI (s) (F4:0C) [19:46:04:364]: Doing action: InstallServices
MSI (s) (F4:0C) [19:46:04:364]: Note: 1: 2205 2: 3: ActionText
Action ended 19:46:04: WriteRegistryValues. Return value 1.
Action start 19:46:04: InstallServices.
MSI (s) (F4:0C) [19:46:04:379]: Doing action: MsiConfigureServices
MSI (s) (F4:0C) [19:46:04:379]: Note: 1: 2205 2: 3: ActionText
Action ended 19:46:04: InstallServices. Return value 1.
Action start 19:46:04: MsiConfigureServices.
MSI (s) (F4:0C) [19:46:04:382]: Note: 1: 2205 2: 3: MsiServiceConfigFailureActions
MSI (s) (F4:0C) [19:46:04:382]: Note: 1: 2228 2: 3: MsiServiceConfigFailureActions 4: SELECT `Name`, `Event`, `ResetPeriod`, `RebootMessage`,`Command`, `Actions`, `DelayActions`, `Action` FROM `MsiServiceConfigFailureActions`, `Component` WHERE `Component_` = `Component` AND (`Action` = 0 OR `Action` = 1 OR `Action` = 3)
MSI (s) (F4:0C) [19:46:04:382]: Doing action: StartServices
MSI (s) (F4:0C) [19:46:04:382]: Note: 1: 2205 2: 3: ActionText
Action ended 19:46:04: MsiConfigureServices. Return value 1.
Action start 19:46:04: StartServices.
MSI (s) (F4:0C) [19:46:04:398]: Doing action: RegisterUser
MSI (s) (F4:0C) [19:46:04:400]: Note: 1: 2205 2: 3: ActionText
Action ended 19:46:04: StartServices. Return value 1.
Action start 19:46:04: RegisterUser.
MSI (s) (F4:0C) [19:46:04:400]: Doing action: RegisterProduct
MSI (s) (F4:0C) [19:46:04:400]: Note: 1: 2205 2: 3: ActionText
Action ended 19:46:04: RegisterUser. Return value 0.
Action start 19:46:04: RegisterProduct.
MSI (s) (F4:0C) [19:46:04:418]: Doing action: PublishFeatures
MSI (s) (F4:0C) [19:46:04:418]: Note: 1: 2205 2: 3: ActionText
Action ended 19:46:04: RegisterProduct. Return value 1.
Action start 19:46:04: PublishFeatures.
MSI (s) (F4:0C) [19:46:04:419]: Doing action: PublishProduct
MSI (s) (F4:0C) [19:46:04:419]: Note: 1: 2205 2: 3: ActionText
Action ended 19:46:04: PublishFeatures. Return value 1.
Action start 19:46:04: PublishProduct.
MSI (s) (F4:0C) [19:46:04:419]: Doing action: InstallFinalize
MSI (s) (F4:0C) [19:46:04:427]: Note: 1: 2205 2: 3: ActionText
Action ended 19:46:04: PublishProduct. Return value 1.
MSI (s) (F4:0C) [19:46:04:440]: Running Script: C:\Windows\Installer\MSI9850.tmp
MSI (s) (F4:0C) [19:46:04:440]: PROPERTY CHANGE: Adding UpdateStarted property. Its value is ‘1’.
MSI (s) (F4:0C) [19:46:04:557]: Machine policy value ‘DisableRollback’ is 0
MSI (s) (F4:0C) [19:46:04:658]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (F4:0C) [19:46:04:794]: Executing op: Header(Signature=1397708873,Version=500,Timestamp=1260821955,LangId=1033,Platform=0,ScriptType=1,ScriptMajorVersion=21,ScriptMinorVersion=4,ScriptAttributes=1)
Action start 19:46:04: InstallFinalize.
MSI (s) (F4:0C) [19:46:04:917]: Executing op: ProductInfo(ProductKey={D48B2CE7-F6B3-4BDD-B9D9-91DEE8668314},ProductName=DiagnosticsHub_CollectionService,PackageName=Microsoft.DiagnosticsHub.Collection.Service.Msi.msi,Language=1033,Version=251684448,Assignment=1,ObsoleteArg=0,,,PackageCode={EC392FC9-CE28-4B6E-8632-F511B57B5626},,,InstanceType=0,LUASetting=0,RemoteURTInstalls=0,ProductDeploymentFlags=3)
MSI (s) (F4:0C) [19:46:04:917]: Executing op: DialogInfo(Type=0,Argument=1033)
MSI (s) (F4:0C) [19:46:04:920]: Executing op: DialogInfo(Type=1,Argument=DiagnosticsHub_CollectionService)
MSI (s) (F4:0C) [19:46:04:923]: Executing op: RollbackInfo(,RollbackAction=Rollback,RollbackDescription=Rolling back action:,RollbackTemplate=[1],CleanupAction=RollbackCleanup,CleanupDescription=Removing backup files,CleanupTemplate=File: [1])
MSI (s) (F4:0C) [19:46:04:923]: Executing op: SetBaseline(Baseline=0,)
MSI (s) (F4:0C) [19:46:04:923]: Executing op: SetBaseline(Baseline=1,)
MSI (s) (F4:0C) [19:46:04:923]: Executing op: ActionStart(Name=InstallInitialize,,)
MSI (s) (F4:0C) [19:46:04:925]: Executing op: ProductUnregister(UpgradeCode={D6365ABB-A695-3299-88A9-A13B6422DCCB})
MSI (s) (F4:0C) [19:46:04:934]: Note: 1: 1402 2: UNKNOWN\Products\7EC2B84D3B6FDDB49B9D19ED8E663841\Transforms 3: 2
MSI (s) (F4:0C) [19:46:04:934]: Note: 1: 1402 2: UNKNOWN\Products\7EC2B84D3B6FDDB49B9D19ED8E663841\Transforms 3: 2
MSI (s) (F4:0C) [19:46:04:934]: Scheduling file ‘C:\Windows\Installer\3dac471.msi’ for deletion during post-install cleanup (not post-reboot).
MSI (s) (F4:0C) [19:46:04:962]: Note: 1: 1402 2: UNKNOWN\Products\7EC2B84D3B6FDDB49B9D19ED8E663841\Usage 3: 2
MSI (s) (F4:0C) [19:46:04:965]: Executing op: ProductCPDisplayInfoUnregister()
MSI (s) (F4:0C) [19:46:04:965]: Executing op: ProductUnpublish(PackageKey={EC392FC9-CE28-4B6E-8632-F511B57B5626})
MSI (s) (F4:0C) [19:46:04:967]: Executing op: UpgradeCodeUnpublish(UpgradeCode={D6365ABB-A695-3299-88A9-A13B6422DCCB})
MSI (s) (F4:0C) [19:46:04:967]: Executing op: ProductUnpublishClient(,,)
MSI (s) (F4:0C) [19:46:04:967]: Note: 1: 1402 2: UNKNOWN\Installer\Products\7EC2B84D3B6FDDB49B9D19ED8E663841 3: 2
MSI (s) (F4:0C) [19:46:04:967]: Executing op: SourceListUnpublish(,)
MSI (s) (F4:0C) [19:46:04:967]: Note: 1: 1402 2: UNKNOWN\Installer\Products\7EC2B84D3B6FDDB49B9D19ED8E663841\SourceList 3: 2
MSI (s) (F4:0C) [19:46:04:967]: Executing op: ActionStart(Name=ProcessComponents,Description=Updating component registration,)
MSI (s) (F4:0C) [19:46:04:967]: Executing op: ProgressTotal(Total=4,Type=1,ByteEquivalent=24000)
MSI (s) (F4:0C) [19:46:04:973]: Executing op: UnregisterSharedComponentProvider(Component={84F63CE5-1CA1-5702-BA62-BC24FAA594F2},ProductCode={D48B2CE7-F6B3-4BDD-B9D9-91DEE8668314})
MSI (s) (F4:0C) [19:46:04:973]: Executing op: ComponentUnregister(ComponentId={84F63CE5-1CA1-5702-BA62-BC24FAA594F2},,BinaryType=0,)
MSI (s) (F4:0C) [19:46:04:988]: Executing op: UnregisterSharedComponentProvider(Component={A2713C01-69A0-5612-A067-7B0EF5DC9B4B},ProductCode={D48B2CE7-F6B3-4BDD-B9D9-91DEE8668314})
MSI (s) (F4:0C) [19:46:04:991]: Executing op: ComponentUnregister(ComponentId={A2713C01-69A0-5612-A067-7B0EF5DC9B4B},,BinaryType=0,)
MSI (s) (F4:0C) [19:46:05:003]: Executing op: UnregisterSharedComponentProvider(Component={C24A00E0-84FA-5FE5-9396-564E5E3C669E},ProductCode={D48B2CE7-F6B3-4BDD-B9D9-91DEE8668314})
MSI (s) (F4:0C) [19:46:05:003]: Executing op: ComponentUnregister(ComponentId={C24A00E0-84FA-5FE5-9396-564E5E3C669E},,BinaryType=0,)
MSI (s) (F4:0C) [19:46:05:006]: Executing op: UnregisterSharedComponentProvider(Component={34962BCA-8371-5AD3-8952-49E5F731026D},ProductCode={D48B2CE7-F6B3-4BDD-B9D9-91DEE8668314})
MSI (s) (F4:0C) [19:46:05:006]: Executing op: ComponentUnregister(ComponentId={34962BCA-8371-5AD3-8952-49E5F731026D},,BinaryType=0,)
MSI (s) (F4:0C) [19:46:05:009]: Executing op: ActionStart(Name=UnpublishFeatures,Description=Unpublishing Product Features,Template=Feature: [1])
MSI (s) (F4:0C) [19:46:05:015]: Executing op: FeatureUnpublish(Feature=DiagnosticsHub_Collection_Service,,Absent=2,Component=qVGgR?H{zC}[Ym.P!&{vz@h5]E.IaCeq^`’3hVA@loiMgB}knFLc,3As+AvZ=b[u4K-?4E.GqcrlO~%K)
MSI (s) (F4:0C) [19:46:05:018]: Note: 1: 1402 2: UNKNOWN\Installer\Features\7EC2B84D3B6FDDB49B9D19ED8E663841 3: 2
MSI (s) (F4:0C) [19:46:05:028]: Executing op: ActionStart(Name=StopServices,Description=Stopping services,Template=Service: [1])
MSI (s) (F4:0C) [19:46:05:031]: Executing op: ProgressTotal(Total=1,Type=1,ByteEquivalent=1300000)
MSI (s) (F4:0C) [19:46:05:031]: Executing op: ServiceControl(,Name=VSStandardCollectorService150,Action=2,Wait=1,)
MSI (s) (F4:0C) [19:46:05:031]: Executing op: ActionStart(Name=DeleteServices,Description=Deleting services,Template=Service: [1])
MSI (s) (F4:0C) [19:46:05:031]: Executing op: ProgressTotal(Total=1,Type=1,ByteEquivalent=1300000)
MSI (s) (F4:0C) [19:46:05:031]: Executing op: ServiceControl(,Name=VSStandardCollectorService150,Action=8,Wait=1,)
MSI (s) (F4:0C) [19:46:05:036]: Executing op: ActionStart(Name=RemoveRegistryValues,Description=Removing system registry values,Template=Key: [1], Name: [2])
MSI (s) (F4:0C) [19:46:05:168]: Executing op: ProgressTotal(Total=12,Type=1,ByteEquivalent=13200)
MSI (s) (F4:0C) [19:46:05:168]: Executing op: RegOpenKey(Root=-2147483646,Key=SOFTWARE\Classes\CLSID\{D2020DEA-EB40-45D5-B420-B9FB623C4FD1},,BinaryType=0,,)
MSI (s) (F4:0C) [19:46:05:168]: Executing op: RegRemoveValue(,Value=PSFactoryBuffer,)
MSI (s) (F4:0C) [19:46:05:168]: Executing op: RegOpenKey(Root=-2147483646,Key=SOFTWARE\Classes\CLSID\{D2020DEA-EB40-45D5-B420-B9FB623C4FD1}\InProcServer32,,BinaryType=0,,)
MSI (s) (F4:0C) [19:46:05:168]: Executing op: RegRemoveValue(,Value=[#DiagnosticsHub.StandardCollector.Host.Proxy.dll_x86],)
MSI (s) (F4:0C) [19:46:05:169]: Executing op: RegRemoveValue(Name=ThreadingModel,Value=Both,)
MSI (s) (F4:0C) [19:46:05:169]: Executing op: RegOpenKey(Root=-2147483646,Key=SOFTWARE\Classes\Interface\{D2020DEA-EB40-45D5-B420-B9FB623C4FD1},,BinaryType=0,,)
MSI (s) (F4:0C) [19:46:05:169]: Executing op: RegRemoveValue(,Value=IStandardCollectorHost,)
MSI (s) (F4:0C) [19:46:05:169]: Executing op: RegOpenKey(Root=-2147483646,Key=SOFTWARE\Classes\Interface\{D2020DEA-EB40-45D5-B420-B9FB623C4FD1}\ProxyStubClsid32,,BinaryType=0,,)
MSI (s) (F4:0C) [19:46:05:172]: Executing op: RegRemoveValue(,Value={D2020DEA-EB40-45D5-B420-B9FB623C4FD1},)
MSI (s) (F4:0C) [19:46:05:174]: Executing op: RegOpenKey(Root=-2147483646,Key=SOFTWARE\Classes\Interface\{D2020DEA-EB40-45D5-B420-B9FB623C4FD1}\NumMethods,,BinaryType=0,,)
MSI (s) (F4:0C) [19:46:05:180]: Executing op: RegRemoveValue(,Value=5,)
MSI (s) (F4:0C) [19:46:05:180]: Executing op: RegOpenKey(Root=-2147483646,Key=SOFTWARE\Classes\AppID\{F2DC0F57-0B99-49E3-BE80-936DBAA54EE0},,BinaryType=0,,)
MSI (s) (F4:0C) [19:46:05:180]: Executing op: RegRemoveValue(Name=LocalService,Value=VSStandardCollectorService150,)
MSI (s) (F4:0C) [19:46:05:180]: Executing op: RegRemoveValue(Name=AccessPermission,Value=#x010004807000000080000000000000001400000002005c0004000000000014000b000000010100000000000512000000000018000b00000001020000000000052000000020020000000014000b00000001010000000000050b000000000014000b0000000101000000000005040000000102000000000005200000002002000001020000000000052000000020020000,)
MSI (s) (F4:0C) [19:46:05:180]: Executing op: RegRemoveValue(Name=AuthenticationLevel,Value=#2,)
MSI (s) (F4:0C) [19:46:05:192]: Executing op: RegRemoveValue(Name=LaunchPermission,Value=#x010004807000000080000000000000001400000002005c0004000000000014000b00000001010000000000050a000000000014000b00000001010000000000050b000000000014000b000000010100000000000512000000000018000b000000010200000000000520000000200200000102000000000005200000002002000001020000000000052000000020020000,)
MSI (s) (F4:0C) [19:46:05:195]: Executing op: RegOpenKey(Root=-2147483646,Key=SOFTWARE\Classes\CLSID\{F2DC0F57-0B99-49E3-BE80-936DBAA54EE0},,BinaryType=0,,)
MSI (s) (F4:0C) [19:46:05:199]: Executing op: RegRemoveValue(Name=AppID,Value={F2DC0F57-0B99-49E3-BE80-936DBAA54EE0},)
MSI (s) (F4:0C) [19:46:05:235]: Executing op: RegRemoveValue(,Value=Visual Studio Standard Collector Host 150,)
MSI (s) (F4:0C) [19:46:05:235]: Executing op: ActionStart(Name=RemoveFiles,Description=Removing files,Template=File: [1], Directory: [9])
MSI (s) (F4:0C) [19:46:05:235]: Executing op: ProgressTotal(Total=2,Type=1,ByteEquivalent=175000)
MSI (s) (F4:0C) [19:46:05:235]: Executing op: SetTargetFolder(Folder=C:\Program Files\Microsoft Visual Studio\Shared\Common\DiagnosticsHub.Collection.Service\x86\)
MSI (s) (F4:0C) [19:46:05:235]: Executing op: FileRemove(,FileName=DiagnosticsHub.StandardCollector.Host.Proxy.dll,,ComponentId={84F63CE5-1CA1-5702-BA62-BC24FAA594F2})
MSI (s) (F4:0C) [19:46:05:235]: Verifying accessibility of file: DiagnosticsHub.StandardCollector.Host.Proxy.dll
MSI (s) (F4:0C) [19:46:05:238]: Note: 1: 2318 2:
MSI (s) (F4:0C) [19:46:05:262]: Note: 1: 2318 2:
MSI (s) (F4:0C) [19:46:05:262]: Executing op: SetTargetFolder(Folder=C:\Program Files\Microsoft Visual Studio\Shared\Common\DiagnosticsHub.Collection.Service\)
MSI (s) (F4:0C) [19:46:05:262]: Executing op: FileRemove(,FileName=StandardCollector.Service.exe,,ComponentId={A2713C01-69A0-5612-A067-7B0EF5DC9B4B})
MSI (s) (F4:0C) [19:46:05:295]: Verifying accessibility of file: StandardCollector.Service.exe
MSI (s) (F4:0C) [19:46:05:295]: Note: 1: 2318 2:
MSI (s) (F4:0C) [19:46:05:300]: Note: 1: 2318 2:
MSI (s) (F4:0C) [19:46:05:304]: Note: 1: 2318 2:
MSI (s) (F4:0C) [19:46:05:307]: Executing op: ActionStart(Name=MsiConfigureServices,,)
MSI (s) (F4:0C) [19:46:05:351]: Executing op: ProgressTotal(Total=2,Type=1,ByteEquivalent=1300000)
MSI (s) (F4:0C) [19:46:05:370]: Executing op: ActionStart(Name=PublishProduct,Description=Publishing product information,)
MSI (s) (F4:0C) [19:46:05:370]: Executing op: CleanupConfigData()
MSI (s) (F4:0C) [19:46:05:370]: Executing op: RegisterPatchOrder(Continue=0,SequenceType=0,Remove=1)
MSI (s) (F4:0C) [19:46:05:372]: Note: 1: 1402 2: UNKNOWN\Installer\Products\7EC2B84D3B6FDDB49B9D19ED8E663841\Patches 3: 2
MSI (s) (F4:0C) [19:46:05:372]: Executing op: RegisterPatchOrder(Continue=0,SequenceType=1,Remove=1)
MSI (s) (F4:0C) [19:46:05:372]: Executing op: CleanupConfigData(RemovingProduct=1)
MSI (s) (F4:0C) [19:46:05:372]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\7EC2B84D3B6FDDB49B9D19ED8E663841\Patches 3: 2
MSI (s) (F4:0C) [19:46:05:372]: Executing op: End(Checksum=0,ProgressTotalHDWord=0,ProgressTotalLDWord=5804400)
MSI (s) (F4:0C) [19:46:05:373]: User policy value ‘DisableRollback’ is 0
MSI (s) (F4:0C) [19:46:05:375]: Machine policy value ‘DisableRollback’ is 0
MSI (s) (F4:0C) [19:46:05:378]: Note: 1: 2318 2:
MSI (s) (F4:0C) [19:46:05:378]: Note: 1: 2318 2:
MSI (s) (F4:0C) [19:46:05:381]: No System Restore sequence number for this installation.
MSI (s) (F4:0C) [19:46:05:381]: Unlocking Server
MSI (s) (F4:0C) [19:46:05:382]: PROPERTY CHANGE: Deleting UpdateStarted property. Its current value is ‘1’.
Action ended 19:46:05: InstallFinalize. Return value 1.
Action ended 19:46:05: INSTALL. Return value 1.
MSI (s) (F4:0C) [19:46:05:405]: Note: 1: 1724
MSI (s) (F4:0C) [19:46:05:405]: Note: 1: 2205 2: 3: Error
MSI (s) (F4:0C) [19:46:05:405]: Note: 1: 2228 2: 3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1724
MSI (s) (F4:0C) [19:46:05:405]: Note: 1: 2205 2: 3: Error
MSI (s) (F4:0C) [19:46:05:405]: Note: 1: 2228 2: 3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1709
MSI (s) (F4:0C) [19:46:05:405]: Product: DiagnosticsHub_CollectionService — Removal completed successfully.
MSI (s) (F4:0C) [19:46:05:466]: Windows Installer removed the product. Product Name: DiagnosticsHub_CollectionService. Product Version: 15.0.26208. Product Language: 1033. Manufacturer: Microsoft Corporation. Removal success or error status: 0.
MSI (s) (F4:0C) [19:46:05:466]: Deferring clean up of packages/files, if any exist
MSI (s) (F4:0C) [19:46:05:466]: MainEngineThread is returning 0
MSI (s) (F4:3C) [19:46:05:561]: RESTART MANAGER: Session closed.
MSI (s) (F4:3C) [19:46:05:561]: No System Restore sequence number for this installation.
=== Logging stopped: 9/6/2017 19:46:05 ===
MSI (s) (F4:3C) [19:46:05:561]: User policy value ‘DisableRollback’ is 0
MSI (s) (F4:3C) [19:46:05:561]: Machine policy value ‘DisableRollback’ is 0
MSI (s) (F4:3C) [19:46:05:561]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (F4:3C) [19:46:05:561]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (F4:3C) [19:46:05:579]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (F4:3C) [19:46:05:579]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (s) (F4:3C) [19:46:05:579]: Post-install cleanup: removing installer file ‘C:\Windows\Installer\3dac471.msi’
MSI (s) (F4:3C) [19:46:05:580]: Restoring environment variables
MSI (c) (2C:04) [19:46:05:609]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (2C:04) [19:46:05:631]: MainEngineThread is returning 0
=== Verbose logging stopped: 9/6/2017 19:46:05 ===
FILE 2
ignTools.XamlLanguageService.resources.dll
[0d2c:0015][2017-09-06T23:36:57] C:\Program Files\Microsoft Visual Studio\2017\Community\Common7\IDE\CommonExtensions\Microsoft\XamlLanguageService\en\Microsoft.VisualStudio.DesignTools.XamlLanguageService.resources.dll file deleted.
[0d2c:0015][2017-09-06T23:36:57] Processing file /Contents/Common7/IDE/PrivateAssemblies/en/Microsoft.VisualStudio.DesignTools.Designer.resources.dll
[0d2c:0015][2017-09-06T23:36:57] C:\Program Files\Microsoft Visual Studio\2017\Community\Common7\IDE\PrivateAssemblies\en\Microsoft.VisualStudio.DesignTools.Designer.resources.dll file deleted.
[0d2c:0015][2017-09-06T23:36:57] Processing file /Contents/Common7/IDE/PrivateAssemblies/en/Microsoft.VisualStudio.DesignTools.DesignerContract.resources.dll
[0d2c:0015][2017-09-06T23:36:57] C:\Program Files\Microsoft Visual Studio\2017\Community\Common7\IDE\PrivateAssemblies\en\Microsoft.VisualStudio.DesignTools.DesignerContract.resources.dll file deleted.
[0d2c:0015][2017-09-06T23:36:57] Processing file /Contents/Common7/IDE/PrivateAssemblies/en/Microsoft.VisualStudio.DesignTools.DesignerHost.resources.dll
[0d2c:0015][2017-09-06T23:36:57] C:\Program Files\Microsoft Visual Studio\2017\Community\Common7\IDE\PrivateAssemblies\en\Microsoft.VisualStudio.DesignTools.DesignerHost.resources.dll file deleted.
[0d2c:0015][2017-09-06T23:36:57] Processing file /Contents/Common7/IDE/PrivateAssemblies/en/Microsoft.VisualStudio.DesignTools.WpfDesigner.resources.dll
[0d2c:0015][2017-09-06T23:36:57] C:\Program Files\Microsoft Visual Studio\2017\Community\Common7\IDE\PrivateAssemblies\en\Microsoft.VisualStudio.DesignTools.WpfDesigner.resources.dll file deleted.
[0d2c:0015][2017-09-06T23:36:57] Processing file /Contents/Common7/IDE/PrivateAssemblies/en/Microsoft.VisualStudio.DesignTools.XamlDesigner.resources.dll
[0d2c:0015][2017-09-06T23:36:57] C:\Program Files\Microsoft Visual Studio\2017\Community\Common7\IDE\PrivateAssemblies\en\Microsoft.VisualStudio.DesignTools.XamlDesigner.resources.dll file deleted.
[0d2c:0015][2017-09-06T23:36:57] Processing file /Contents/Common7/IDE/PrivateAssemblies/en/Microsoft.VisualStudio.DesignTools.XamlDesignerHost.resources.dll
[0d2c:0015][2017-09-06T23:36:57] C:\Program Files\Microsoft Visual Studio\2017\Community\Common7\IDE\PrivateAssemblies\en\Microsoft.VisualStudio.DesignTools.XamlDesignerHost.resources.dll file deleted.
[0d2c:0015][2017-09-06T23:36:57] Processing file /Contents/Common7/IDE/PublicAssemblies/en/Microsoft.Windows.Design.Extensibility.resources.dll
[0d2c:0015][2017-09-06T23:36:57] C:\Program Files\Microsoft Visual Studio\2017\Community\Common7\IDE\PublicAssemblies\en\Microsoft.Windows.Design.Extensibility.resources.dll file deleted.
[0d2c:0015][2017-09-06T23:36:57] Processing file /Contents/Common7/IDE/PublicAssemblies/en/Microsoft.Windows.Design.Interaction.resources.dll
[0d2c:0015][2017-09-06T23:36:57] C:\Program Files\Microsoft Visual Studio\2017\Community\Common7\IDE\PublicAssemblies\en\Microsoft.Windows.Design.Interaction.resources.dll file deleted.
[0d2c:0015][2017-09-06T23:36:57] Processing file /Contents/DesignTools/AppThemes/en/Simple Styles.xaml
[0d2c:0015][2017-09-06T23:36:57] C:\Program Files\Microsoft Visual Studio\2017\Community\DesignTools\AppThemes\en\Simple Styles.xaml file deleted.
[0d2c:0015][2017-09-06T23:36:57] Processing file
[0d2c:0015][2017-09-06T23:34:12] Using cached package manifest as the embedded manifest
[0d2c:0015][2017-09-06T23:34:13] Processing file /extension.vsixmanifest
[0d2c:0015][2017-09-06T23:34:13] C:\Program Files\Microsoft Visual Studio\2017\Community\Common7\IDE\Extensions\ngono243.wly\extension.vsixmanifest file deleted.
[0d2c:0015][2017-09-06T23:34:13] Processing file /Microsoft.VisualStudio.Azure.ResourceManagement.dll
[0d2c:0015][2017-09-06T23:34:13] C:\Program Files\Microsoft Visual Studio\2017\Community\Common7\IDE\Extensions\ngono243.wly\Microsoft.VisualStudio.Azure.ResourceManagement.dll file deleted.
[0d2c:0015][2017-09-06T23:34:13] Processing file /Microsoft.VisualStudio.Azure.VSIntegration.dll
[0d2c:0015][2017-09-06T23:34:13] C:\Program Files\Microsoft Visual Studio\2017\Community\Common7\IDE\Extensions\ngono243.wly\Microsoft.VisualStudio.Azure.VSIntegration.dll file deleted.
[0d2c:0015][2017-09-06T23:34:13] Processing file /Microsoft.VisualStudio.ConnectedServices.Azure.Storage.dll
[0d2c:0015][2017-09-06T23:34:13] C:\Program Files\Microsoft Visual Studio\2017\Community\Common7\IDE\Extensions\ngono243.wly\Microsoft.VisualStudio.ConnectedServices.Azure.Storage.dll file deleted.
[0d2c:0015][2017-09-06T23:34:13] Processing file /AzureStorageProviderIcon.png
[0d2c:0015][2017-09-06T23:34:13] C:\Program Files\Microsoft Visual Studio\2017\Community\Common7\IDE\Extensions\ngono243.wly\AzureStorageProviderIcon.png file deleted.
[0d2c:0015][2017-09-06T23:34:13] Processing file /zh-Hans/Microsoft.VisualStudio.Azure.ResourceManagement.resources.dll
[0d2c:0015][2017-09-06T23:34:13] C:\Program Files\Microsoft Visual Studio\2017\Community\Common7\IDE\Extensions\ngono243.wly\zh-Hans\Microsoft.VisualStudio.Azure.ResourceManagement.resources.dll file deleted.
[0d2c:0015][2017-09-06T23:34:13] Processing file /zh-Hant/Microsoft.VisualStudio.Azure.ResourceManagement.resources.dll
[0d2c:0015][2017-09-06T23:34:13] C:\Program Files\Microsoft Visual Studio\2017\Community\Common7\IDE\Extensions\ngono243.wly\zh-Hant\Microsoft.VisualStudio.Azure.ResourceManagement.resources.dll file deleted.
[0d2c:0015][2017-09-06T23:34:13] Processing file /de/Microsoft.VisualStudio.Azure.ResourceManagement.resources.dll
[0d2c:0015][2017-09-06T23:34:13] C:\Program Files\Microsoft Visual Studio\2017\Community\Common7\IDE\Extensions\ngono243.wly\de\Microsoft.VisualStudio.Azure.ResourceManagement.resources.dll file deleted.
[0d2c:0015][2017-09-06T23:34:13] Processing file /es/Microsoft.VisualStudio.Azure.ResourceManagement.resources.dll
[0d2c:0015][2017-09-06T23:34:13] C:\Program Files\Microsoft Visual Studio\2017\Community\Common7\IDE\Extensions\ngono243.wly\es\Microsoft.VisualStudio.Azure.ResourceManagement.resources.dll file deleted.
[0d2c:0015][2017-09-06T23:34:13] Processing file /fr/Microsoft.VisualStudio.Azure.ResourceManagement.resources.dll
[0d2c:0015][2017-09-06T23:34:13] C:\Program Files\Microsoft Visual Studio\2017\Community\Common7\IDE\Extensions\ngono243.wly\fr\Microsoft.VisualStudio.Azure.ResourceManagement.resources.dll file deleted.
[0d2c:0015][2017-09-06T23:34:13] Processing file /it/Microsoft.VisualStudio.Azure.ResourceManagement.resources.dll
[0d2c:0015][2017-09-06T23:34:13] C:\Program Files\Microsoft Visual Studio\2017\Community\Common7\IDE\Extensions\ngono243.wly\it\Microsoft.VisualStudio.Azure.ResourceManagement.resources.dll file deleted.
[0d2c:0015][2017-09-06T23:34:13] Processing file /ja/Microsoft.VisualStudio.Azure.ResourceManagement.resources.dll
[0d2c:0015][2017-09-06T23:34:13] C:\Program Files\Microsoft Visual Studio\2017\Community\Common7\IDE\Extensions\ngono243.wly\ja\Microsoft.VisualStudio.Azure.ResourceManagement.resources.dll file deleted.
[0d2c:0015][2017-09-06T23:34:13] Processing file /ko/Microsoft.VisualStudio.Azure.ResourceManagement.resources.dll
[0d2c:0015][2017-09-06T23:34:14] C:\Program Files\Microsoft Visual Studio\2017\Community\Common7\IDE\Extensions\ngono243.wly\ko\Microsoft.VisualStudio.Azure.ResourceManagement.resources.dll file deleted.
[0d2c:0015][2017-09-06T23:34:14] Processing file /ru/Microsoft.VisualStudio.Azure.ResourceManagement.resources.dll
[0d2c:0015][2017-09-06T23:34:14] C:\Program Files\Microsoft Visual Studio\2017\Community\Common7\IDE\Extensions\ngono243.wly\ru\Microsoft.VisualStudio.Azure.ResourceManagement.resources.dll file deleted.
[0d2c:0015][2017-09-06T23:34:14] Processing file /cs/Microsoft.VisualStudio.Azure.ResourceManagement.resources.dll
[0d2c:0015][2017-09-06T23:34:15] C:\Program Files\Microsoft Visual Studio\2017\Community\Common7\IDE\Extensions\ngono243.wly\cs\Microsoft.VisualStudio.Azure.ResourceManagement.resources.dll file deleted.
[0d2c:0015][2017-09-06T23:34:15] Processing file /pt-BR/Microsoft.VisualStudio.Azure.ResourceManagement.resources.dll
[0d2c:0015][2017-09-06T23:34:15] C:\Program Files\Microsoft Visual Studio\2017\Community\Common7\IDE\Extensions\ngono243.wly\pt-BR\Microsoft.VisualStudio.Azure.ResourceManagement.resources.dll file deleted.
[0d2c:0015][2017-09-06T23:34:15] Processing file /pl/Microsoft.VisualStudio.Azure.ResourceManagement.resources.dll
[0d2c:0015][2017-09-06T23:34:15] C:\Program Files\Microsoft Visual Studio\2017\Community\Common7\IDE\Extensions\ngono243.wly\pl\Microsoft.VisualStudio.Azure.ResourceManagement.resources.dll file deleted.
[0d2c:0015][2017-09-06T23:34:15] Processing file /tr/Microsoft.VisualStudio.Azure.ResourceManagement.resources.dll
[0d2c:0015][2017-09-06T23:34:15] C:\Program Files\Microsoft Visual Studio\2017\Community\Common7\IDE\Extensions\ngono243.wly\tr\Microsoft.VisualStudio.Azure.ResourceManagement.resources.dll file deleted.
[0d2c:0015][2017-09-06T23:34:15] Processing file /zh-Hans/Microsoft.VisualStudio.Azure.VSIntegration.resources.dll
[0d2c:0015][2017-09-06T23:34:15] C:\Program Files\Microsoft Visual Studio\2017\Community\Common7\IDE\Extensions\ngono243.wly\zh-Hans\Microsoft.VisualStudio.Azure.VSIntegration.resources.dll file deleted.
[0d2c:0015][2017-09-06T23:34:15] Processing file /zh-Hant/Microsoft.VisualStudio.Azure.VSIntegration.resources.dll
[0d2c:0015][2017-09-06T23:34:15] C:\Program Files\Microsoft Visual Studio\2017\Community\Common7\IDE\Extensions\ngono243.wly\zh-Hant\Microsoft.VisualStudio.Azure.VSIntegration.resources.dll file deleted.
[0d2c:0015][2017-09-06T23:34:15] Processing file /de/Microsoft.VisualStudio.Azure.VSIntegration.resources.dll
[0d2c:0015][2017-09-06T23:34:15] C:\Program Files\Microsoft Visual Studio\2017\Community\Common7\IDE\Extensions\ngono243.wly\de\Microsoft.VisualStudio.Azure.VSIntegration.resources.dll file deleted.
[0d2c:0015][2017-09-06T23:34:15] Processing file /es/Microsoft.VisualStudio.Azure.VSIntegration.resources.dll
[0d2c:0015][2017-09-06T23:34:15] C:\Program Files\Microsoft Visual Studio\2017\Community\Common7\IDE\Extensions\ngono243.wly\es\Microsoft.VisualStudio.Azure.VSIntegration.resources.dll file deleted.
[0d2c:0015][2017-09-06T23:34:15] Processing file /fr/Microsoft.VisualStudio.Azure.VSIntegration.resources.dll
[0d2c:0015][2017-09-06T23:34:15] C:\Program Files\Microsoft Visual Studio\2017\Community\Common7\IDE\Extensions\ngono243.wly\fr\Microsoft.VisualStudio.Azure.VSIntegration.resources.dll file deleted.
[0d2c:0015][2017-09-06T23:34:15] Processing file /it/Microsoft.VisualStudio.Azure.VSIntegration.resources.dll
[0d2c:0015][2017-09-06T23:34:15] C:\Program Files\Microsoft Visual Studio\2017\Community\Common7\IDE\Extensions\ngono243.wly\it\Microsoft.VisualStudio.Azure.VSIntegration.resources.dll file deleted.
[0d2c:0015][2017-09-06T23:34:15] Processing file /ja/Microsoft.VisualStudio.Azure.VSIntegration.resources.dll
[0d2c:0015][2017-09-06T23:34:15] C:\Program Files\Microsoft Visual Studio\2017\Community\Common7\IDE\Extensions\ngono243.wly\ja\Microsoft.VisualStudio.Azure.VSIntegration.resources.dll file deleted.
[0d2c:0015][2017-09-06T23:34:15] Processing file /ko/Microsoft.VisualStudio.Azure.VSIntegration.resources.dll
[0d2c:0015][2017-09-06T23:34:15] C:\Program Files\Microsoft Visual Studio\2017\Community\Common7\IDE\Extensions\ngono243.wly\ko\Microsoft.VisualStudio.Azure.VSIntegration.resources.dll file deleted.
[0d2c:0015][2017-09-06T23:34:15] Processing file /ru/Microsoft.VisualStudio.Azure.VSIntegration.resources.dll
[0d2c:0015][2017-09-06T23:34:15] C:\Program Files\Microsoft Visual Studio\2017\Community\Common7\IDE\Extensions\ngono243.wly\ru\Microsoft.VisualStudio.Azure.VSIntegration.resources.dll file deleted.
[0d2c:0015][2017-09-06T23:34:15] Processing file /cs/Microsoft.VisualStudio.Azure.VSIntegration.resources.dll
[0d2c:0015][2017-09-06T23:34:15] C:\Program Files\Microsoft Visual Studio\2017\Community\Common7\IDE\Extensions\ngono243.wly\cs\Microsoft.VisualStudio.Azure.VSIntegration.resources.dll file deleted.
[0d2c:0015][2017-09-06T23:34:15] Processing file /pt-BR/Microsoft.VisualStudio.Azure.VSIntegration.resources.dll
[0d2c:0015][2017-09-06T23:34:15] C:\Program Files\Microsoft Visual Studio\2017\Community\Common7\IDE\Extensions\ngono243.wly\pt-BR\Microsoft.VisualStudio.Azure.VSIntegration.resources.dll file deleted.
[0d2c:0015][2017-09-06T23:34:15] Processing file /pl/Microsoft.VisualStudio.Azure.VSIntegration.resources.dll
[0d2c:0015][2017-09-06T23:34:15] C:\Program Files\Microsoft Visual Studio\2017\Community\Common7\IDE\Extensions\ngono243.wly\pl\Microsoft.VisualStudio.Azure.VSIntegration.resources.dll file deleted.
[0d2c:0015][2017-09-06T23:34:15] Processing file /tr/Microsoft.VisualStudio.Azure.VSIntegration.resources.dll
[0d2c:0015][2017-09-06T23:34:15] C:\Program Files\Microsoft Visual Studio\2017\Community\Common7\IDE\Extensions\ngono243.wly\tr\Microsoft.VisualStudio.Azure.VSIntegration.resources.dll file deleted.
[0d2c:0015][2017-09-06T23:34:15] Processing file /zh-Hans/Microsoft.VisualStudio.ConnectedServices.Azure.Storage.resources.dll
[0d2c:0015][2017-09-06T23:34:15] C:\Program Files\Microsoft Visual Studio\2017\Community\Common7\IDE\Extensions\ngono243.wly\zh-Hans\Microsoft.VisualStudio.ConnectedServices.Azure.Storage.resources.dll file deleted.
[0d2c:0015][2017-09-06T23:34:15] Processing file /zh-Hant/Microsoft.VisualStudio.ConnectedServices.Azure.Storage.resources.dll
[0d2c:0015][2017-09-06T23:34:15] C:\Program Files\Microsoft Visual Studio\2017\Community\Common7\IDE\Extensions\ngono243.wly\zh-Hant\Microsoft.VisualStudio.ConnectedServices.Azure.Storage.resources.dll file deleted.
[0d2c:0015][2017-09-06T23:34:15] Processing file /de/Microsoft.VisualStudio.ConnectedServices.Azure.Storage.resources.dll
[0d2c:0015][2017-09-06T23:34:15] C:\Program Files\Microsoft Visual Studio\2017\Community\Common7\IDE\Extensions\ngono243.wly\de\Microsoft.VisualStudio.ConnectedServices.Azure.Storage.resources.dll file deleted.
[0d2c:0015][2017-09-06T23:34:15] Processing file /es/Microsoft.VisualStudio.ConnectedServices.Azure.Storage.resources.dll
[0d2c:0015][2017-09-06T23:34:15] C:\Program Files\Microsoft Visual Studio\2017\Community\Common7\IDE\Extensions\ngono243.wly\es\Microsoft.VisualStudio.ConnectedServices.Azure.Storage.resources.dll file deleted.
[0d2c:0015][2017-09-06T23:34:15] Processing file /fr/Microsoft.VisualStudio.ConnectedServices.Azure.Storage.resources.dll
[0d2c:0015][2017-09-06T23:34:15] C:\Program Files\Microsoft Visual Studio\2017\Community\Common7\IDE\Extensions\ngono243.wly\fr\Microsoft.VisualStudio.ConnectedServices.Azure.Storage.resources.dll file deleted.
[0d2c:0015][2017-09-06T23:34:15] Processing file /it/Microsoft.VisualStudio.ConnectedServices.Azure.Storage.resources.dll
[0d2c:0015][2017-09-06T23:34:16] C:\Program Files\Microsoft Visual Studio\2017\Community\Common7\IDE\Extensions\ngono243.wly\it\Microsoft.VisualStudio.ConnectedServices.Azure.Storage.resources.dll file deleted.
[0d2c:0015][2017-09-06T23:34:16] Processing file /ja/Microsoft.VisualStudio.ConnectedServices.Azure.Storage.resources.dll
[0d2c:0015][2017-09-06T23:34:16] C:\Program Files\Microsoft Visual Studio\2017\Community\Common7\IDE\Extensions\ngono243.wly\ja\Microsoft.VisualStudio.ConnectedServices.Azure.Storage.resources.dll file deleted.
[0d2c:0015][2017-09-06T23:34:16] Processing file /ko/Microsoft.VisualStudio.ConnectedServices.Azure.Storage.resources.dll
[0d2c:0015][2017-09-06T23:34:16] C:\Program Files\Microsoft Visual Studio\2017\Community\Common7\IDE\Extensions\ngono243.wly\ko\Microsoft.VisualStudio.ConnectedServices.Azure.Storage.resources.dll file deleted.
[0d2c:0015][2017-09-06T23:34:16] Processing file /ru/Microsoft.VisualStudio.ConnectedServices.Azure.Storage.resources.dll
[0d2c:0015][2017-09-06T23:34:16] C:\Program Files\Microsoft Visual Studio\2017\Community\Common7\IDE\Extensions\ngono243.wly\ru\Microsoft.VisualStudio.ConnectedServices.Azure.Storage.resources.dll file deleted.
[0d2c:0015][2017-09-06T23:34:16] Processing file /cs/Microsoft.VisualStudio.ConnectedServices.Azure.Storage.resources.dll
[0d2c:0015][2017-09-06T23:34:16] C:\Program Files\Microsoft Visual Studio\2017\Community\Common7\IDE\Extensions\ngono243.wly\cs\Microsoft.VisualStudio.ConnectedServices.Azure.Storage.resources.dll file deleted.
[0d2c:0015][2017-09-06T23:34:16] Processing file /pt-BR/Microsoft.VisualStudio.ConnectedServices.Azure.Storage.resources.dll
[0d2c:0015][2017-09-06T23:34:16] C:\Program Files\Microsoft Visual Studio\2017\Community\Common7\IDE\Extensions\ngono243.wly\pt-BR\Microsoft.VisualStudio.ConnectedServices.Azure.Storage.resources.dll file deleted.
[0d2c:0015][2017-09-06T23:34:16] Processing file /pl/Microsoft.VisualStudio.ConnectedServices.Azure.Storage.resources.dll
[0d2c:0015][2017-09-06T23:34:16] C:\Program Files\Microsoft Visual Studio\2017\Community\Common7\IDE\Extensions\ngono243.wly\pl\Microsoft.VisualStudio.ConnectedServices.Azure.Storage.resources.dll file deleted.
[0d2c:0015][2017-09-06T23:34:16] Processing file /tr/Microsoft.VisualStudio.ConnectedServices.Azure.Storage.resources.dll
[0d2c:0015][2017-09-06T23:34:16] C:\Program Files\Microsoft Visual Studio\2017\Community\Common7\IDE\Extensions\ngono243.wly\tr\Microsoft.VisualStudio.ConnectedServices.Azure.Storage.resources.dll file deleted.
[0d2c:0015][2017-09-06T23:34:16] Processing file /zh-Hans/extension.vsixlangpack
[0d2c:0015][2017-09-06T23:34:16] C:\Program Files\Microsoft Visual Studio\2017\Community\Common7\IDE\Extensions\ngono243.wly\zh-Hans\extension.vsixlangpack file deleted.
[0d2c:0015][2017-09-06T23:34:16] Processing file /zh-Hant/extension.vsixlangpack
[0d2c:0015][2017-09-06T23:34:16] C:\Program Files\Microsoft Visual Studio\2017\Community\Common7\IDE\Extensions\ngono243.wly\zh-Hant\extension.vsixlangpack file deleted.
[0d2c:0015][2017-09-06T23:34:16] Processing file /de/extension.vsixlangpack
[0d2c:0015][2017-09-06T23:34:16] C:\Program Files\Microsoft Visual Studio\2017\Community\Common7\IDE\Extensions\ngono243.wly\de\extension.vsixlangpack file deleted.
[0d2c:0015][2017-09-06T23:34:16] Processing file /es/extension.vsixlangpack
[0d2c:0015][2017-09-06T23:34:16] C:\Program Files\Microsoft Visual Studio\2017\Community\Common7\IDE\Extensions\ngono243.wly\es\extension.vsixlangpack file deleted.
[0d2c:0015][2017-09-06T23:34:16] Processing file /fr/extension.vsixlangpack
[0d2c:0015][2017-09-06T23:34:16] C:\Program Files\Microsoft Visual Studio\2017\Community\Common7\IDE\Extensions\ngono243.wly\fr\extension.vsixlangpack file deleted.
[0d2c:0015][2017-09-06T23:34:16] Processing file /it/extension.vsixlangpack
[0d2c:0015][2017-09-06T23:34:16] C:\Program Files\Microsoft Visual Studio\2017\Community\Common7\IDE\Extensions\ngono243.wly\it\extension.vsixlangpack file deleted.
[0d2c:0015][2017-09-06T23:34:16] Processing file /ja/extension.vsixlangpack
[0d2c:0015][2017-09-06T23:34:16] C:\Program Files\Microsoft Visual Studio\2017\Community\Common7\IDE\Extensions\ngono243.wly\ja\extension.vsixlangpack file deleted.
[0d2c:0015][2017-09-06T23:34:16] Processing file /ko/extension.vsixlangpack
[0d2c:0015][2017-09-06T23:34:16] C:\Program Files\Microsoft Visual Studio\2017\Community\Common7\IDE\Extensions\ngono243.wly\ko\extension.vsixlangpack file deleted.
[0d2c:0015][2017-09-06T23:34:16] Processing file /ru/extension.vsixlangpack
[0d2c:0015][2017-09-06T23:34:16] C:\Program Files\Microsoft Visual Studio\2017\Community\Common7\IDE\Extensions\ngono243.wly\ru\extension.vsixlangpack file deleted.
[0d2c:0015][2017-09-06T23:34:16] Processing file /cs/extension.vsixlangpack
[0d2c:0015][2017-09-06T23:34:16] C:\Program Files\Microsoft Visual Studio\2017\Community\Common7\IDE\Extensions\ngono243.wly\cs\extension.vsixlangpack file deleted.
[0d2c:0015][2017-09-06T23:34:16] Processing file /pt-BR/extension.vsixlangpack
[0d2c:0015][2017-09-06T23:34:16] C:\Program Files\Microsoft Visual Studio\2017\Community\Common7\IDE\Extensions\ngono243.wly\pt-BR\extension.vsixlangpack file deleted.
[0d2c:0015][2017-09-06T23:34:16] Processing file /pl/extension.vsixlangpack
[0d2c:0015][2017-09-06T23:34:16] C:\Program Files\Microsoft Visual Studio\2017\Community\Common7\IDE\Extensions\ngono243.wly\pl\extension.vsixlangpack file deleted.
[0d2c:0015][2017-09-06T23:34:16] Processing file /tr/extension.vsixlangpack
[0d2c:0015][2017-09-06T23:34:16] C:\Program Files\Microsoft Visual Studio\2017\Community\Common7\IDE\Extensions\ngono243.wly\tr\extension.vsixlangpack file deleted.
[0d2c:0015][2017-09-06T23:34:16] Processing file /manifest.json
[0d2c:0015][2017-09-06T23:34:16] C:\Program Files\Microsoft Visual Studio\2017\Community\Common7\IDE\Extensions\ngono243.wly\manifest.json file deleted.
[0d2c:0015][2017-09-06T23:34:16] Processing file /catalog.json
[0d2c:0015][2017-09-06T23:34:16] C:\Program Files\Microsoft Visual Studio\2017\Community\Common7\IDE\Extensions\ngono243.wly\catalog.json file deleted.
[0d2c:0015][2017-09-06T23:34:16] Started: Deleting empty directories
[0d2c:0015][2017-09-06T23:34:16] Completed: Deleting empty directories
[0d2c:0015][2017-09-06T23:34:16] Package executed successfully. Return code: 0
Hi, after update to 15.3.3 I lost the feature to write down the value and display fields in Datasource configuration wizard when selecting Objectdatasource, the selector dropdown became not editable, I have to F4 and set them using properties windows.