Windows 10: Installing .NET Core SDK fails.

ChadAllen1 · May 4, 2019

Hello,

I am trying to install the .NET Core SDK version 2.2.203 (latest as of today), but the installation fails immediately with error, "User cancelled installation." with "Retry" and "Cancel" buttons. I did not cancel the installation. Clicking Retry immediately results in the same window appearing. I did run the installer as administrator.

If I click "Cancel" I get a "Setup Failed" window with the following:

Setup Failed

One or more issues caused the setup to fail. Please fix the issues and then retry setup. For more information see the log file.

0x80070642 - User cancelled installation.

The referenced log file contains the following:

[38EC:3578][2019-05-04T14:16:59]i001: Burn v3.10.4.4718, Windows v10.0 (Build 17763: Service Pack 0), path: C:\WINDOWS\Temp\{E6E7F00F-A56E-4459-969A-73A476B752A8}\.cr\dotnet-sdk-2.2.203-win-gs-x64.exe

[38EC:3578][2019-05-04T14:16:59]i000: Initializing string variable 'DOTNETHOME' to value '[ProgramFiles6432Folder]dotnet'

[38EC:3578][2019-05-04T14:16:59]i000: Initializing string variable 'BUNDLEMONIKER' to value 'Microsoft .NET Core SDK 2.2.203'

[38EC:3578][2019-05-04T14:16:59]i000: Initializing string variable 'DOTNETSDKVERSION' to value '2.2.203'

[38EC:3578][2019-05-04T14:16:59]i000: Initializing string variable 'DOTNETRUNTIMEVERSION' to value '2.2.4'

[38EC:3578][2019-05-04T14:16:59]i000: Initializing string variable 'ASPNETCOREVERSION' to value '2.2.4'

[38EC:3578][2019-05-04T14:16:59]i009: Command Line: '-burn.clean.room=C:\Users\ME\Downloads\dotnet-sdk-2.2.203-win-gs-x64.exe -burn.filehandle.attached=228 -burn.filehandle.self=616'

[38EC:3578][2019-05-04T14:16:59]i000: Setting string variable 'WixBundleOriginalSource' to value 'C:\Users\ME\Downloads\dotnet-sdk-2.2.203-win-gs-x64.exe'

[38EC:3578][2019-05-04T14:16:59]i000: Setting string variable 'WixBundleOriginalSourceFolder' to value 'C:\Users\ME\Downloads\'

[38EC:3578][2019-05-04T14:16:59]i000: Setting string variable 'WixBundleLog' to value 'C:\Users\ME\AppData\Local\Temp\Microsoft_.NET_Core_SDK_2.2.203_(x64)_20190504141659.log'

[38EC:3578][2019-05-04T14:16:59]i000: Setting string variable 'WixBundleName' to value 'Microsoft .NET Core SDK 2.2.203 (x64)'

[38EC:3578][2019-05-04T14:16:59]i000: Setting string variable 'WixBundleManufacturer' to value 'Microsoft Corporation'

[38EC:2B0C][2019-05-04T14:16:59]i000: Setting numeric variable 'WixStdBALanguageId' to value 1033

[38EC:2B0C][2019-05-04T14:16:59]i000: Setting version variable 'WixBundleFileVersion' to value '2.2.203.0'

[38EC:3578][2019-05-04T14:17:00]i100: Detect begin, 5 packages

[38EC:3578][2019-05-04T14:17:00]i101: Detected package: dotnet_runtime_2.2.4_win_x64.msi, state: Absent, cached: None

[38EC:3578][2019-05-04T14:17:00]i101: Detected package: dotnet_hostfxr_2.2.4_win_x64.msi, state: Absent, cached: None

[38EC:3578][2019-05-04T14:17:00]i101: Detected package: dotnet_host_2.2.4_win_x64.msi, state: Absent, cached: None

[38EC:3578][2019-05-04T14:17:00]i101: Detected package: dotnet_sdk_internal_2.2.203_win_x64.msi, state: Absent, cached: None

[38EC:3578][2019-05-04T14:17:00]i101: Detected package: AspNetCoreSharedFramework_x64, state: Absent, cached: None

[38EC:3578][2019-05-04T14:17:00]i199: Detect complete, result: 0x0

[38EC:3578][2019-05-04T14:17:02]i200: Plan begin, 5 packages, action: Install

[38EC:3578][2019-05-04T14:17:02]i000: Setting string variable 'WixBundleRollbackLog_dotnet_runtime_2.2.4_win_x64.msi' to value 'C:\Users\ME\AppData\Local\Temp\Microsoft_.NET_Core_SDK_2.2.203_(x64)_20190504141659_000_dotnet_runtime_2.2.4_win_x64.msi_rollback.log'

[38EC:3578][2019-05-04T14:17:02]i000: Setting string variable 'WixBundleLog_dotnet_runtime_2.2.4_win_x64.msi' to value 'C:\Users\ME\AppData\Local\Temp\Microsoft_.NET_Core_SDK_2.2.203_(x64)_20190504141659_000_dotnet_runtime_2.2.4_win_x64.msi.log'

[38EC:3578][2019-05-04T14:17:02]i000: Setting string variable 'WixBundleRollbackLog_dotnet_hostfxr_2.2.4_win_x64.msi' to value 'C:\Users\ME\AppData\Local\Temp\Microsoft_.NET_Core_SDK_2.2.203_(x64)_20190504141659_001_dotnet_hostfxr_2.2.4_win_x64.msi_rollback.log'

[38EC:3578][2019-05-04T14:17:02]i000: Setting string variable 'WixBundleLog_dotnet_hostfxr_2.2.4_win_x64.msi' to value 'C:\Users\ME\AppData\Local\Temp\Microsoft_.NET_Core_SDK_2.2.203_(x64)_20190504141659_001_dotnet_hostfxr_2.2.4_win_x64.msi.log'

[38EC:3578][2019-05-04T14:17:02]i000: Setting string variable 'WixBundleRollbackLog_dotnet_host_2.2.4_win_x64.msi' to value 'C:\Users\ME\AppData\Local\Temp\Microsoft_.NET_Core_SDK_2.2.203_(x64)_20190504141659_002_dotnet_host_2.2.4_win_x64.msi_rollback.log'

[38EC:3578][2019-05-04T14:17:02]i000: Setting string variable 'WixBundleLog_dotnet_host_2.2.4_win_x64.msi' to value 'C:\Users\ME\AppData\Local\Temp\Microsoft_.NET_Core_SDK_2.2.203_(x64)_20190504141659_002_dotnet_host_2.2.4_win_x64.msi.log'

[38EC:3578][2019-05-04T14:17:02]i000: Setting string variable 'WixBundleRollbackLog_dotnet_sdk_internal_2.2.203_win_x64.msi' to value 'C:\Users\ME\AppData\Local\Temp\Microsoft_.NET_Core_SDK_2.2.203_(x64)_20190504141659_003_dotnet_sdk_internal_2.2.203_win_x64.msi_rollback.log'

[38EC:3578][2019-05-04T14:17:02]i000: Setting string variable 'WixBundleLog_dotnet_sdk_internal_2.2.203_win_x64.msi' to value 'C:\Users\ME\AppData\Local\Temp\Microsoft_.NET_Core_SDK_2.2.203_(x64)_20190504141659_003_dotnet_sdk_internal_2.2.203_win_x64.msi.log'

[38EC:3578][2019-05-04T14:17:02]i052: Condition 'VersionNT64 AND (NOT OPT_NO_SHAREDFX)' evaluates to true.

[38EC:3578][2019-05-04T14:17:02]i000: Setting string variable 'WixBundleRollbackLog_AspNetCoreSharedFramework_x64' to value 'C:\Users\ME\AppData\Local\Temp\Microsoft_.NET_Core_SDK_2.2.203_(x64)_20190504141659_004_AspNetCoreSharedFramework_x64_rollback.log'

[38EC:3578][2019-05-04T14:17:02]i000: Setting string variable 'WixBundleLog_AspNetCoreSharedFramework_x64' to value 'C:\Users\ME\AppData\Local\Temp\Microsoft_.NET_Core_SDK_2.2.203_(x64)_20190504141659_004_AspNetCoreSharedFramework_x64.log'

[38EC:3578][2019-05-04T14:17:02]i201: Planned package: dotnet_runtime_2.2.4_win_x64.msi, state: Absent, default requested: Present, ba requested: Present, execute: Install, rollback: Uninstall, cache: Yes, uncache: No, dependency: Register

[38EC:3578][2019-05-04T14:17:02]i201: Planned package: dotnet_hostfxr_2.2.4_win_x64.msi, state: Absent, default requested: Present, ba requested: Present, execute: Install, rollback: Uninstall, cache: Yes, uncache: No, dependency: Register

[38EC:3578][2019-05-04T14:17:02]i201: Planned package: dotnet_host_2.2.4_win_x64.msi, state: Absent, default requested: Present, ba requested: Present, execute: Install, rollback: Uninstall, cache: Yes, uncache: No, dependency: Register

[38EC:3578][2019-05-04T14:17:02]i201: Planned package: dotnet_sdk_internal_2.2.203_win_x64.msi, state: Absent, default requested: Present, ba requested: Present, execute: Install, rollback: Uninstall, cache: Yes, uncache: No, dependency: Register

[38EC:3578][2019-05-04T14:17:02]i201: Planned package: AspNetCoreSharedFramework_x64, state: Absent, default requested: Present, ba requested: Present, execute: Install, rollback: Uninstall, cache: Yes, uncache: No, dependency: Register

[38EC:3578][2019-05-04T14:17:02]i299: Plan complete, result: 0x0

[38EC:3578][2019-05-04T14:17:02]i300: Apply begin

[38EC:3578][2019-05-04T14:17:02]i010: Launching elevated engine process.

[38EC:3578][2019-05-04T14:17:02]e000: Error 0x800704c7: Failed to launch elevated child process: C:\WINDOWS\Temp\{B183CA6D-FCEB-485A-8E10-F90553041CF6}\.be\dotnet-sdk-2.2.203-win-x64.exe

[38EC:3578][2019-05-04T14:20:52]e000: Error 0x80070642: Failed to elevate.

[38EC:3578][2019-05-04T14:20:52]e000: Error 0x80070642: Failed to actually elevate.

[38EC:3578][2019-05-04T14:20:52]e000: Error 0x80070642: Failed to elevate.

[38EC:3578][2019-05-04T14:20:52]i399: Apply complete, result: 0x80070642, restart: None, ba requested restart: No

I have noticed problems installing various other pieces of software. All of the ones that fail seem to be ones which attempt to launch some other process with elevated privileges.

:)

ufo · May 4, 2019

Uninstall .NET Core SDK older versions

I've got many versions of .NET Core SDK installed in my Windows 10 PC. I'm wondering if older versions can be uninstalled:

List of installed softwares

I'm not sure how .NET Core versioning works and if I need specific version in my PC.

Brink · May 4, 2019

Announcing .NET Core, .NET Native and NuGet Updates in VS 2017 RC

We just released updates to the .NET Core SDK, .NET Native Tools and NuGet, all of which are included in Visual Studio 2017 RC. You can also install the .NET Core SDK for command-line use, on Windows, Mac and Linux. Please check out the ASP.NET blog to learn more about Web Tools updates and the Visual Studio blog for the Visual Studio 2017 RC update.

Install Visual Studio 2017 RC

Install .NET Core 1.0 SDK – RC3

The following improvements are the .NET highlights of the release:

.NET Core – The csproj project format has been simplified and project migration is much more reliable.

.NET Native – Major performance increase for SIMD and other performance improvements.

NuGet – .NET Framework, UWP, .NET Core and other .NET projects can now use PackageReference instead of packages.config for NuGet dependencies.

Note: csproj projects created with earlier releases of Visual Studio 2017 or on the command-line with the .NET Core SDK must be manually updated to load in the latest release. Please read the Updating .NET Core Projects section, below, for more information.

.NET Core

The .NET Core tools have been significantly improved in this update, fixing bugs and usability issues. A major focus of this release has been simplifying the project file and improving project migration. We are no longer using the “preview” term, but “RC3” to match Visual Studio 2017 RC.

The tools in the new SDK produce and operate on csproj projects. If you are using project.json projects, including with Visual Studio 2015, then please wait to install the new SDK until you are ready to move to csproj and MSBuild. If you are a Visual Studio user, you will get the SDK when you install Visual Studio 2017. See Known issues for Web Tools, and ASP.NET and ASP.NET/.NET Core in Visual Studio 2017.

Getting the Release

This .NET Core SDK release is available in Visual Studio 2017 RC, as part of the .NET Core cross-platform development workload. It is also available in the ASP.NET Web workload and an optional component of the .NET Desktop workload. These workloads can be selected as part of the Visual Studio 2017 RC installation process. The ability to build and consume .NET Standard class libraries is available in the all of the above workloads and in the UWP workload.

You can also install the .NET Core SDK release for command-line use on Windows, macOS and Linux by following the instructions at .NET Core 1.0 – RC3 Download.

The release is also available as Docker images, in the dotnet repo. The following images include the new SDK:

1.0.3-sdk-msbuild-rc3

1.0.3-sdk-msbuild-rc3-nanoserver

1.1.0-sdk-msbuild-rc3

1.1.0-sdk-msbuild-rc3-nanoserver

The aspnetcore-build repo has also been updated.

.NET Core SDK Components

This release contains the .NET Core Tools 1.0 RC3, the .NET Core 1.0.3 runtime and the .NET Core 1.1.0 runtime. No changes have been made to the .NET Core runtime in this release. .NET Core 1.0.3 and 1.1.0 were both released previously.

The .NET Core SDK includes a set of .NET Core Tools and one of more runtimes. In previous SDK releases, there was only ever one runtime included. This change in approach was made to make it easier to acquire all supported runtimes as a single step. This experience helps when you are collaborating with developers who are using multipe runtimes. It also makes it easier to update multiple runtimes on your machine when fixes are released. The SDK naturally gets larger, but not as much as you might guess since there is only ever one set of tools in the package. It also enables us to improve the tools for everyone more easily...
Click to expand...

Read more: https://blogs.msdn.microsoft.com/dot...in-vs-2017-rc/

Brink · May 4, 2019

.NET Core October 2018 Update - NET Core 1.0 and 1.1

Today, we are releasing the .NET Core October 2018 Update for 1.0 and 1.1. This update includes .NET Core 1.0.13, 1.1.10 and .NET Core SDK 1.1.11.

Security

CVE-2018-8292: .NET Core Information Disclosure Vulnerability

Microsoft is aware of a security feature bypass vulnerability that exists when .NET Core when HTTP authentication information is inadvertently exposed in an outbound request that encounters an HTTP redirect. An attacker who successfully exploited this vulnerability could use the information to further compromise the web application.

The update addresses the vulnerability by correcting how .NET Core applications handles HTTP redirects.

Getting the Update

The latest .NET Core updates are available on the .NET Core download page.

Today’s releases are listed as follows:

.NET Core 1.1.10

.NET Core 1.0.13

Docker Images

.NET Docker images have been updated for today’s release. The following repos have been updated.

microsoft/dotnet

Note: Look at the “Tags” view in each repository to see the updated Docker image tags.

Note: You must re-pull base images in order to get updates. The Docker client does not pull updates automatically.

Azure App Services deployment

Deployment to Azure App Services has begun and the West Central US region will be live this morning. Remaining regions will be updated over the next few days and deployment is expected to be complete by end of week.
Click to expand...

Source: .NET Core October 2018 Update - NET Core 1.0 and 1.1 | .NET Blog

Windows 10: Installing .NET Core SDK fails.

Installing .NET Core SDK fails.

Installing .NET Core SDK fails.

Installing .NET Core SDK fails.

Installing .NET Core SDK fails. - Similar Threads - Installing NET Core

Unable to install .NET 6 SDK SOLVED

Unable to install .NET 6 SDK

Unable to install .NET 6 SDK

Unable to install .NET 6 SDK

.NET SDK installation issue: SDK not recognized despite successful installation

.NET SDK installation issue: SDK not recognized despite successful installation

.NET SDK installation issue: SDK not recognized despite successful installation

Windows SDK installation failed

.NET Core 1.0.0 RC2 SDK Preview1