April 13, 2026 | Read Time: 4 minutes
// Direct download link for the Desktop Runtime Process.Start(new ProcessStartInfo FileName = "https://aka.ms/dotnet-core-applaunch?missing_runtime=true&arch=x64&rid=win-x64&apphost_version=8.0.4", UseShellExecute = true );
const string runtimeKey = @"SOFTWARE\dotnet\Setup\InstalledVersions\x64\sharedfx\Microsoft.WindowsDesktop.App"; using var key = Registry.LocalMachine.OpenSubKey(runtimeKey); var installedVersion = key?.GetValue("Version") as string; .net desktop runtime 8
if (result == MessageBoxResult.Yes)
dotnet publish -c Release -r win-x64 --self-contained true -p:PublishSingleFile=true Zero runtime dependencies. Works on Windows 7, 10, 11, and Server 2016+. Cons: Large file size (~70-120 MB per app). Must redeploy to update runtime. Strategy 2: Bootstrap with the Official Detector (The "User-Friendly" Way) Keep your app small (framework-dependent) but add a runtime check on startup. April 13, 2026 | Read Time: 4 minutes
You build your app against 8.0.4 . Your user has 8.0.1 installed. Your app tries to load and fails with: "Application has stopped working" or a silent crash in event logs. Why? Starting with .NET 8, the runtime rolls forward, but only within certain bounds. If your app is published as framework-dependent (the default), it requires the exact same major.minor version (8.0.x). A missing 8.0.4 dependency will break. The Fix: Two Professional Strategies Stop telling users to "go download a runtime." Here are your two reliable solutions. Strategy 1: Self-Contained Deployment (The "Nuclear Option") Publish your app with the runtime bundled inside the .exe . No runtime installation required.
Mastering the .NET Desktop Runtime 8: Solving the "Missing Runtime" Nightmare for Good Must redeploy to update runtime
The aka.ms link auto-detects the user's architecture and downloads the Desktop Runtime (not the SDK or ASP.NET). Pro Tip: Validate Your Build with the .NET CLI Before shipping, run this command locally to see exactly what your app expects: