A recent thread on X blamed VLC for slow MP3 playback, then turned out to be a Microsoft Defender bug. The whole argument is more useful as a debugging case study than as a platform fight, because the fix is short and the misdiagnosis is instructive.
If you have noticed VLC taking 5 to 30 seconds to open an MP3, the answer is almost certainly not “VLC is slow.” It is Microsoft Defender quarantining VLC’s plugin cache after a Windows 11 update. Adding VLC’s install folder to the Defender exclusion list makes the delay disappear.
What actually happened
Video game designer Jonathan Blow posted on X that VLC was taking 33 seconds to start playing an MP3 after a click. He switched to Microsoft Media Player and added that “a large sector of open source software is in a truly embarrassing place.” The post was clipped and amplified before anyone had checked the cause.
A community note was added to the original post once the diagnosis landed: the slow loading is caused by Microsoft Defender, not VLC. VideoLAN, the developers of VLC, replied directly. Per their public statement, “a bug from Microsoft Defender in one update of Windows 11” quarantined the VLC plugins cache, and reinstalling VLC or regenerating the plugin cache would fix it.
Blow also noted that he had recently had to fix a separate issue caused by an AMD graphics driver. The two incidents are unrelated. They are both examples of how fragile the audio/video pipeline is on Windows when an OS component decides to scan a directory it should leave alone.
Why Defender is the culprit
On Reddit, in a thread on r/pcmasterrace, several users identified the smoking gun. The proof is mechanical. Adding VLC’s install directory as an exclusion in Microsoft Defender fixes the slow loading. If the bug lived inside VLC, the exclusion would do nothing. Defender was scanning the directory on every MP3 open, and the scan was slow enough to feel like a hang.
The fix works because Defender treats the VLC plugin cache as suspicious content. Per Microsoft’s documentation, Defender has a default behavior of scanning any executable it finds on disk, and a Windows 11 update changed which directories got the more aggressive treatment. The plugin cache, which is rebuilt every time VLC opens and closes, is exactly the kind of file churn that triggers repeated Defender scans.
The exception fix (and why you should not have to use it)
You should not have to add a folder exception to your antivirus to play an MP3 in under a second. Today you do. The steps to fix it on Windows 11:
- Open Windows Security. Search for “Windows Security” from the Start menu.
- Select Virus threat protection. That is the shield icon in the left rail.
- Select Manage settings. Under “Virus threat protection settings.”
- Select Add or remove exclusions. It sits at the bottom of the page.
- Click Add an exclusion. Pick “Folder” from the dropdown.
- Navigate to C:\Program Files\VideoLAN. Click “Select Folder.”
After the exclusion is in place, an MP3 that took about five seconds to open in the source testing dropped to under one second. The same fix should hold across most Defender-influenced slowdowns: if a Windows update changed which directories Defender aggressively scans, the directories your media player uses are the ones that will start feeling slow first.
Who is responsible for fixing it
Both sides have a fair point, and the source piece from Windows Central captures both arguments well.
Microsoft’s side: Defender is doing what Defender is designed to do, which is scan executable code on disk. If a Windows 11 update changed the heuristic in a way that affected VLC, that is a Defender regression, and Microsoft should patch it. To their credit, this kind of regression is usually fixed in the next defender definition update.
VLC’s side: a media player that takes 30 seconds to open a file is broken from the user’s perspective. Even if the cause is upstream, the user experience has degraded, and that is the VideoLAN team’s problem to work around. They can detect the slow path, fall back to a faster path, or trigger Defender rescans on demand. None of those is trivial, but they are all on the table.
The right outcome is for Microsoft to fix the Defender regression, and the workaround exists in case Microsoft takes a while. Defender exclusions are a standard escape hatch, and the steps above are the same ones Microsoft documents for any performance-sensitive application.
What this kind of bug teaches
Three lessons are worth keeping for the next time a media app starts feeling slow on Windows.
Lesson one: identify which process is the bottleneck before blaming the visible app. When VLC takes 30 seconds, VLC is the surface symptom. The actual work is happening in Defender (or another background process). Tools like Process Monitor, Task Manager’s Details tab, and Resource Monitor show which process is holding the file handle or running the long scan.
Lesson two: the fix is often a configuration change, not a reinstall. Reinstalling VLC was VideoLAN’s first suggestion, and it works because the reinstall resets the plugin cache and triggers a fresh Defender scan. The cleaner fix is the exclusion, which leaves VLC alone and tells Defender to skip that directory.
Lesson three: vendor arguments are not the same as root cause. The X argument between Blow and VideoLAN was a sideshow. The actual cause was a Windows 11 update interacting with Defender’s default scanning. Neither side was wrong in spirit, but neither side had identified the bug at the start. The community notes and the Reddit thread did.
Trade-offs
Adding a Defender exclusion is not free. You are telling Microsoft Defender to skip virus scanning on C:\Program Files\VideoLAN, which is the directory where VLC, its plugins, and any helper executables live. For most users, the risk is small. VideoLAN ships signed binaries, and Defender’s default heuristics still cover the rest of the system. For users who install many plugins from third-party sources, the risk profile is higher, and the right move is to wait for Microsoft to patch the regression.
There is also a non-zero chance that the Windows 11 update is doing something Defender-specific that another antivirus would not replicate. If you are running a third-party antivirus suite (Norton, Bitdefender, ESET, and so on), the same symptom may not appear, and the same exclusion may not be the right fix. The diagnosis above is specific to Windows Defender.
Finally, this fix does not address the underlying Defender regression. If Microsoft pushes another Windows 11 update that changes the heuristic again, you may have to reapply the exclusion or wait for another Defender definition update. The exclusion is a workaround, not a permanent fix.
Bottom line
If VLC is suddenly slow to open MP3s, you are looking at a Defender regression, not a VLC regression. The fix is a Defender folder exclusion for C:\Program Files\VideoLAN, and the steps above take about 90 seconds. After the exclusion is in place, MP3 opens should be back to under one second.
Anyone who is debugging the same problem on a different media player should check the same directory. Defender can also slow down foobar2000, MusicBee, AIMP, and other apps that rebuild a cache directory under Program Files. The pattern is consistent.
The one thing worth remembering from the X argument: when a media app suddenly feels slow, check the background scanners before you blame the app.