Month: June 2016

How to fix scaling issues in SQL Server Management Studio on 4k or other high density displays.

Many thanks to SpaghettiDBA (Gianluca Sartori). He wrote about this on

Sadly enough Microsoft sees this as a non issue for us and won’t fix this issue. ( Many more High DPI displays will occur in the future.

In short how to fix this in four easy steps:

1) Create [SSMSDPISCALING.reg] file as per example below
2) Create [Ssms.exe.manifest] file as per example below
3) Double-click on [SSMSDPISCALING.reg] to enter a key into the registry
4) Copy [Ssms.exe.manifest] file to “C:\Program Files (x86)\Microsoft SQL Server\120\Tools\Binn\ManagementStudio” folder
    (Replace 120 by 130, 110, 105 or 100 if using another version of SSMS than SQL 2014)

I have tested this work around with SQL Server 2014 and SQL Server 2016 Management Studio Versions on Windows 10

Reg file [SSMSDPISCALING.reg] contains:
Windows Registry Editor Version 5.00


Manifest file [Ssms.exe.manifest] contains:
<?xml version=”1.0″ encoding=”UTF-8″ standalone=”yes”?>

<assembly xmlns=”urn:schemas-microsoft-com:asm.v1″ manifestVersion=”1.0″ xmlns:asmv3=”urn:schemas-microsoft-com:asm.v3″>

    <assemblyIdentity type=”win32″ name=”Microsoft.Windows.Common-Controls” version=”″ processorArchitecture=”*” publicKeyToken=”6595b64144ccf1df” language=”*”>

    <assemblyIdentity type=”win32″ name=”Microsoft.VC90.CRT” version=”9.0.21022.8″ processorArchitecture=”amd64″ publicKeyToken=”1fc8b3b9a1e18e3b”>

<trustInfo xmlns=”urn:schemas-microsoft-com:asm.v3″>
      <requestedExecutionLevel level=”asInvoker” uiAccess=”false”/>

  <asmv3:windowsSettings xmlns=””>
    <ms_windowsSettings:dpiAware xmlns:ms_windowsSettings=””>false</ms_windowsSettings:dpiAware>