aspnetcore: Unable to repair .NET 5 SDK with error "Failed to find payload: AspNetCoreSharedFramework_x64"
Running dotnet-sdk-5.0.100-win-x64.exe to perform a repair.
[1BB4:146C][2020-11-12T13:06:58]e000: Error 0x80070002: Failed to find payload: AspNetCoreSharedFramework_x64 in working path: C:\Users\augustoproiete\AppData\Local\Temp\{482F5E84-80CE-4DA0-A5AB-6EBF3622BB3D}\AspNetCoreSharedFramework_x64 and unverified path: C:\ProgramData\Package Cache\.unverified\AspNetCoreSharedFramework_x64
[1BB4:146C][2020-11-12T13:06:58]e000: Error 0x80070002: Failed to cache payload: AspNetCoreSharedFramework_x64
[2EB8:1088][2020-11-12T13:06:58]e314: Failed to cache payload: AspNetCoreSharedFramework_x64 from working path: C:\Users\augustoproiete\AppData\Local\Temp\{482F5E84-80CE-4DA0-A5AB-6EBF3622BB3D}\AspNetCoreSharedFramework_x64, error: 0x80070002.
// ...
[1BB4:1BA4][2020-11-12T13:07:50]e000: Error 0x80070643: Failed to run maintanance mode for MSI package.
[1BB4:1BA4][2020-11-12T13:07:50]e000: Error 0x80070643: Failed to execute MSI package.
[2EB8:3110][2020-11-12T13:07:50]e000: Error 0x80070643: Failed to configure per-machine MSI package.
[2EB8:3110][2020-11-12T13:07:50]i319: Applied execute package: AspNetCoreSharedFramework_x64, result: 0x80070643, restart: None
[2EB8:3110][2020-11-12T13:07:50]e000: Error 0x80070643: Failed to execute MSI package.
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Reactions: 2
- Comments: 17 (11 by maintainers)
I’ve been able to reproduce this. The problem is with one of the installer file names that’s different in the standalone bundle compared to VS (the files are binary matches). In this scenario, SEC REPAIR kicks in and can’t resolve the installer source. Even if you place the installer in the SEC REPAIR exclusion list, it will resolve to the correct cache path, but then fail to resolve the filename.
Right now, installing the 5.0 SDK through VS, then applying the standalone installer and doing a repair from the latter will not work. There might be a way to do fool the installer by editing some other registry keys, BUT, when you repair VS it will be in the same situation and then fail to repair.
I’m going to move the issue to ASP.NET Core and we can get this addressed for the next release.
Unfortunately don’t have the bandwidth today, and I’m OOF until after thanksgiving - I can take a look when I get back
Hah. We don’t build the SDK, so I moved it here.