Because of the resolution compatibility problem, which causes Roon window to stretch below the taskbar, I have to update the application shortcut according to the following guide:
Every update changes the number after the last backslash. This doesn’t affect the application but resets the resolution settings done per the guide.
Attempt to set it again causes an error about the wrong path of “Start in:”, so I first need to find where Roon is now installed (the number), update the shortcut path and then fix the resolution setting. This annoyance is repeated after each update.
Thanks for writing in, it’s good to see you on the community again! This issue likely arises because Roon updates itself by creating a new folder for the updated version, resulting in the changing “Start in:” path. To work around this, you can create a fixed path shortcut that will dynamically point to the correct version of Roon regardless of updates.
Let’s see if the below steps help you:
Open a text editor (e.g., Notepad) and paste the following code:
@echo off
set roonPath=%localappdata%\Roon\Application
for /d %%i in ("%roonPath%\*") do set latestVersion=%%i
start "" "%latestVersion%\Roon.exe"
Save the file as LaunchRoon.bat
Right-click on the LaunchRoon.bat file and select Create Shortcut. Place this shortcut wherever you normally use the Roon shortcut (e.g., Desktop, Start Menu).
Use the Batch File Shortcut to Launch Roon. The batch file will always look for the latest version of Roon in the application directory and launch it automatically.
Thanks for the prompt reply. The shortcut of the batch file doesn’t have the “Compatibility” tab, where the screen issue is being taken care of per the guide.
Alternatively, can I modify the “Start in:” path to a one which is not deleted during the update? For instance:
Modify the Start filepath string to point to the correct application folder ( I think this will now be 200001490 for Production or 200001489 for Early Access) and Apply the change. Then you will be able to open the Compatibility tab.
This is a continuation of a closed topic. The original issue remained - A new update is installed in a new path so the shortcuts paths of “Start in” are broken. This by itself is not a problem, but apparently, they must be valid in order to resolve the DPI issue.
Now things got even worst, since none of the DPI issue solutions work anymore. PC Roon application always starts with ridiculously high resolution, which makes it useless. The only way to control Roon is using a smartphone, not the PC anymore, a huge downgrade.
Because of this, any previously configured compatibility settings (such as High DPI support) are reset. To avoid reapplying these settings manually after each update, we provide an automated solution.
What Does This Script Do?
It locates the latest version of Roon in the Application folder.
It applies the High DPI compatibility setting (~ HIGHDPIAWARE) via the Windows Registry.
The script can be set to run automatically at system startup or on a schedule using Windows Task Scheduler.
Why You Won’t See a Checkbox in the Shortcut Properties
The DPI setting is applied via the Windows Registry under the key:
This approach tells Windows to apply the DPI mode at runtime, but it does not update the graphical user interface in the shortcut properties.
In other words: even though the script works correctly, the DPI-related checkbox under the “Compatibility” tab will not appear checked.
This is expected behavior for registry-based configuration.
PowerShell Script to Apply DPI Settings
Here’s a PowerShell script that:
Identifies the latest version of Roon installed in the user’s AppData directory.
Applies the ~ HIGHDPIAWARE flag to ensure the application handles its own DPI scaling.
# Define the path to the Roon application directory
$localAppData = "$env:LOCALAPPDATA\Roon\Application"
$exeName = "Roon.exe"
# Retrieve the most recent version folder
$latestFolder = Get-ChildItem -Path $localAppData -Directory |
Sort-Object Name -Descending |
Select-Object -First 1
if ($latestFolder) {
$exePath = Join-Path $latestFolder.FullName $exeName
if (Test-Path $exePath) {
# Define the registry path for compatibility settings
$regPath = "HKCU:\Software\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers"
# Apply the High DPI awareness setting
Set-ItemProperty -Path $regPath -Name $exePath -Value "~ HIGHDPIAWARE"
Write-Host "High DPI settings applied to $exePath"
} else {
Write-Warning "Roon.exe not found in the latest folder."
}
} else {
Write-Warning "No Roon Application folder found."
}
Automating the Script Execution
To ensure the DPI settings persist after each Roon update:
Save the Script: Store the above script as Set-Roon-DPI.ps1 in a known directory, e.g., C:\Scripts\.
In both of them, the application path is already as you wrote. The ‘Start in’ path is the one I’m manually modifying after each software update, otherwise Properties → Compatibility → Change high DPI settings is not accessible.
Currently, the RoonServer shortcut Properties → Compatibility → Change high DPI settings has both items selected. However, in the Roon shortcut Properties → Compatibility → Change high DPI settings both items are greyed out. If I recall correctly, I was able to enable them in the past.
As a next step, we’ll want to see if performing a full reinstall may help you - before performing any of the below, be sure you have a fresh backup saved and available.
Go to Start > Settings > Apps > Installed apps.
Find Roon, click the three dots, and select Uninstall.
Follow the prompts to remove the application.
This step removes Roon’s database and settings to ensure a truly fresh install.
This will delete your Roon database (including playlists, play history, settings, etc). If you want to keep it, back up your Roon database first via Roon’s settings before proceeding.
Navigate to the following folders and delete them if they exist:
Press Win + R, type: %localappdata%
Delete the entire Roon, Roon Server and RAATServer folders.
Then restart your Machine, and download and install a fresh instance of Roon. Restore your saved backup and see if you’re able to keep your shortcut.