Urgent.News

600+ sources. One page. See who else covered it.

Editions

Tech

Devs blame Windows for VLC media player bug that causes 33-second delay when playing MP3 files — creators allege Microsoft Defender blocking plugin cache is to blame

VLC developers say a Windows 11 issue involving Microsoft Defender can interfere with the media player's plugin cache and cause unusually long playback delays.

Devs blame Windows for VLC media player bug that causes 33-second delay when playing MP3 files — creators allege Microsoft Defender blocking plugin cache is to blame

The widely-used open-source media player VLC has encountered an unusual issue on Windows 11, causing it to take up to 33 seconds to start playing an MP3 file. This delay stems from a recent change in Windows, which Microsoft Defender seems to be blocking, quarantining the VLC plugins cache file. The VLC developers claim this bug is due to a Microsoft Defender issue introduced through a Windows 11 update, which makes VLC's plugin cache quarantined by Windows.

Reinstalling VLC or regeneration of the plugin cache can fix this, but it's an inconvenient workaround. The easiest fix is to reinstall VLC or regenerate the plugin cache, but this will remove any customized preferences. Alternatively, adding an exception for the VLC installation folder in Microsoft Defender can prevent the issue from recurring, though it's not an ideal solution.

Microsoft has yet to comment on the issue, leaving it unclear if a future Windows Defender update will address the underlying cause.

Written by urgent.news from Tom's Hardware's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

This story

This is one outlet's version. Read the fullest account.

Read the original at tomshardware.com →

More in Tech

Archi Semantic Core: Using Archi Models from TypeScript

How to read a .archimate file and work with its elements, relationships, and views from your own application. Archi stores its models in .archimate files.

  • Archi Semantic Core library enables working with Archi models using TypeScript.
  • Installation via npm package @cda/archi-semantic-core.

Five things that break when you move from Jest to Vitest

Vitest advertises a Jest-compatible API, and it delivers. describe , test , expect , toHaveBeenCalledWith — all identical.

  • Vitest's global scope differs from Jest's, requiring explicit opt-in through globals in config file.
  • Vitest's jest.mock hoisting behavior requires using vi.hoisted instead of Jest's jest.mock.

More from Saturday 15 August →