You're trying to start a Data Collector Set in Performance Monitor, and bam — error 0x80300070. The exact message says PLA_E_NO_MIN_DISK. It usually pops up when you've got less than 1 GB free on the drive where the log files are saved. I've seen this on Windows 10 Pro, Windows 11, and even Server 2019 when someone forgets to clean up old performance logs.
It's frustrating because the error doesn't tell you which drive is full, or how much space it actually needs. But don't worry — the fix is straightforward.
Why does this happen?
Data Collector Sets have a minimum disk space requirement built into them. By default, Windows needs at least 1 GB free on the drive where the log file goes. If you're below that, the collector refuses to start. It's a safety thing — helps prevent the system from crashing if logs fill up the drive completely.
Thing is, the error doesn't always point to the right drive. If your collector saves to C:\PerfLogs and C: is full, you get this error. But sometimes the collector is set to a different drive (like D: or E:) and that drive is the problem.
How to fix it
Here's the steps I've used hundreds of times in corporate environments. Skip the fancy tools — just do this:
- Open Performance Monitor. Type
perfmon.mscin the Run box (Win+R). - Find your Data Collector Set under Data Collector Sets → User Defined (or System if you're using a built-in one).
- Right-click the set and choose Properties.
- Go to the Directory tab. This shows where log files are saved. Copy that path — you'll need it.
- Check free space on that drive. Open File Explorer, right-click the drive, and pick Properties. If it's below 1 GB free, that's your culprit.
- Free up space: Delete old log files from that folder. Or move them to another drive. Or change the collector's path to a drive with more space.
- Restart the collector. Right-click it and choose Start.
If you changed the path, the new folder must already exist. Windows won't create it for you.
Still getting the error?
Two things to check:
- The temp folder is full. Data Collector Sets sometimes use
%TEMP%for temporary files. Runcleanmgr.exeto clear temp files on the system drive. - You're looking at the wrong drive. Some built-in collectors (like the System Performance set) save to a hidden folder. Check
C:\PerfLogseven if the collector says otherwise.
If you're on a server with multiple drives, the collector might be using a network path. In that case, free up space on the server where the share lives.
One more thing
I've seen this error on systems with 30 GB free on C: but the collector was pointed to a 200 MB partition on E:. Always check the actual path in the collector properties. The error message lies sometimes.
And if you're in a hurry? Just delete old .blg files from the log folder. That usually buys you enough space to start the collector again.