Update Keep crashing Plex

Plex Media Server
1

Server Version#: 1.43.3.10896-cb3ebc72d
Player Version#: Multiple clients; this is a server-side failure affecting Plex Web and local clients
Platform: Windows x64, Windows build 10.0.26200, Dell PowerEdge T440

Plex intermittently becomes unavailable and requires a manual restart. During failures, Plex Media Server.exe and TCP port 32400 may remain present, but /identity and /web/ become unresponsive or time out.

The main recurring log errors are:

  • com.plexapp.system: Couldn’t connect to plug-in, treating as dead
  • Exception caught while updating system agent list: Error parsing file
  • Timeout or error reading status line from plug-in pipe
  • Private handlers are no longer supported
  • Error decoding with simplejson, using demjson instead

Affected legacy agents included TVDB, Theme Music, MusicBrainz, Fanart.tv, and others. Fanart-TV.bundle was disabled reversibly, but the wider com.plexapp.system failure continued.

A ghost TCP 32400 listener also occurred after Plex was stopped. It was owned by a PID that no longer existed and required a Windows reboot to clear.

PMS was tested on:

  • 1.43.3.10896
  • 1.43.3.10861
  • 1.43.2.10687

The same com.plexapp.system failures appeared across versions. PMS also automatically updated itself back to 1.43.3.10896.

All optional legacy agent bundles were then renamed with a .disabled suffix. Framework.bundle, System.bundle, Scanners.bundle, Media-Flags.bundle, and WebClient.bundle were left active. The com.plexapp.system errors still occurred.

Database checks were run read-only using Plex SQLite while PMS was stopped:

  • com.plexapp.plugins.library.db: ok
  • com.plexapp.plugins.library.blobs.db: ok

No database repair, vacuum, reindex, or edits were performed. No persistent database corruption errors were found.

Does anyone have any idea…

  1. Why com.plexapp.system cannot answer local resourceHashes/system-agent requests.
  2. Whether there is a Windows regression in the legacy plug-in runtime or private-handler implementation.
  3. Whether the orphaned TCP 32400 listener is related.
  4. Whether the plug-in runtime failures can eventually hang the main PMS request handler.
  5. Whether Windows security software, VPN/network filtering, WSL networking, or injected DLLs are interfering with loopback plug-in communication.

Plex-Support-Logs-2026-09-07.zip (3.9 MB)

2

Your logs indicate PMS is crashing somewhere along the way. The errors you see are likely a side effect of the cash not the cause. Only Plex employees can see the crash so will need to wait if someone is able to look.