dotnet-sdk-3.1.406-win-x64 failed to install, always

[EricOuellet2]

Description

Always getting error :

[4E6C:35F0][2021-02-25T14:08:15]e000: Error 0x80070002: Failed to find payload: AspNetCoreSharedFramework_x64 in working path: C:\LOCAL\TEMP{C8B06F83-D0BD-4A3C-86FF-E0115FE762B4}\AspNetCoreSharedFramework_x64 and unverified path: C:\ProgramData\Package Cache.unverified\AspNetCoreSharedFramework_x64
[4E6C:35F0][2021-02-25T14:08:15]e000: Error 0x80070002: Failed to cache payload: AspNetCoreSharedFramework_x64

I expect to install without any fuss.

Configuration

Windows 10 1803. Visual Studio 2019 latest.
I do have Asp.Net development selected in VS2019 installation.

Regression?

???

Other information

Log included
Microsoft_.NET_Core_SDK_3.1.406_(x64)_20210225140807.log

I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label.

[EricOuellet2]

I guess : area-Infrastructure-installer because it is the only one with "Installer in it" ?

[danmoseley]

@wli3 should this go to the sdk repo? or the installer repo?

[wli3]

should be in https://github.com/aspnet/AspNetCore the msi is produced there

[danmoseley]

Thanks @wli3. transferring there.

[danmoseley]

sounds like #28029 which looks like it has a fix #30439 schedule for 3.1.14. (April)
perhaps they can help with a workaround meantime.

[javiercn]

@EricOuellet2 thanks for reporting this.

@dotnet/aspnet-build folks, can you check this out?

/cc: @Pilchie

[Pilchie]

@wtgodbe checked in the fix, and @joeloff was looking for workaround.

[dougbu]

help with a workaround meantime

@wtgodbe @joeloff is there a way to work around this issue prior to the April 3.1.14 release❔

[joeloff]

@EricOuellet2 can you provide this log file: C:\LOCAL\TEMP\Microsoft_.NET_Core_SDK_3.1.406_(x64)_20210225140807_014_AspNetCoreSharedFramework_x64.log

[EricOuellet2]

Microsoft_.NET_Core_SDK_3.1.406_(x64)_20210225140807_014_AspNetCoreSharedFramework_x64.log

This is it

[joeloff]

This looks like the SEC REPAIR issue we're fixing for the next release where it's conflicting with the original source location of the install from VS.

@EricOuellet2 You can try the following from a commandline: <SDK.EXE> /install OPT_NO_SHAREDFX=1

[EricOuellet2]

Still failed.

Microsoft_.NET_Core_SDK_3.1.406_(x64)_20210226152123.log
Microsoft_.NET_Core_SDK_3.1.406_(x64)_20210226152123_014_AspNetCoreSharedFramework_x64.log