Quick Guide: Installing and Using MediaInfo Plus on Windows, macOS, and Linux

Troubleshooting MediaInfo Plus: Common Issues and Fixes

1. Installation fails or installer won’t launch

• Possible causes: corrupted download, missing dependencies, insufficient permissions, antivirus blocking.
• Fixes:
  1. Re-download the installer from the official source and verify file size/checksum if available.
  2. Run installer as administrator (Windows) or with sudo (macOS/Linux).
  3. Temporarily disable antivirus or add an exclusion for the installer.
  4. Ensure required runtime libraries are installed (e.g., Visual C++ Redistributable on Windows).
  5. Check installer logs in the temp folder for specific errors.

2. Application crashes on startup

• Possible causes: incompatible system libraries, corrupted config, GPU/driver conflicts.
• Fixes:
  1. Update OS and graphics drivers.
  2. Start the app in safe or compatibility mode (if available).
  3. Rename or remove the user config folder to force defaults (location varies by OS; check app docs).
  4. Reinstall after completely removing previous installation and leftover folders.
  5. Check system Event Viewer / Console logs for crash details and share with support.

3. Media files not opening or metadata missing

• Possible causes: unsupported container/codec, file corruption, incomplete scanning settings.
• Fixes:
  1. Verify the file plays in a media player that supports the codec (e.g., VLC).
  2. Update MediaInfo Plus to latest version to get new format support.
  3. Use the “Scan full file” or equivalent option instead of quick scan.
  4. Test with other files to determine if issue is file-specific; re-download or repair corrupted files.
  5. Enable verbose logging and inspect output for parser errors.

4. Incorrect or inconsistent metadata displayed

• Possible causes: multiple embedded streams, faulty tags, sidecar metadata conflicts.
• Fixes:
  1. Inspect all streams and tag sections (container tags, codec tags, chapters).
  2. Use the raw or full tree view to see conflicting fields.
  3. Export metadata and compare with original file using ffprobe or mediainfo CLI.
  4. If sidecar files (e.g., .xml, .json) exist, temporarily remove them and re-open file.
  5. Update or patch metadata using dedicated tools (ffmpeg, AtomicParsley, MP4Box).

5. CLI version behaves differently from GUI

• Possible causes: different default options, environment PATH issues, older CLI binary.
• Fixes:
  1. Check version of both GUI and CLI (help/version flags) and update if mismatched.
  2. Compare command-line options and ensure flags match GUI settings.
  3. Run CLI with full paths to the binary and files to avoid PATH confusion.
  4. Use verbose or debug flags for the CLI to reveal processing steps.

6. Slow scanning or high CPU usage

• Possible causes: large files, deep scanning enabled, antivirus interference.
• Fixes:
  1. Use quick scan for routine checks; reserve deep scan for detailed analysis.
  2. Exclude large media folders from real-time antivirus scanning.
  3. Close other CPU-intensive apps and increase available RAM/swap.
  4. Update to latest build which may include performance improvements.

7. Export or report generation fails

• Possible causes: permission errors, unsupported export format, long file paths.
• Fixes:
  1. Export to a local folder with write permissions and a short path.
  2. Try alternative export formats (CSV, XML, JSON).
  3. Check for special characters in filenames and remove them.
  4. If exporting large batches, split into smaller groups.

8. Integration with other apps (PMS, DAM) not working

• Possible causes: API/auth mismatches, incorrect field mapping, network/firewall blocks.
• Fixes:
  1. Verify API credentials and endpoint URLs.
  2. Confirm field mapping and format expectations with the other app.
  3. Test connectivity (curl, ping) and check firewall logs.
  4. Enable request/response logging to inspect payloads.

When to contact support

• Collect: app version, OS version, sample file (if possible), logs or verbose output, exact steps to reproduce.
• Contact support with that package if fixes above fail.