Microsoft Windows Desktop Runtime 6.0.5 (x64): Fix Broken Apps in 3 Steps

Windows

Microsoft Windows Desktop Runtime 6.0.5 (x64): Fix Broken Apps in 3 Steps

The Microsoft Windows Desktop Runtime 6.0.5 (x64) is the backbone for modern apps like Visual Studio, .NET, and even some games—yet many users miss its critical role until their software stops working.

Picture this: You install a Windows update, and suddenly your favorite app crashes on launch or refuses to open at all. The culprit? Often, it’s a missing or corrupted runtime component that developers rely on behind the scenes.

This runtime isn’t just another background service—it’s the bridge between your OS and the latest software.

Below, I’ll walk you through how to install, verify, and troubleshoot this runtime so your apps run smoothly—without the guesswork. No tech degree required.

How to install or reinstall Windows Desktop runtime 6.0.5 (x64) correctly

The Windows Desktop Runtime 6.0.5 (x64) is essential for running modern Universal Windows Platform (UWP) apps, Visual Studio projects, and .NET 6.0+ applications. If your system is missing this runtime, apps may crash or fail to launch entirely.

Here’s how to install or reinstall it correctly—without breaking existing dependencies.

Before proceeding, ensure you’re installing the x64 version (not ARM or x86) unless you’re on a 32-bit system. This runtime is required for apps like Microsoft Teams, Visual Studio 2022, and Windows Terminal. A clean install avoids conflicts with older runtimes.

Step-by-Step Installation Guide

  1. Download the Official Package

    Head to Microsoft’s official download page and save the WindowsDesktopRuntime.6.0.5.x64.exe file to your Downloads folder.

  2. Run the Installer as Administrator

    Right-click the downloaded file and select Run as administrator. This ensures the installer has full permissions to modify system files.

  3. Follow the On-Screen Prompts

    Click Next twice, then Install. The process takes under 2 minutes and requires no reboot unless prompted.

  4. Verify the Installation

    Open PowerShell as admin and run: Get-AppxPackage -Name WindowsDesktopRuntime to confirm the 6.0.5.5 version is listed.

  5. Repair Corrupted Files (If Needed)

    If apps still fail, run: DISM /Online /Cleanup-Image /RestoreHealth followed by: sfc /scannow to fix system file corruption.

For a clean reinstall, first uninstall the runtime via Settings > Apps > Installed Apps. This prevents conflicts with older versions. If you’re on Windows 11, the runtime may auto-install with updates—check Windows Update history to confirm.

Pro tip: If you’re using Visual Studio 2022, ensure the Desktop development with C++ workload is installed. This bundle includes the runtime automatically. For UWP apps, rebuild your project after installation to ensure compatibility.

Always download from Microsoft’s official sources to avoid malware-infected installers. Third-party sites often bundle adware or ransomware with runtime packages. Verify the installer’s SHA-256 hash matches Microsoft’s published checksum if security is a concern.

After installation, test with a known runtime-dependent app, like Windows Calculator (Store version). If it launches, your runtime is correctly installed. For troubleshooting, check Event Viewer > Windows Logs > Application for errors related to Microsoft.Windows.DesktopRuntime.

Remember: This runtime is not backward-compatible with older apps. If you’re running legacy software, consider using Windows Sandbox or a virtual machine with an older runtime version.

For enterprise environments, deploy the runtime via Group Policy or Microsoft Endpoint Manager to ensure consistency across devices. Script the installation using: msiexec /i WindowsDesktopRuntime.6.0.5.x64.msi /qn /norestart for silent deployment.

If you’re still facing issues, your system might need a Windows Update or a repair install. Use the Media Creation Tool to refresh your OS without losing data.

Common errors when missing Windows Desktop runtime 6.0.5 (x64) and how to fix them

Missing the Windows Desktop Runtime 6.0.5 (x64) often triggers cryptic errors like 0x80073D02 or 0x80073CF9 when launching apps built with modern .NET 6.0 or Visual Studio 2022.

These errors typically appear after Windows updates or when installing new software requiring this runtime. The good news? Most fixes are straightforward and don’t require advanced technical skills.

Before diving into solutions, verify whether your system actually lacks the runtime. Open Control Panel > Programs > Programs and Features, then check under Windows Features. If it’s missing, you’ll need to install it manually. For offline systems, Microsoft provides direct download links—more on that later.

⚠️ Critical Warning: Corrupted Runtime Files
If you see errors like 0x80073D02 or 0x80073CF9 after installing the runtime, your system may have corrupted registry entries or damaged system files. Skipping the SFC/DISM scan (below) risks persistent crashes. Always run these checks post-installation.

Start with the easiest fix: run a System File Checker (SFC) scan. Open Command Prompt as Administrator and type: sfc /scannow Let it complete (100% progress). If errors persist, proceed to DISM: DISM /Online /Cleanup-Image /RestoreHealth This repairs deeper system file corruption that SFC might miss.

If errors like 0x80073D02 remain, manually download the Windows Desktop Runtime 6.0.5 (x64) from Microsoft’s official site. Use this direct link for offline installs: Microsoft’s WDR 6.0.5 (x64) Download Save the file, then run it as Administrator. Reboot your system afterward.

For stubborn issues, check the Windows Registry for missing entries. Press Win + R, type regedit, and navigate to: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall Look for entries related to Windows Desktop Runtime 6.0.5. If missing, reinstall the runtime or restore from a backup.

As a last resort, enable Developer Mode in Windows Settings (Update & Security > For Developers). This ensures your system has all necessary UWP app dependencies, including runtime components. Reboot and test your apps again—this often resolves hidden compatibility gaps.

★★★★★4.9(12 reviews)
Categories Windows