tinyMediaManager does not start from within the “Program Files” folder

First of all: tinyMediaManager is designed to be a portable application. This means that you can simply extract it to your preferred location (e.g. the users directory, or any other hard drive/network share). There is no need to install tinyMediaManager into C:\Program Files\.

If you still want to install tinyMediaManager to C:\Program Files\, you have to adopt permissions for this folder to run tinyMediaManager without Administrator (you should never run tinyMediaManager as Administrator - there is absolutely no need to do that):

Right click on the folder where you have installed tinyMediaManager (e.g. C:\Program Files\tinyMediaManager) and choose preferences. Go to the tab Security. In the list of all available users, choose Users (machine name\Users). In the area below the users list, activate all permissions.

tinyMediaManager.exe is reported to be a virus

The launcher from tinyMediaManager (tinyMediaManager.exe) is reported from several anti virus programs to be a virus. The launcher it self is written in Go and there is a FAQ from Go about this problem: https://golang.org/doc/faq#virus:

This is a common occurrence, especially on Windows machines, and is almost always a false positive. Commercial virus scanning programs are often confused by the structure of Go binaries, which they don’t see as often as those compiled from other languages.

In any case, if you believe the report is in error, please report a bug to the supplier of your virus scanner. Maybe in time virus scanners can learn to understand Go programs.

tinyMediaManager can’t connect to the internet via NTLM proxy

NTLM authentication does not work within tinyMediaManager. You can use something like CNTLM to connect to the internet.

The user interface of tinyMediaManager is corrupted

Try to create (or edit if it already exists) a file called launcher-extra.yml in the tinyMediaManager install directory and add the following line under the node jvmOpts:, so it looks like

jvmOpts:
- "-Dsun.java2d.nodraw=true"

and restart tinyMediaManager

v3: Try to create (or edit if it already exists) a file called extra.txt in the tinyMediaManager install directory and add the following line -Dsun.java2d.nodraw=true and restart tinyMediaManager

tinyMediaManager won’t start with Java Portable

Java Portable provides Java in a different way than the installed one. You may need to create a batch file (.bat) inside the tinyMediaManager folder with the following content (including the dot at the end!):

cd %~dp0
<path to PortableApps>\CommonFiles\Java\bin\javaw.exe -Djava.net.preferIPv4Stack=true -Dsilent=noupdate -Dfile.encoding=UTF-8 -jar getdown.jar .

replace <path to PortableApps> with the installation path of your PortableApps.

tinyMediaManager v4 ships its own Java, so this is not needed any more

tinyMediaManager does not respect UI scaling settings from the system

Every Java version/Operating System does handle high DPI/UI scaling differently, but you can force tinyMediaManager to pick up your preferred scaling factor:

  1. open (or create if it does not exist) the file launcher-extra.yml in the tinyMediaManager folder
  2. add (or modify) the following part in this file:
    jvmOpts:
    - "-Dsun.java2d.uiScale=2"
    

    where 2 is the scaling factor you want to use.

  3. relaunch tinyMediaManager

v3: Java 8: follow the steps from this thread.
Java 9+: either do the same as for Java 8 or create a file called extra.txt in the tinyMediaManager install directory and add the following line -Dsun.java2d.uiScale=2. Last but not least you could try to increase the font size in the general settings and restart tinyMediaManager

UI glitches with a remote desktop connection

If you use tinyMediaManager with a remote desktop connection software like RDP or VNC, Java can produce some weird glitches due a lack of 3D rendering with remote desktop connections.

  1. open (or create if it does not exist) the file launcher-extra.yml in the tinyMediaManager folder
  2. add (or modify) the following part in this file:
    jvmOpts:
    - "-Dsun.java2d.d3d=false"
    
  3. relaunch tinyMediaManager

v3: You can create (or edit if it already exists) a file called extra.txt in the tinyMediaManager install directory and add the following line -Dsun.java2d.d3d=false