Workload error recovery problems.

[lewing]

We've been testing dotnet workload install on multiple platforms and we've run into a few cases where a network failure occurred. If you try to run dotnet workload install again after the network error we've seen a different failure that looks like (on windows)

Writing workload pack installation record for Microsoft.NET.Runtime.Emscripten.Python version 6.0.0-preview.6.21268.1...
Installing pack Microsoft.NET.Runtime.Emscripten.Sdk version 6.0.0-preview.6.21268.1...
Workload installation failed, rolling back installed packs...
Installing workload manifest microsoft.net.sdk.android version 11.0.200-ci.main.256.
Installation roll back failed: Failed to install manifest microsoft.net.sdk.android version 11.0.200-ci.main.256: The transaction has aborted..
Rolling back pack Microsoft.NETCore.App.Runtime.Mono.browser-wasm installation...
Rolling back pack Microsoft.NET.Runtime.MonoAOTCompiler.Task installation...
Rolling back pack Microsoft.NET.Runtime.WebAssembly.Sdk installation...
Rolling back pack Microsoft.NETCore.App.Runtime.AOT.Cross.browser-wasm installation...
Rolling back pack Microsoft.NET.Runtime.Emscripten.Node installation...
Rolling back pack Microsoft.NET.Runtime.Emscripten.Python installation...
Rolling back pack Microsoft.NET.Runtime.Emscripten.Sdk installation...
Workload installation failed: One or more errors occurred. (Number of entries expected in End Of Central Directory does not correspond to number of entries in Central Directory.)

And exits

Running install a third time does seem to succeed after that.

[dotnet-issue-labeler]

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.

[lewing]

cc @pavelsavara @radekdoulik

[sfoslund]

@lewing are you still seeing this? Can you provide a repro version?

[sfoslund]

Ping @lewing, is this still an issue?

[lewing]

@sfoslund we're still seeing rollback problems in preview5 dotnet/runtime#54342

[sfoslund]

I've filed #18450 for the installation issues in that issue. That error seems to be different from the one you originally reported here though, are you still seeing the One or more errors occurred. (Number of entries expected in End Of Central Directory does not correspond to number of entries in Central Directory.) you mentioned above?

[lewing]

haven't seen that recently

[sfoslund]

Sounds good, I'll close this issue then and track the other error in #18450

[doniyorniazov]

I Still have this issue when doing "dotnet workload install maui"

[almas-f]

I Still have this issue when doing "dotnet workload install maui"

I have the same issue while installing maui workload

[sfoslund]

@doniyorniyozov @almas-f which errors have you been seeing, can you provide the output from the command? What versions of .NET are you using?

[doniyorniazov]

@sfoslund I'm getting "Workload with id maui is not recognized." message. I tried to repair and it didn't work either. How I can completely delete all workloads and reinstall again?

SDK version: 6.0.100-preview.7.21379.14

[sfoslund]

@doniyorniyozov what's the output of dotnet workload search? What OS are you on?

[doniyorniazov]

@sfoslund
OS: Windows.

This is what I get when I do dotnet workload search.

[sfoslund]

Okay, based on the output of workload search it looks like you're missing manifests. Does the dotnet/sdk-manifests dir exist? If so, what's inside of it? If not, then your sdk installation is broken and you'll want to either repair or re-install the sdk.

[pavelsavara]

I saw Workload installation failed: Number of entries expected in End Of Central Directory does not correspond to number of entries in Central Directory on my windows machine today too with 7.0.0-alpha.1.21560.2. It was in single purpose runtime\artifacts\bin\dotnet-workload folder.
Possibly I caused it myself by interrupting the workload installation at wrong moment and then restarted it.

I resolved it by deleting whole dotnet folder and installing again. Then it just worked.