User interface elements very small or missing


Items are very small or are missing from the user interface. Check boxes are the most likely object to not appear properly. This may only happen when logged into a remote desktop session.

Error Message



Display scaling is set to more than 100%. This issue is common on premium systems or tablets such as the Surface that have displays with high pixel density and non-standard scaling and resolution settings.

The application has limited support for scaling and displays best with scaling set to 100%, which is the default value on most computers. 


Option 1: Change Scaling 

Ensure that your computer's display scaling is set to 100%. 

  1. On the Start Menu, click the settings (gear) icon
  2. In Windows Settings, click System
  3. In the Change the size of text, apps, and other items list, click '100%'

If you are having this issue on a remote desktop connection, this resolution will not work unless you follow these steps carefully:

  1. Sign out from your remote desktop connection.  Simply "disconnecting" will not work.  You must find the Sign out option under the start menu or power options and choose that exact option.  This is  because the connection must be completely reset for the fix to work properly. 
  2. Adjust the scaling on your local machine.  As mentioned above, it should be set to 100%
  3. Reconnect to the remote desktop.  The change should take effect. 

Option 2: Let Windows Scale the Application

If you need to run with a higher scaling setting, you can also let Windows scale the application. Since this basically resizes the application like you would enlarge a picture in a photo editor, this will make the application look slightly blurry.

  1. Go to the folder where the application is installed. The default is 
    'C:\Program Files\Discovery Hub\Discovery Hub <version>'
  2. Right click 'timextender.exe' and click Properties
  3. (for Windows 10, click on "Compatibility" tab)
  4. Click Change high DPI settings 
  5. Select Override high DPI scaling behavior and click 'System (enhanced)' in the Scaling performed by list.


Was this article helpful?
0 out of 0 found this helpful


  • 1
    Jan De Dycker

    Sorry, but this isn't a viable solution.


    All other software does actually work using scaling, such as SSMS. This "fixes" the issue that TX isn't properly set up for scaling, but breaks all other software that, since half a decade, is.

  • 1
    Martin Dideriksen

    For me at least, it helps, when using the Remote Desktop App for windows 10 (download from Microsoft store).

    In this, you are able to set the resolution on the RDP session - Far from perfect, but it helps, while we are waiting for better scaling in TX.

  • 1
    Thomas Hjermitslev

    We are aware of the scaling issues and fixing them is in the backlog.

    I've updated the article with a second resolution option: Let Windows scale the application. This should enable Discovery Hub to play well with better-scaling applications at the expense of some UI fidelity in Discovery Hub.

  • 0
    Jan De Dycker

    Thanks Thomas and Martin.

    I've noticed that it's less of an issue on newer servers, but Win 2012 and older seem to struggle.

    At this time, we still see a lot of Win 2012 unfortunately.

  • 0
    Stuart Cuthbertson

    Just want to highlight Martin D's point - custom scaling per connection in Win10 Remote Desktop app has just saved me! 

     I normally work at a multimonitor setup and have never had problems with TX font size, but (thanks to a certain virus) am currently working on just my 15" laptop screen with native 1920x1080 resolution. I found that setting my remote desktop connection to our TX DH instance at 1280x720, with scaling at 100%, makes DH usable.

    As suggested by this article, at any resolution, increasing the scaling of the RDC to 125% or 150% made things worse. 1280x720 was also the highest resolution at which the result was usable for me, I tried multiple steps from 1920x1080 downwards first.

    To Jan's point, our TX machine is Server 2012 R2. (Yes, I know... :-( )

Please sign in to leave a comment.