Remote Troubleshooting a Broken Windows 11 PC in 2026: Modern Alternatives to DaRT

The Microsoft Desktop Optimization Pack, and with it DaRT (Diagnostics and Recovery Toolset), reached the end of extended support on 14 April 2026. If you’ve been keeping a DaRT 8 recovery image around for the odd unbootable machine, that image is now unsupported and increasingly useless: it was built for BIOS-era Windows 7/8 recovery scenarios and has no awareness of Entra ID, BitLocker with TPM, or cloud-managed fleets.

The good news is that Windows 11 and Intune now cover the same ground properly, and in most cases without anyone driving to site with a USB stick. This post covers the three tools that actually replace DaRT’s job in 2026: Quick Machine Recovery, Intune Remote Help, and Windows Autopilot Reset, plus which one to reach for depending on how badly the machine is broken.

What DaRT actually did, and what replaces it

DaRT’s value was booting a dead machine from external media into a mini Windows PE environment with a crash analyser, registry editor, file restore and remote viewer bolted on. That workflow assumed a technician physically present (or at least a working KVM) and a domain-joined PC. Neither assumption holds for a modern hybrid fleet.

Quick Machine Recovery: automatic repair from inside WinRE

QMR is the closest thing to what DaRT’s Crash Analyzer was trying to be, just automated and cloud-fed. When a Windows 11 device fails to boot repeatedly, it drops into WinRE, and if Cloud Remediation is enabled, it phones home over Ethernet or a supported Wi-Fi profile to check whether Microsoft has already published a fix for that specific failure (this is what shipped after the 2024 CrowdStrike outage forced the issue). If a remediation exists, it’s applied and the machine restarts on its own. No USB stick, no technician, no ticket.

Configure it centrally via the RemoteRemediation CSP, or through the Intune settings catalog:

# CSP path (Intune custom profile or settings catalog)
./Device/Vendor/MSFT/RemoteRemediation/CloudRemediationSettings

# Confirm WinRE is enabled locally (required for QMR to run at all)
reagentc /info
reagentc /enable

In the Intune settings catalog search for “Cloud Remediation” and “Remote Remediation” to find the toggles. You can also test the flow deliberately with reagentc /setrecoverytestmode on a lab machine before rolling it out fleet-wide.

Intune Remote Help: for machines that still boot

Remote Help is Microsoft’s supported replacement for third-party remote viewers on managed devices, and as of August 2026 it’s included with Microsoft 365/Intune E5 rather than needing a separate Intune Suite add-on for most scenarios. It runs two modes:

• Attended: the end user is signed in and approves the session from the taskbar. Good for “my app’s broken” tickets.
• Unattended remote sign-in: a helpdesk technician signs in with their own Entra credentials to a physical, corporate-owned, Intune-managed Windows device with nobody present. Useful for meeting-room PCs, kiosks, or a user who’s away from their desk.

The limitation that matters for DaRT-style scenarios: Remote Help needs a functioning, booted Windows session with network connectivity and the Intune management agent running. It’s not a recovery tool for a machine that’s stuck at a black screen or a BSOD loop. For that, you’re back to QMR or Autopilot Reset. Enable it under Intune admin centre, Tenant administration, Remote Help, and set unattended access permissions via RBAC before you need it, not during an incident.

Windows Autopilot Reset: wipe and re-provision remotely

When a device is so badly misconfigured that repair isn’t worth the time, Autopilot Reset removes user files, apps and settings while keeping the Entra ID join, Intune enrolment, Wi-Fi profiles and provisioning package intact. The machine comes back out the other side already business-ready, without a full re-image.

WinRE has to be enabled and healthy for this to work at all; if it’s been disabled or corrupted, Autopilot Reset fails with ERROR_NOT_SUPPORTED (0x80070032). Check it with reagentc /info before you rely on the feature, ideally as a standard build-time step. It also doesn’t cover Entra hybrid-joined devices or Surface Hub, which still need a full wipe and re-enrol.

Which tool for which failure

• Won’t boot at all, known widespread issue: let Quick Machine Recovery try first. It’s unattended and costs nothing to wait for.
• Boots fine but something’s broken (app, driver, user error): Intune Remote Help, attended or unattended.
• Misconfigured, malware-suspect, or “just start clean”: Autopilot Reset, remote if reachable, local if someone’s on site.
• None of the above works: you’re now doing a proper re-image, which is what DaRT would eventually have led to anyway.

Frequently asked questions

Can I still use my old DaRT 8 recovery disk?

It’ll technically still boot on legacy hardware, but it has no support, no updates, and doesn’t understand modern disk encryption or cloud identity. Treat it as retired rather than “still works if I need it.”

Does Quick Machine Recovery need a licence?

No, it’s a Windows 11 feature, not an Intune add-on. You do need Intune (or another MDM) to configure and enforce the Cloud Remediation settings centrally, and to see fleet-wide recovery status.

What if Remote Help and Autopilot Reset both fail because the device won’t enrol or authenticate?

That’s the scenario none of these tools cover, by design: they all depend on the device having a working, previously-established Entra ID and Intune relationship. If that’s broken, you’re into standard WinRE command-line repair (sfc /scannow, DISM, bootrec) or a re-image from installation media.