Skip to main content

Media Server Troubleshooting

Media Server Won't Start

Check the installation:

Check Windows requirements:

  • Windows 10 or 11 (64-bit)
  • Visual C++ Redistributable installed
  • .NET 4.8 or later installed

Check for port conflicts: The server auto-assigns ports on first run. If another application is using the chosen ports, the server may fail to start. Delete app.config.json from Vu One_Data\StreamingAssets\Vu One\ and restart — it will pick new ports.

Black Screen on Startup

A blank or black screen usually means the system.config.json file is missing or corrupted.

  1. Press F12 to open the Operator Menu
  2. Navigate to System → Reset Config
  3. Restart the application

If the config file was blank (a known issue fixed in March 2026), this reset will regenerate it correctly.

Content Won't Play / Stuck on Splash Screen

  1. Confirm you're connected in Vū Studio (green indicator)
  2. Click any asset and try playing it — check if commands are reaching the server
  3. Check the Operator Menu (F12) for any error messages in the log viewer
  4. Try a remote restart from Vū Studio Settings
  5. If restart fails, manually close and reopen the Vū Media Server software on the Windows machine

Communication Bridge Issues

If the Vū Media Server software is running but remote control stops working, the internal communication bridge may need attention. The Vū Media Server software manages this component automatically — do not attempt to start or stop it manually.

  1. Press F12Send Logs to send diagnostic info to support
  2. Check Task Manager — if overall memory usage is very high, there may be a memory leak; contact support
  3. Try a remote restart from Vū Studio Settings, which will bring all components back up cleanly
  4. Make sure you don't have two instances of the Vū Media Server software open simultaneously

Dual Instance Warning

If you see a warning like "Second server instance detected. Shutting down to prevent conflicts" — the system detected two copies of the software trying to run. This is by design. Close all instances and relaunch once.

Getting More Help

Collect logs and contact support:

  1. Press F12Send Logs
  2. Note the time the issue occurred
  3. Email support@vustudio.com with your Wall ID, log timestamp, and description of the problem