PLA_E_DCS_START_WAIT_TIMEOUT 0x8030010A Fix

Quick answer for advanced users

Restart the Performance Logs & Alerts service from Services.msc, then delete the corrupt Data Collector Set in %SystemRoot%\System32\PerfLogs\ or using logman. Run winmgmt /resyncperf to re-register performance counters if needed.

Why this happens

I know this error is infuriating — it usually pops up when you're trying to run Performance Monitor or a custom Data Collector Set and Windows just sits there. Then you get PLA_E_DCS_START_WAIT_TIMEOUT (0x8030010A). The trigger is almost always a corrupt or orphaned Data Collector Set left behind by a previous failed run. I've seen it after Windows updates that bork performance counters, after aggressive antivirus scans that lock files, or when the Performance Logs & Alerts service crashes mid-collection. The real fix is cleaning up the mess and giving the service a fresh start.

Step-by-step fix

Restart the service
Open Services.msc (Win+R, type services.msc), find Performance Logs & Alerts. Right-click it, hit Stop, then Start. If it's already stopped, just start it. This clears any hung state.
Stop all related services
While you're there, also restart Windows Management Instrumentation (WMI) — but note: this will temporarily break anything relying on WMI, like some system monitoring tools. Do it during a maintenance window if you can.
Delete corrupt Data Collector Sets
Open an elevated Command Prompt (right-click, Run as administrator). Type:
```
logman stop <CollectorSetName> -ets
```
Replace <CollectorSetName> with the name of the set that's failing. If you don't know which one, run logman query to list all sets. Look for sets with a status of Stopped or Corrupted.
Clean up the physical files
Go to %SystemRoot%\System32\PerfLogs\ and delete any subfolders for the problematic collector set. Sometimes files get stuck with exclusive locks. If Windows says they're in use, boot into Safe Mode and delete them there.
Forcefully reset performance counters
Open an elevated Command Prompt and run:
```
winmgmt /resyncperf
```
This re-registers all performance counter DLLs with WMI. Wait 30 seconds, then try your Data Collector Set again.
Reboot
Yeah, it's cliché, but a full restart flushes the service's memory and clears any lingering handles.

Alternative fixes if the main one fails

Use PowerShell to nuke the set

If logman can't stop the set, use PowerShell:

Get-CounterSet -SetName "YourSetName" | Remove-CounterSet -Force

But be careful — this deletes the set entirely. You'll lose any custom configuration.

Rebuild the PerfLogs folder

If the PerfLogs folder itself is corrupt, delete it (yes, the whole thing), then create a new empty one. Then restart the Performance Logs & Alerts service. I've done this on Windows 10 21H2 and Server 2022 and it works.

Check permissions

This one's rare but happens. Make sure the Performance Log Users group has write access to %SystemRoot%\System32\PerfLogs\. Right-click the folder, Properties, Security tab, edit permissions. Add NT AUTHORITY\NETWORK SERVICE with Modify permissions.

Clean boot to rule out third-party interference

Boot with a minimal set of drivers and startup programs using msconfig. If the error goes away, some third-party driver or service is holding a lock on performance counter files. Common culprits: McAfee Endpoint Security, Dell SupportAssist, or any monitoring tool that uses WMI.

Prevention tip

Don't let Data Collector Sets run indefinitely. That's the #1 cause of this error. Set a stop condition in the collector's properties — use a schedule or a duration limit. Also, keep your Windows Performance Toolkit updated through the Windows SDK. I've seen stale binaries from old SDK versions cause this exact timeout. On Server 2019 and 2022, apply the latest cumulative update; Microsoft fixed a related bug in KB5014678.

Pro tip: If you're using custom Data Collector Sets for long-term monitoring, script a nightly restart of the Performance Logs & Alerts service using Task Scheduler. Keeps things clean.