Jacques Eloff

> @joeloff does this line up with your expectation of the layouts for the runtimes on macOS? Yes. though it would apply to the SDK too. Any x64 pieces should...

5.0.401 - 5.0.10 runtime 5.0.303 - 5.0.9 runtime 3.1.413 - 3.1.19 runtime 2.2.207 - 2.2.8 runtime Those runtimes that show in ARP likely came through MU. The Desktop runtime will...

So in VS, if you selected the 3.1 Runtime, you'll get the targeting packs, runtime (.NET Core) and Desktop runtime. When Microsoft Update scan the machine, it could offer the...

@sfoslund for desktop, you'd want to include `(displayName.IndexOf("Windows Desktop Runtime", StringComparison.OrdinalIgnoreCase) >= 0)` Originally it shipped using "Shared Framework for Windows Desktop", but was changed later to be "Windows Desktop...

Based on the logs, I'm seeing standalone MSI installs for the following (which the uninstall tool won't remove). {84BBB763-AD8F-4033-8429-3DFC7C9FF3E2} Microsoft .NET Runtime - 5.0.12 (x64) {9E190CBD-B034-491A-BD02-BDDBB4D67F74} Microsoft .NET Runtime -...

You left out the `/x` on the commandline When installed with VS (or the EXE bundles when we have 10+ MSIs per release, the MSIs are hidden from ARP)

If you don't plan to target those it should be fine I think to remove those too.

It would. The VS logs would help to tell us whether anything else was installed that referenced the same SDK installers that shipped with VS.

Log collection tool: https://www.microsoft.com/en-us/download/details.aspx?id=12493 @adrianwright109 those two entries in ARP don't actually represent anything. It's just there to let users know when the SDK was installed as part of Visual...

The authentication relates to the package feed it's trying to access. Check your global nuget.config file for that package source and potentially remove it. You can run ```dotnet nuget list...