runtime: .NET Runtime missing prompt is not redirecting to the correct runtime URL
Description
When the .NET Core Runtime is a missing you receive a messagebox where when the user agrees, it redirects the user to the download page where he can install it. Previously it has redirected the user to the correct runtime version. Now it redirects to https://dotnet.microsoft.com/download/dotnet-core/?utm_source=getdotnetcore&utm_medium=referral which is a collection of ALL runtimes, the end user will download the wrong version. The application will not launch and show the message again. We are currently receiving many support tickets because of this.
User sees this messagebox
And gets redirect to this URL:
And when he clicks on something, it gives them the SDK

Expectation
Because this is a (64bit) .NET Core 3.1 desktop application, it should redirect to https://dotnet.microsoft.com/download/dotnet-core/3.1/runtime/desktop/x64 OR at least to https://dotnet.microsoft.com/download/dotnet-core/3.1/runtime
Configuration
Published as .NET Core 3.1 Windows 10 (desktop application WPF or Winforms)
Host (useful for support):
Version: 5.0.0-preview.3.20214.6
Commit: b037784658
.NET SDKs installed:
3.1.201 [C:\Program Files\dotnet\sdk]
3.1.202 [C:\Program Files\dotnet\sdk]
3.1.300-preview-015135 [C:\Program Files\dotnet\sdk]
5.0.100-preview.3.20216.6 [C:\Program Files\dotnet\sdk]
Regression?
Yes, it has worked before. I cannot say when it has stopped working, but it seems to be more a website redirect issue.
Related
https://github.com/dotnet/runtime/issues/3848
ping: @dagood @richlander @vitek-karas
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Reactions: 5
- Comments: 28 (19 by maintainers)
@vitek-karas @richlander Any update on this? Can we please get this fixed for .NET 6? Because on RC1 this issue still exist, the prompt clearly says what’s missing:
clicking on yes opens an URL which contains all the necessary information:
https://aka.ms/dotnet-core-applaunch?missing_runtime=true&arch=x64&rid=win10-x64&apphost_version=6.0.0-rc.1.21451.13&gui=truebut user gets redirected to:https://dotnet.microsoft.com/download/dotnet/6.0/runtime?utm_source=getdotnetcore&utm_medium=referralWhich offers ALL versions of .NET 6 (Console, Desktop Server) including x86 and Arm64. This is getting odd that this bug is not getting any attention for so long time.I’ve assigned this to myself. This is a high-priority task for my team and we’ll work on this as soon as we’re done with some MAUI work.
Thanks @DubbleClick. I looked at our telemetry and I figured out what was happening. We’re pushing a fix in a few minutes.
It was checking the browser agent instead of respecting the arch being passed. We now have browser agent as a fallback, if needed.
Works great, thank you very much.
Edit: Nevermind, it only works great for the x64 version. If your application requires the x86 desktop runtime, it still downloads the x64 desktop one.
Hey folks! We pushed a fix for this to production this week and we’re monitoring to see if we have any issues with any of the redirects. Please let me know if any redirect is not behaving as expected.
Yes, that’s what we’re doing @DubbleClick and the work has already started now. So the fix should be coming soon.
Moving to 8 as there’s no work on the runtime for 7, this is basically a tracking bug for the work on the website, which can happen at any time (not bound to the same release schedule as runtime repo).
Has this been looked at yet? On a current WinForms app, this is the URL that starts:
https://aka.ms/dotnet-core-applaunch?missing_runtime=true&arch=x64&rid=win10-x64&apphost_version=6.0.4&gui=trueThat gets you redirected here:
https://dotnet.microsoft.com/en-us/download/dotnet/6.0/runtime?cid=getdotnetcoreTo improve the experience, the redirect should point here instead:
https://dotnet.microsoft.com/en-us/download/dotnet/thank-you/runtime-desktop-6.0.4-windows-x64-installer…and here for x86:
https://dotnet.microsoft.com/en-us/download/dotnet/thank-you/runtime-desktop-6.0.4-windows-x86-installerThat leads the user to a direct download and makes it easier.
Thanks for the reminder - I’ll ping the right people again.
Sorry - I didn’t realize it’s private. I’ll keep this issue opened for tracking purposes.
This is up to me to fix. I’ll look at it. I had noticed the same thing, but hadn’t fixed it yet.