VLC developers reportedly blame Microsoft Defender for quarantining plugin cache and causing 33-second MP3 playback delays on Windows 11

The core dispute is about attribution. Game developer Jonathan Blow publicized a 33-second delay when playing MP3 files in VLC and used it to criticize open-source software on Windows. VLC developers responded that the delay stems from a Microsoft Defender update on Windows 11 that quarantines VLC's plugin cache file, not from VLC itself. The VLC team called Blow's criticism disrespectful given that a Windows update caused the breakage.

VLC's architecture relies on a plugin cache to avoid scanning its entire plugin directory on every launch. The cache file, plugins.dat, stores metadata for codecs, demuxers, and I/O modules. When Microsoft Defender quarantines or blocks this file, VLC must process its full plugin system from scratch before playback starts, producing the reported delay. The VLC team states that reinstalling VLC or regenerating the cache resolves the immediate symptom.

Two workarounds are described. The first is regenerating the cache by running vlc-cache-gen.exe from the VLC installation folder or using the Start menu shortcut labeled "VLC media player - reset preferences and cache files," though this also wipes customized preferences. The second and more durable fix is adding the VLC installation folder as an exception in Microsoft Defender, which should prevent future quarantine of the cache file. Neither workaround addresses the underlying Defender behavior.

Corroboration is weak. Only one feed carries this story, and the publisher itself could not reproduce the issue on a fully updated Windows 11 machine. Two forum commenters also reported experiencing no delay. Microsoft has not commented. The VLC team's claim is stated as an allegation rather than a confirmed diagnosis, and the inability of multiple parties to replicate the problem leaves the root cause uncertain.

For engineers, the broader signal is that antivirus software can silently quarantine application cache files after an update, degrading performance without any visible error. Plugin-based or modular desktop applications that rely on cached metadata at startup are particularly exposed. Adding installation directories to Defender exclusion lists is a known mitigation, but it shifts the burden onto application users rather than addressing the detection logic that caused the false positive.