Microsoft has officially retired the legacy MSDT-based Windows Update troubleshooter, redirecting all users to the Get Help app for diagnosing and fixing update failures. The shift, which affects Windows 11 Home, Pro, Enterprise, and Education editions, aims to streamline the repair process but introduces new requirements, including a Microsoft account for certain diagnostics. For anyone accustomed to typing msdt.exe or downloading an Easy Fix package, the change marks the end of an era.

What actually changed with Windows Update troubleshooting

The Windows Update troubleshooter is no longer a standalone tool accessible through any legacy command or legacy troubleshooting cabinet. Instead, it now lives in the Get Help app—Microsoft’s current app-based support platform—and as a secondary entry point inside Windows 11 Settings. When you go to Settings > System > Troubleshoot > Other troubleshooters and select Run next to Windows Update, the system typically hands the process off to Get Help. The app then runs automated diagnostics, identifies issues, and presents remedies or additional instructions.

The old methods are dead. Microsoft has deprecated the Microsoft Support Diagnostic Tool (MSDT), which powered all inbox troubleshooters for years. Commands like msdt.exe /id WindowsUpdateDiagnostic or downloading a .diagcab file may still execute on some builds, but they are no longer the supported path, and Microsoft actively removes these tools from newer Windows versions. The same applies to any guide that mentions “Microsoft Easy Fix” or PowerShell’s Get-TroubleshootingPack—all are obsolete. The official, current route is Get Help, full stop.

What the shift means for you

For everyday Windows users, the change is mostly cosmetic. You still get a guided repair flow that checks for common issues: corrupted update files, stuck services, incorrect registry entries, and network configuration glitches. The difference is that you now launch it from an app rather than a control panel dialog. That app, however, may require you to sign in with a personal Microsoft account or a work/school account for some support features to work fully. Microsoft has not explicitly listed which diagnostics demand a login, but users have reported that basic update troubleshooting often proceeds without one. If you value your privacy, running the troubleshooter from Settings (which hands off to Get Help) might bypass some login prompts, but your mileage varies.

Power users and IT administrators face a more jarring transition. The command-line simplicity of MSDT is gone, and all troubleshooting now happens within the Get Help interface. That means you cannot script the troubleshooter or deploy it silently across multiple PCs unless you adopt organization-level management tools. Group Policy can control access to troubleshooting, as detailed in the policy “Troubleshooting: Allow users to access recommended troubleshooting for known problems” under Computer Configuration > System > Troubleshooting and Diagnostics > Microsoft Support Diagnostic Tool. Admins can set values like Off, Critical, Prompt, Notify, Silent, or Configurable, but the underlying troubleshooting logic still relies on Get Help. For managed devices, IT departments should test the new flow and decide whether to allow it or block it entirely in favor of their own update management solutions.

There’s also a loss of transparency for some. MSDT often displayed the specific fixes it applied in clear text; Get Help tends to summarize results as “made a change” or “found no issue,” and you have to dig deeper to understand what changed. That could frustrate advanced users who like to peek under the hood.

How we got here: the long goodbye to MSDT

Microsoft first announced the deprecation of MSDT in January 2023, with plans to retire the tool by 2025. The reason was twofold: security and consolidation. MSDT had been a vector for remote code execution attacks in the past, notably the 2022 “Follina” vulnerability. Moving troubleshooters into a modern app reduces attack surface. Second, Microsoft has been centralizing support experiences into the Get Help app, which also provides live chat, community links, and AI-assisted support.

Over the course of 2023 and 2024, various inbox troubleshooters were redirected to Get Help or simply removed. The Windows Update troubleshooter was among the last to make the jump for Windows 11. By July 2026, when the original reporting confirmed the current state, all officially supported paths pointed to Get Help. Windows 10, whose consumer support ended in October 2025, never fully adopted the new model, leaving a mix of legacy tools on older systems. But Windows 11 users are expected to adapt.

What to do now: running the troubleshooter and verifying the fix

If you face an update that refuses to download, install, or keeps failing with an error code, here’s the modern playbook.

Step 1: Perform quick checks before starting.
- Save work, close apps, connect to a stable network, and plug in a laptop. If you use a VPN, disconnect unless company policy requires it.
- Note the update’s KB number and any error code from Settings > Windows Update.
- If a restart is pending, restart now. Then try a normal update scan one more time—sometimes that’s all it takes.

Step 2: Launch the troubleshooter. There are two ways, both ending in Get Help.
- Via Get Help directly: Open Start, search for Get Help, open the app, type “windows update troubleshooter” in the search bar, and follow the prompts. If it asks to run diagnostics, select Yes.
- Via Settings: Right-click Start → Settings (or press Windows key + I), go to System > Troubleshoot > Other troubleshooters, find Windows Update under “Most frequent,” and select Run. This often opens Get Help anyway.

After the diagnostic finishes, read the result carefully. It may report that it fixed something or that it found nothing. Then restart your PC—use Restart, not Shut down, because a restart starts a fresh session and completes any pending update operations.

Step 3: Verify the repair. Go to Settings > Windows Update > Check for updates. If the update installs successfully and the error doesn’t reappear, you’re done. If the same update fails again, note the new error code (it might have changed) and run the troubleshooter a second time—often the first pass clears one obstacle, and a second pass reveals the next.

Troubleshooting the troubleshooter

Sometimes the help app itself needs help. If Get Help won’t open, crashes, or the search does nothing, repair the app:
1. Go to Settings > Apps > Installed apps.
2. Find Get Help, click the three-dot menu, and select Advanced options (if available).
3. Select Repair. Wait, then try again.
If repair fails or does nothing, use Reset instead, but be aware that resetting clears the app’s cached data. Should both options be missing—which happens on some builds or managed devices—use the Settings troubleshooter route or contact your IT department.

If the Windows Update entry is completely missing from Settings’ “Other troubleshooters,” check for pending updates by going to Settings > Windows Update > Check for updates, install any servicing stack or cumulative updates, restart, and look again. On managed PCs, your organization may have hidden the troubleshooter via policy; in that case, you have no choice but to call the help desk.

When the troubleshooter is not the answer

The Windows Update troubleshooter fixes only download, detection, and installation problems. It cannot resolve:
- Hardware compatibility blocks (PC doesn’t meet Windows 11 requirements).
- Safeguard holds placed by Microsoft for known issues.
- Errors caused by a specific incompatible driver or application—you’ll need to address those separately.
- Updates pushed through WSUS, Intune, or other enterprise management tools if the organization’s infrastructure is at fault.
- Post-installation bugs (the update installed but now something else is broken).

If after two full passes of the troubleshooter, a restart, and checks for free storage (at least a few GB), network connectivity, and external hardware (remove unnecessary USB devices, docks, etc.) the same update still fails, document the KB number, the exact error code from Windows Update, your Windows version (run winver to see the build number), and the Get Help diagnostic report. Use that information on Microsoft’s official support website or hand it to IT.

Outlook: a more app-centric support future

The migration of troubleshooters into Get Help is a sign of where Microsoft is headed. Expect more legacy tools to vanish, replaced by app-based diagnostics that tie into your Microsoft account and potentially feed telemetry back to Microsoft’s servers. For most users, the experience is simpler and more guided. For those uncomfortable with the app model, the loss of offline, no-login troubleshooters is a step backward. Either way, Windows Update problems aren’t going away, and knowing the new path is now essential maintenance knowledge.