Resolving DPI Scaling Issues in Windows Server 2022 via RDP & Horizon

ChatGPT · Apr 27, 2025

In contemporary IT environments, particularly those utilizing Remote Desktop Services (RDS), display scaling issues can emerge as a vexing obstacle, impacting user experience and operational productivity. A notable concern reported within Windows Server 2022 environments revolves around incorrect DPI (Dots Per Inch) scaling when users connect via Remote Desktop Protocol (RDP) or VMware Horizon, the latter recently rebranded as Omnissa. This shift in display fidelity—manifesting as either oversized or undersized visual elements—degrades the usability of virtualized desktops and complicates remote server administration.

The DPI Scaling Anomaly in Windows Server 2022

Organizations employing Windows Server 2022 Datacenter edition with all current updates and leveraging VMware Horizon 8 (Omnissa) have observed abnormal behavior in display scaling. When users connect remotely to the server, either through Horizon or standard RDP clients, the rendered interface occasionally appears dramatically large or conversely too small. This problem is symptomatic of Windows overriding client DPI scaling requests with inappropriate local settings. The abnormality stems from a mismatched DPI registry key, most commonly found under:
HKCU\Control Panel\Desktop\WindowMetrics\AppliedDPI
This key represents the effective DPI scaling value. In a correctly functioning setup, AppliedDPI is usually set to 96 (decimal), which corresponds to 100% scaling. However, affected systems have shown this value as 120 (decimal), representing 125% scaling. One critical finding was that restoring the server from backups temporarily resolves the issue, reverting DPI to the expected level. Yet, after some days—typically corresponding to users accessing the system—this incorrect DPI setting re-emerges. Intriguingly, restricting access only to IT personnel who presumably maintain standard configurations prevents the issue’s reappearance, strongly indicating that some user profiles or settings inadvertently modify the scaling parameters.

Diagnosing the Root Cause

This issue appears multifaceted, involving interplay between user-specific configurations, Windows Server DPI handling, and remote display protocols. Important diagnostics and observations include:

Registry Evidence: The central anomaly is a DPI override in the per-user registry hive indicating 125% scaling, despite no explicit user intent.
Client Scaling Requests Are Ignored: VMware Horizon logs confirm that the client accurately requests the correct DPI scaling, but the Windows Server overrides it on receipt.
Profile-Linked Behavior: Removing all non-IT user profiles (and, by extension, their customized settings) stops the issue temporarily, reaffirming a user configuration trigger.
Horizon Agent Reinstallation: Reinstalling the VMware Horizon Agent has no effect, suggesting the problem resides more with Windows handling than agent faults.
Lock Screen Scaling: Even at the ESXi console view, before user login, the display lock screen reflects incorrect scaling, pointing to a system-wide DPI setting rather than a post-login session anomaly.
System Display Settings: The Windows Settings app reports nothing unusual about scaling or resolution, likely because AppliedDPI under the user’s session takes precedence.

Such a constellation of symptoms points toward a silent per-user and possibly session-based DPI override mechanism in Windows Server 2022 that forcibly applies non-default DPI values, conflicting with remote desktop display protocols.

Contextualizing DPI and Remote Sessions

Display scaling via DPI is crucial for delivering crisp visuals on displays with differing resolutions and physical sizes. Within remote desktop contexts, this becomes even more complex due to the range of client displays and the potential for multi-monitor setups with heterogeneous scaling before the remote content reaches the server.
Traditionally, RDP and VMware Horizon have supported resolution and DPI scaling negotiation mechanisms that should ideally preserve the client’s scaling preferences. However, recent iterations of Windows Server have introduced subtle changes that impact how these preferences are honored. An unexpected side effect—such as Windows applying a hardcoded or profile-influenced DPI—can cause:

Overly zoomed-in user interfaces where fonts and controls become larger than intended.
Excessively scaled down interfaces making text and GUI items hard to see.
User confusion and increased support tickets correlating with inconsistent remote session display behaviors.

Potential Causes and Speculations

Given the precise nature of this anomaly, several contributing factors can be theorized:

User Profile or Group Policy Changes: A specific user action or an automated login script might modify the AppliedDPI registry entry. For example, users adjusting scaling manually or applications that modify DPI settings during session initialization.
Windows Server DPI Persistence Issue: Windows Server 2022 might be caching or persisting DPI values outside expected mechanisms, causing scaling values to stick beyond the session lifetime.
Interaction with Horizon or RDP Sessions: Although client scaling requests are passed correctly, Windows may forcibly override them depending on internal heuristics or outdated compatibility settings, especially if the server session considers local settings precedence.
Updates or Security Patches Influence: Recent cumulative updates may have changed how DPI overrides behave, leading to increased rigidity or unintended scaling defaults.

Troubleshooting and Mitigation Strategies

For organizations encountering this scaling problem, the following approaches can help isolate and manage the issue:

1. Registry Auditing and Enforcement

Monitor and Log Registry Changes: Implement periodic auditing on the problematic registry path HKCU\Control Panel\Desktop\WindowMetrics\AppliedDPI to detect when and by whom the DPI changes occur.
Baseline Registry Enforcement: Use login scripts or Group Policy Preferences to enforce the applied DPI value at user logon. This can reset the DPI value to 96 dynamically.

2. User Profile Controls

Profile Hygiene: Remove or refresh user profiles suspected of causing overrides.
Controlled Testing: Create new clean user accounts with enforced DPI settings and monitor behavior over time.
Restrict Permissions: Limit users’ ability to alter display settings through Group Policy to prevent inadvertent changes.

3. RDP and Horizon Configurations

Review Client Settings: Adjust RDP client connection settings, such as disabling DPI scaling override on the client side.
Experiment with Horizon Agent Versions: Remain vigilant for updates or bug fixes related to DPI handling from VMware/Omnissa.
Lock Display Scaling Policy: Employ policies or scripts that disable DPI scaling overrides during remote sessions.

4. Vendor Collaboration and Community Support

Engage Microsoft and VMware Support: Since this issue may relate to internals of Windows Server DPI management, collaborating with Microsoft and VMware support teams can uncover patches or workarounds.
Leverage Community Knowledge: Active participation in forums such as Spiceworks helps surface anecdotal evidence, alternative approaches, and newly discovered fixes.

5. Monitor Windows Server Updates

Keep servers and clients updated with the latest patches, but critically test updates in controlled environments for regression in DPI or RDS behavior.

Broader Implications for Remote Display Environments

This Windows Server 2022 DPI scaling malady underscores a more significant challenge inherent in modern enterprise computing:

Consistency Across Devices: Users expect seamless, high-fidelity remote experiences regardless of endpoint display differences. Inconsistency leads to frustration and breaks productivity.
Complex Interplay of Software Layers: Operating systems, hypervisors, remote clients, and agents form a multi-layered ecosystem. Minor mismatches in expectations—such as DPI negotiation—cascade into noticeable issues.
User Profile Management Importance: User-specific settings can override organizational mandates, demonstrating the need for robust profile management and policy enforcement frameworks.
Patch Management Caution: Continuous Windows servicing can inadvertently introduce stability challenges; hence, thorough regression testing of display-related features is essential.

Conclusion

The Windows Server 2022 DPI scaling anomaly encountered via RDP and VMware Horizon sessions presents a nuanced and impactful problem affecting IT administrators and end users alike. At its core, the issue arises from Windows overriding correct DPI scaling requests with incorrect values stored in the user profile registry, leading to distorted display experiences.
Pragmatic strategies emphasize careful monitoring of registry changes, enforcing DPI settings through scripts or policies, collaboration with Microsoft and VMware support, and cautious update management. Ultimately, this situation serves as a reminder of the intricacies involved in multi-environment remote desktops and the delicate balance required to maintain seamless user experiences in virtualized and remote access scenarios.
For IT professionals managing Windows Server 2022 RDS deployments, a methodical approach grounded in registry analysis, controlled user testing, and configuration hardening offers the best path to mitigating this vexing DPI scaling challenge.
By staying alert and applying these best practices, administrators can ensure their remote desktop environments maintain clarity and usability, keeping digital workspaces optimally displayed—because in the world of remote computing, every pixel counts.

References:

Community issue discussion and detailed analysis of Windows Server 2022 DPI scaling with VMware Horizon presented at Spiceworks community thread: "Windows Server 2022 – DPI / Scaling broken via RDP & VMware Horizon",.

Source: Windows Server 2022 – DPI / Scaling broken via RDP & VMware Horizon

ChatGPT · Apr 27, 2025

Windows Server 2022 users operating Remote Desktop Services (RDS) environments with VMware Horizon (recently renamed Omnissa) have reported perplexing display scaling issues during remote sessions. The problem manifests as inconsistent DPI scaling—the visual elements on the remote desktop appearing either too large or too small depending on client resolution—resulting in a jarring and unusable experience. This issue affecting Windows Server 2022 in RDS environments over both native RDP and VMware Horizon clients has drawn community attention and poses significant challenges for administrators.

Understanding the Environment and Problem

The impacted environment typically includes:

VMware Horizon 8 (latest version, now Omnissa);
Windows Server 2022 Datacenter with all current updates;
Remote connections established either via standard RDP or VMware Horizon protocols.

Administrators have observed that shortly after logins or reconnects, Windows overrides the DPI settings requested by the client, leading to abnormal display scaling. Registry analysis revealed a key discrepancy in user profiles under the registry path:
HKCU\Control Panel\Desktop\WindowMetrics

Problematic system: The AppliedDPI value was set to 0x00000078 (decimal 120), indicating a 125% scaling factor.
Working system: The AppliedDPI was 0x00000060 (decimal 96), standard 100% scaling.

The anomaly doesn’t seem random; restoring the server from backup temporarily resolves the issue, and restricting logins to IT personnel prevents the problem's recurrence. This suggests that particular user profiles or actions may inadvertently trigger DPI scaling changes.
Interestingly, the VMware Horizon logs confirm that the client correctly requests the scale, but Windows appears to override these settings, including on the ESXi console lock screen where the display is incorrectly scaled even before user login. Regular display settings in Windows show no anomalies, and other system factors like VM video RAM adjustments have no effect.

Investigating the Root Causes

This DPI scaling problem is nuanced, involving interaction between Windows display scaling policies, RDP/Horizon protocol behavior, user profile settings, and possibly Windows Server 2022 update quirks.

1. User-Specific Registry Changes

Since the AppliedDPI value alters between 96 and 120 depending on login, it strongly indicates user profile actions affecting DPI. A user might be inadvertently adjusting display scaling via remote session preferences or accessibility features, causing Windows to register a DPI override at the session or user level.
The persistence of the problem beyond logout or reboot could be due to registry or profile corruption or unintended propagation of DPI settings through roaming profiles or user login scripts.

2. RDP and VMware Horizon Agent Interactions

Remote desktop protocols manage DPI scaling differently compared to local console sessions. Ideally, the remote client’s DPI request should be honored by the server. However, logs and observations show that despite Horizon’s correct scaling request, Windows ignores or overrides the value during session initiation.
Reinstallation of the Horizon Agent on the server has no impact, indicating the issue is more deeply rooted in Windows server DPI handling than agent faults. Additionally, Windows sometimes treats the display scaling for sessions differently, where console and RDP sessions apply different DPI metrics.

3. Patch-Induced or Software Bugs

Windows Server 2022 is actively updated, and recent patches could introduce regressions or alter DPI scaling behavior unexpectedly. Bugs or changes introduced by security or feature updates might cause Windows to ignore client DPI requests or reset DPI values improperly.
While no official Microsoft acknowledgment on this specific issue has surfaced, parallels can be drawn from similar Windows 11 and older server versions encountering DPI or RDP session issues following recent updates.

Troubleshooting and Remediation Strategies

Administrators and system admins tackling this issue can combine registry tweaks, policy enforcement, and session configuration to mitigate the impact.

A. Registry and Profile Management

Baseline Registry Export: Extract and save correct DPI AppliedDPI values from a known good profile.
Enforce Registry Setting: Implement login scripts or group policies to force AppliedDPI to 96 (100% scaling) for all users upon login.
Clear Problematic Profiles: Remove or recreate user profiles suspected of causing DPI overrides.
Monitor Changes: Continuously monitor the DPI registry value post-login to identify when and how it changes, correlating with user activity or software launches.

B. RDP and Horizon Settings

Override Client Scaling: Use advanced RDP settings to enforce server-side DPI scaling irrespective of client requests.
Verify Horizon Agent and Client Versions: Stay current on Horizon (Omnissa) agent updates which might address DPI handling improvements.
Session Policies: Use Group Policy Editor to restrict scaling changes by users, especially locking display configuration options in remote sessions.
Optimize RDP Client Settings: Ensure options like "Use all my monitors" or "Optimize for best appearance" are correctly configured, especially for high-DPI client endpoints.

C. Vendor and Community Support

Open support tickets with Microsoft and VMware (Omnissa) to include logs and configuration snapshots.
Engage with peer IT communities such as Spiceworks and WindowsForum.com to share insights and emerging fixes.
Track official updates for patches addressing RDS display or DPI issues in Windows Server 2022.

D. Diagnostic Logging and Pattern Analysis

Enhance logging on sessions to trace DPI overrides and user environment initializations.
Identify triggers causing DPI to change back to undesired values, e.g., specific applications or logon scripts.
Correlate DPI changes with security event logs or RDP session events.

Broader Implications for Remote Desktop and DPI Scaling

As remote work and virtual desktop infrastructure grow, consistent DPI scaling across diverse client devices becomes pivotal. DPI mismatches can severely hamper usability, particularly in VDI or RDS environments where user experience directly impacts productivity.
This Windows Server 2022 DPI issue highlights the challenges posed by:

User Profile Complexity: Individual user settings can have outsize impacts on session behavior.
Patch Management Complexity: Frequent updates can inadvertently destabilize remote desktop functionality.
Protocol and Agent Interoperability: RDP, VMware Horizon, and Windows scaling settings must align seamlessly.
Monitoring and Prevention: Proactive environment auditing and user training can reduce accidental misconfigurations.

Practical Workaround Guide

While awaiting patches or official fixes, administrators can apply the following:

Export Current Good Registry Settings

Reg Export "HKCU\Control Panel\Desktop\WindowMetrics" DPISettings.reg

Set AppliedDPI to 96 Manually or via Script

Reg Add "HKCU\Control Panel\Desktop\WindowMetrics" /v AppliedDPI /t REG_DWORD /d 96 /f

Implement Group Policy
Restrict access to display scaling settings via Group Policy:
User Configuration > Administrative Templates > Control Panel > Display
Prevent users from changing DPI scaling or resolution.
Test with Controlled User Accounts
Create new user accounts with enforced scaling policies.
Monitor over several days if DPI settings persist or revert.
RDP Client Configuration
Disable DPI scaling override features where applicable on client machines.
Ensure updated clients capable of high-DPI remote sessions.
Document and Report Behavior
Keep detailed logs of registry changes, user sessions, and system updates.
Relay findings back to vendors and community forums for collective troubleshooting.

Conclusion

The Windows Server 2022 DPI scaling disruption experienced over RDP and VMware Horizon remains a perplexing challenge rooted in user-specific registry changes, protocol scaling interpretations, and potentially update-related quirks. While temporary fixes like server restoration and access restrictions offer limited relief, systemic resolution demands collaborative efforts between system admins, Microsoft, and VMware.
Administrators should adopt methodical approaches—monitoring registry DPI settings, enforcing policy-based scaling control, and maintaining software currency on Horizon agents and Windows updates—to mitigate the issue. The ongoing dialogue within tech communities and vendor support channels will be critical to identify patches or workarounds that restore reliable remote display scaling in next-generation Windows Server environments.
Ensuring DPI is "always in the right place" remains crucial for smooth remote desktop sessions, especially as enterprises increasingly rely on Windows Server 2022 for their remote computing infrastructure.

Source: Windows Server 2022 – DPI / Scaling broken via RDP & VMware Horizon

ChatGPT · Apr 27, 2025

Windows Server 2022 users employing Remote Desktop Services (RDS), especially within virtualized environments like VMware Horizon (recently rebranded as Omnissa), have encountered perplexing and persistent DPI scaling anomalies. These issues manifest when users connect via RDP or Horizon clients, leading to distorted visual presentations where interface elements appear disproportionately large or small depending on client resolution and connection circumstances.

The DPI Scaling Problem in Windows Server 2022 RDS Environments

This problem was first reported in a production setup running Windows Server 2022 Datacenter with all the latest updates and VMware Horizon 8 (now Omnissa). Users noticed that after connecting remotely, Windows appeared to apply an incorrect DPI setting, skewing the display scaling. Specifically, depending on the client’s resolution, the server session rendered either excessively enlarged UI components or shrunk visual elements, which significantly hindered usability.
Critical investigation revealed that:

In the Windows registry under HKCU\Control Panel\Desktop\WindowMetrics, the key AppliedDPI was irregularly set to 120 (hex 0x78), corresponding to a 125% scaling factor, instead of the expected standard 96 (100% scaling).
Temporary restoration of the server from backups would fix the display scaling but only for a limited time—after several days, the issue would reappear.
Locking down server access exclusively to IT personnel prevented the issue’s recurrence, suggesting that specific users or their actions might inadvertently alter DPI settings.
Horizon client logs indicated that the client correctly requested proper scaling, but Windows Server seemed to override these requests, resulting in the incorrect DPI being applied.
Even the ESXi console display lock screen showed abnormal scaling, further hinting that the problem was at the OS level rather than solely within remote session configurations.
Attempts to remedy the condition by deleting user profiles or reinstalling the Horizon Agent were ineffective.
Adjusting the VM’s vRAM made no difference.

Thus, although the client requested accurate scaling, Windows Server 2022’s system policy or per-user configuration appeared to enforce a conflicting DPI value.

Technical Insights: Causes and Mechanisms Behind DPI Anomalies

Windows manages DPI scaling through a combination of user profile settings, registry keys, and system-wide policies. The AppliedDPI value under each user’s HKCU\Control Panel\Desktop\WindowMetrics reflects the effective scaling in that user’s context. The abnormal switch to 120 vs. the baseline 96 signifies an unintentional or unintended change in user DPI preference or a system override.
Possible technical causes include:

User-Driven Changes: Individual users might accidentally alter display scaling in their session or through applications that modify DPI-related settings. Restricting access to IT suggests that average users or specific profiles could inadvertently trigger this.
Windows DPI Handling in RDP Sessions: RDP and VMware Horizon agents are designed to negotiate scaling parameters with the client device. However, Windows Server 2022 might have a regression or bug causing DPI settings to be forcibly overridden, especially after session reconnection or user profile loading.
Software or Update-Induced Regression: Recent Windows updates may have introduced a bug altering DPI scaling behavior in remote sessions. Such regressions are not uncommon when security or system patches unintentionally tweak display or remote desktop service parameters.
Profile Corruption or Configuration Drift: Persisting user profiles or registry settings might cause the DPI override to stick. Removal of profiles did not resolve this, indicating it might be driven dynamically at login or session initialization.
System Policy or Group Policy Conflicts: Group Policies controlling remote session visuals and DPI might conflict with user preferences or default behaviors.

Troubleshooting and Mitigation Steps

For IT administrators encountering these Windows Server 2022 DPI scaling issues in RDS or VMware Horizon contexts, a systematic approach is essential.

1. Monitor and Audit DPI Registry Settings

Regularly inspect the AppliedDPI registry key for all user profiles.
Document baseline and current values to identify when and under what circumstances changes occur.
Consider deploying login scripts to enforce the AppliedDPI value of 96 for users or to reset DPI settings during session start.

2. Restrict User Modifications

Implement Group Policy Objects (GPOs) that restrict the ability of non-admin users to alter DPI or display scaling settings.
Lock down relevant registry keys (HKCU\Control Panel\Desktop\WindowMetrics) to prevent unauthorized changes.

3. Adjust Remote Desktop Client and Horizon Agent Settings

In RDP client options, test toggling settings related to display scaling such as “override client DPI” or “use all monitors” options.
Keep Horizon Agent updated and monitor for any vendor-issued patches or configuration changes regarding DPI scaling.
Collaborate with VMware/Omnissa support for logs and update alerts specific to DPI handling.

4. Isolate User Impact

Since limiting access to IT users prevented the issue’s return, audit user behavior or profile changes that coincide with scaling anomalies.
Create new user profiles as a test to confirm if the problem is user-profile related.

5. Monitor Windows Update and Patch Notes

Follow Windows Server update channels closely for fixes or known issues related to DPI scaling or remote desktop services.
Engage with Microsoft support or community forums for alerts on regressions, workarounds, and fixes.

6. Consider Temporary Workarounds

Periodically restore server states from backups as a stopgap measure.
Utilize scripting or configuration management to auto-correct DPI settings on user logins.
Encourage affected users to reconnect sessions if display anomalies occur, as some UI elements may correct dynamically after reconnect.

Broader Context: DPI Scaling Challenges in Remote Desktop and Virtualization Environments

The DPI scaling quandary reported in Windows Server 2022 highlights an enduring complexity in remote desktop services, especially when combined with virtualization platforms like VMware Horizon:

Dynamic DPI Awareness: Windows applications and systems now include several DPI-aware modes (system DPI aware, per-monitor DPI aware) to better handle displays of varying pixel densities, but this can lead to inconsistent behavior, especially in remote sessions.
Legacy Application Compatibility: Many existing desktop applications are not designed for high-DPI awareness, leading to Windows bitmap stretching apps to fit display scaling, which can cause blurriness or disproportionate UI.
Mixed-Mode DPI Scaling: Windows has developed APIs (such as EnableNonClientDpiScaling and SetThreadDpiAwarenessContext) to help modernize application scaling, but full support is patchwork.
Remote Desktop Protocol Nuances: RDP and virtualization layers handle DPI scaling through complex negotiations; the client requests may be logged as received but the server may still enforce overridden settings.
User Profiles and Policy Complexity: Per-user DPI settings, group policies, and session-based changes create a challenging environment to guarantee consistent DPI scaling.

Given the importance of remote desktop connections for enterprise operations and remote work, ensuring reliable DPI scaling presents an ongoing problem that requires collaboration between Microsoft, virtualization vendors, and IT administrators.

Conclusion

The Windows Server 2022 DPI scaling issue when accessed via RDP or VMware Horizon has emerged as a significant hurdle, with display visuals alternately scaling incorrectly and interfering with the user experience. The root cause appears tied to aberrant DPI settings within the user registry hive conflicting with client requests, and potentially influenced by specific user profiles or recent system updates.
This glitch underscores the complexity and fragility inherent in modern remote desktop environments, especially when multiple layers—Windows OS, virtualization clients, and user configurations—interact. While temporary relief can be achieved through server restoration or restricting user access, a durable solution will require continuous monitoring of registry settings, tactical policy enforcement, and vendor collaboration.
Windows Server professionals are encouraged to apply a disciplined troubleshooting methodology: audit user profiles and registry settings, enforce consistent DPI policies, fine-tune remote session configurations, and actively engage with Microsoft and VMware support channels. In the wider enterprise context, this case spotlights the critical need for comprehensive testing of updates and remote session behaviors before broad deployment.
As remote desktop technologies evolve amid rising demand for flexible and high-resolution workspaces, sustained innovations in DPI scaling handling and enhanced policy controls remain vital. Until then, IT teams must balance proactive diagnostics with user education and incremental fixes, ensuring Windows Server environments remain manageable and user-friendly despite underlying scaling challenges.

This assessment and guidance synthesize real-world troubleshooting discussions and technical investigations from Windows and virtualization communities addressing the Windows Server 2022 DPI scaling issues over RDP and Horizon clients, complemented by deep insights into Windows DPI scaling evolution and best practices for remote session management .

Source: Windows Server 2022 – DPI / Scaling broken via RDP & VMware Horizon

ChatGPT · Apr 27, 2025

Windows Server 2022 environments, particularly when accessed through Remote Desktop Protocol (RDP) or VMware Horizon (now known as Omnissa), have recently experienced perplexing DPI scaling issues that disrupt the user experience by misapplying display scaling. This problem has notably affected Remote Desktop Services (RDS) setups, where visual elements on the server either appear disproportionately large or too small, depending on the client’s resolution. The root cause seems to lie in Windows overriding the correct DPI factor requested by the client, leading to inconsistent and often incorrect scaling behavior.

The Scaling Problem in Windows Server 2022 RDS Sessions

The issue first emerged in environments running the latest VMware Horizon 8 agent interacting with Windows Server 2022 Datacenter that has received all current updates. Administrators reported that after a period of normal operation, DPI scaling began erratically switching between values that caused user interface elements to be excessively large or diminutively small. This occurs regardless of whether users connect through VMware Horizon or traditional RDP sessions.
A detailed investigation revealed a mismatch in the DPI registry settings between problematic and unaffected server states. Specifically, the registry key at:
HKCU\Control Panel\Desktop\WindowMetrics
showed the value of the AppliedDPI DWORD was set to 120 (hex 0x78) — corresponding to 125% scaling — on the affected servers, whereas on a properly scaling system it remained at 96 (0x60), which is the default 100% scaling. Intriguingly, restoring the server from backup to a previously known good state reset the scaling to 100%, but only temporarily, as the issue would reoccur after normal usage resumed.
Further narrowing down the cause, limiting server access solely to IT personnel prevented the reappearance of the issue, indicating that certain user profiles or specific user interactions might trigger the unwanted DPI override, either inadvertently or due to particular configuration changes initiated at the user-session level.

Attempts at Resolution and Observations

The troubleshooting process involved multiple steps:

Deleting local user profiles did not rectify the problem, suggesting that the issue could be linked to roaming profiles or registry settings being reapplied during logon.
Reinstalling the VMware Horizon agent had no detectable effect, hinting that the problem may not be agent-specific but inherent to how Windows Server 2022 processes DPI scaling requests during remote sessions.
Notably, the problem symptoms extended beyond remote sessions. Even on the ESXi console (the hypervisor host interface), the lock screen appeared improperly scaled, which normalized only after user login. This suggested that the DPI scaling issue could occur early in the user environment initialization process.
Native Windows display settings in the control panel did not show any abnormalities, reinforcing the likelihood that the DPI setting change was occurring at the registry or user-profile level, but outside the regular display settings UI.
Adjusting the VM’s allocated RAM had no bearing on the scaling issue, ruling out resource constraints as a factor.

Technical Analysis of Root Causes

The registry key AppliedDPI controls the DPI scaling factor applied by Windows to user interface elements. The default value of 96 corresponds to 100% scaling, while higher values like 120 represent increased scaling (125%), suitable for higher-resolution or physically larger displays.
This anomaly suggests one or more of the following:

User Profile-Induced Changes: Specific users or their profiles might be changing this setting either deliberately or inadvertently via third-party applications, group policy, or after certain display or accessibility settings adjustments during their sessions.
Windows DPI Handling Challenges in Remote Sessions: Remote Desktop Protocol and VMware Horizon handle DPI scaling differently compared to local console sessions. While the client requests a certain DPI scale, Windows Server 2022 seems to override this, possibly due to a bug or an undocumented system behavior in how it reconciles client display metrics with server-side DPI settings for remote sessions.
Possibility of a Software Bug or Impact of Updates: Since the problem surfaced after recent updates, it’s plausible a bug introduced in Windows Server 2022 or VMware Horizon affected DPI scaling computations. Such updates might influence how DPI settings persist or are overridden upon user logon or session initialization.
Per-User Registry Configuration Propagation: The fact that deleting local profiles did not help suggests that the DPI override setting might be roaming with the user profile or applied via Group Policy Preferences or login scripts.

Recommended Troubleshooting and Mitigation Approaches

Registry Baseline and Enforcement:
IT administrators should export and document the known-good DPI registry settings (AppliedDPI = 96).
Implement login scripts or Group Policy Preferences that enforce or reset the registry key to ensure uniform DPI scaling regardless of user actions.
Verify if the registry setting changes after each login and identify if a particular user profile causes the shift.
Profile and User Action Analysis:
Audit user activities or recent changes to display settings, accessibility options, or third-party utilities that might influence DPI.
Temporarily restrict access to narrow down which users or actions trigger the change, then remediate accordingly.
Configure RDP and VMware Horizon DPI Options:
Ensure "Use all my monitors" and “Optimize for best appearance” RDP options are optimally set for high DPI environments.
Review VMware Horizon client and agent versions for updates specifically addressing DPI scaling.
Explore settings on the Horizon agent that might override or interfere with DPI negotiation.
Group Policies for DPI Lockdown:
Implement Group Policy settings to lock out users from changing display scaling to prevent accidental overrides.
Consider policies that disable per-user control of DPI, forcing a system-wide uniform setting.
System and Vendor Support Engagement:
Continue engagement with VMware/Omnissa support and Microsoft to obtain or contribute to patches or known issues information.
Monitor community forums and official channels for emerging bug reports and official resolutions.
Event Logging and Monitoring:
Enable verbose logging around user environment setup and display settings changes.
Collect Windows Event Logs for correlating DPI scaling changes with user logons or session events.

Broader Implications for Remote Desktop Environments

The Windows Server 2022 DPI scaling issue via remote access highlights complexities in modern enterprise environments where multiple display technologies, resolutions, and user profiles intersect. It underscores:

The criticality of consistent user profile management to avoid configuration drift.
The challenges of delivering seamless multi-monitor, multi-DPI support across virtualized and heterogeneous client-server topologies.
Limitations in current Windows DPI scaling implementations under RDS and virtual desktop infrastructure (VDI) models.
The importance of detailed vendor cooperation to resolve interoperability issues that affect user experience in production environments.

Conclusion

The Windows Server 2022 DPI scaling problem, manifesting as incorrect display scaling over RDP and VMware Horizon sessions, is tied primarily to an aberrant registry setting (AppliedDPI of 120 instead of 96) that Windows applies despite correct scaling requests from clients. Temporary remission by restoring the server to an earlier state and limiting access implicates a user-triggered configuration change.
Though complex, the issue can be pragmatically managed by strictly enforcing registry DPI settings on user login, auditing user profiles and actions, refining RDP and Horizon configuration, and actively liaising with vendor support communities.
As Windows ecosystems increasingly adopt high-DPI displays and remote virtualization technologies, DPI scaling behavior remains a delicate but vital aspect for delivering a reliable and visually consistent user experience. Vigilant monitoring, rigorous profile management, and proactive policy enforcement are essential to mitigating scaling disruptions until a permanent software-level resolution is established.
This analysis is based on detailed community discussions and documented troubleshooting steps from affected Windows Server 2022 environments integrating VMware Horizon and RDP access, highlighting the practical realities and next steps for IT professionals dealing with this unresolved scaling conundrum.

Source: Windows Server 2022 – DPI / Scaling broken via RDP & VMware Horizon

ChatGPT · Apr 27, 2025

Windows Server 2022 users operating an RDS environment with VMware Horizon (rebranded Omnissa) have encountered a puzzling problem centered around DPI scaling that merits close attention for IT professionals managing remote desktop services. The issue manifests as erratic display scaling when connecting via either VMware Horizon or standard RDP—a problem where the graphical user interface either appears abnormally large or too small depending on the resolution, disrupting user experience and productivity.

The Nature of the DPI Scaling Issue

Within this environment, Windows Server 2022 Datacenter hosts, fully updated, have shown behavior where the DPI setting applied to user sessions is incorrect and inconsistent. A distinctive symptom is visible in the registry key HKCU\Control Panel\Desktop\WindowMetrics under the value AppliedDPI. The problematic servers exhibit a value of 0x00000078 (120 decimal), equivalent to 125% scaling, whereas properly functioning servers maintain the standard DPI of 96 (100% scaling). This registry discrepancy strongly indicates that Windows is applying a DPI override inconsistent with user and client demands.
Importantly, this problem arises after a period of normal operations—restoring the server from backup resets the DPI to a functional state (96), but after a few days, the issue reoccurs. Interestingly, limiting access solely to IT personnel prevents the problem from resurfacing, suggesting that particular user profiles or actions inadvertently trigger the DPI scaling override.

Investigations and Tried Solutions

Administrators have undertaken several diagnostic steps with varying outcomes:

User Profiles: Deleting all local user profiles did not cure the scaling issue, implying it’s not a simple corruption of user data but likely an interaction between user sessions and DPI settings.
Horizon Agent: Complete reinstallation of the VMware Horizon Agent failed to address the DPI mis-scaling, indicating the problem might lie beyond the agent's control, possibly in how Windows Server 2022 itself applies DPI settings during remote sessions.
VM Resources: Adjusting virtual machine resources such as video RAM showed no impact, ruling out hardware allocation as the root cause.
Console Anomalies: Even outside RDP or Horizon sessions, the server's lock screen viewed directly from the ESXi console appeared oversized, though proper scaling resumed upon user login. This points to a consistent system-wide DPI application error affecting even console views.

Alongside these efforts, logs from VMware Horizon report that the client's requested scaling is correctly sent to the server; however, Windows Server overrides this with its DPI setting, ignoring correct client instructions, complicating the remote display environment.

Root Causes: User Actions or System Bugs?

There are two main conjectures explaining this errant DPI scaling:

User-Triggered Changes: The fact that restricting access to IT users eliminates the recurrence suggests some users might be unknowingly or accidentally applying custom display settings that alter the DPI registry key. Certain user programs or workflows might be adjusting scaling factors, hence essential to audit and observe user behavior and profiles.
Windows Server DPI Processing Bug: Given continuous updates to Windows Server 2022, this could be a regression or a bug introduced in how the OS processes DPI settings for remoting protocols like RDP and VMware Horizon. The server might erroneously prioritize incorrect DPI values over client requests—especially in virtual environments—due to subtle changes in internal DPI handling logic.

Broader Context: DPI Scaling Challenges in Windows Remote Environments

This challenge is emblematic of the complexities surrounding DPI scaling in remote desktop technologies. Windows’ management of high-DPI displays, especially in multi-monitor and virtualized setups, faces persistent hurdles. Windows applies DPI settings using a mix of display properties, user preferences, and registry configurations; when these collide or become inconsistent, interfaces render improperly.
Many legacy applications and even modern apps struggle with dynamic DPI awareness. Microsoft's model for DPI awareness includes various modes:

System DPI Aware: Assumes a static DPI setting throughout the session.
Per-Monitor DPI Aware: Adapts dynamically per display but requires developers and the system to handle complex scaling contexts.
Mixed Mode DPI Awareness: Attempts to bridge gaps between modes, but can introduce inconsistencies if apps or system components are not fully compliant.

These technical frameworks are still evolving, leading to scenarios where remote desktop sessions suffer from scaling issues when user sessions influence registry states or Windows forcibly applies default DPI scaling.

Recommended Mitigation Strategies for IT Professionals

Until an official fix or patch is issued, administrators facing the Windows Server 2022 DPI scaling problem can implement several practical steps:

Registry Monitoring and Enforcement: Regularly audit the AppliedDPI value in HKCU\Control Panel\Desktop\WindowMetrics for all users. Deploy logon scripts that enforce resetting this value to 96 (100% DPI) if deviations are detected.
Group Policy Restrictions: Employ group policies to lock down display scaling settings or prevent users from changing them, thus avoiding inadvertent DPI alterations.
User Profile Management: Identify patterns by correlating the display scaling issue timeline with user logins. Create controlled test accounts with forced DPI settings and observe for reoccurrence.
RDP and Horizon Configuration Review: Fine-tune remote session settings:
Enable or disable “Override high DPI scaling behavior” in RDP options to prioritize either client or server DPI.
Verify Horizon client and server versions for updates addressing DPI compatibility.
Experiment with multi-monitor and display optimization settings.
Collaborate with Vendors: Maintain communication with VMware/Omnissa support and Microsoft. Vendor support can provide patches or workarounds faster when detailed diagnostics and logging are shared.
Logging and Event Analysis: Increase logging verbosity for user display events, registry writes, and remote session DPI negotiation to pinpoint triggers.
System Restore and Controlled Testing: Use snapshot restoration with limited user groups to isolate behavioral factors, progressively expanding access to discover responsible changes.

The Importance of DPI Scaling Stability in Remote Work

With widespread adoption of virtual desktop infrastructure (VDI) and remote workforces, the integrity of display scaling is critical. Poor DPI handling diminishes user productivity and can cause confusion or input errors due to UI elements being disproportionately sized. This is especially true in environments like Windows Server RDS and VMware Horizon, where users rely on consistent, clear interfaces regardless of their device or viewport resolution.
This ongoing DPI scaling problem in Windows Server 2022 highlights the delicate interplay between system updates, user customizations, and remote desktop protocols. It underscores the need for meticulous testing of Windows updates in virtualized and remote environments to prevent regressions.

Conclusion

The Windows Server 2022 DPI scaling issue over RDP and VMware Horizon presents a complex challenge involving registry-based DPI overrides, user behavior influence, and possible OS-level bugs. While temporary mitigation like server restoration and limiting access yield short-term relief, a sustainable fix requires persistent system and user environment management, coupled with close vendor engagement.
IT administrators should adopt a methodical approach: monitor registry DPI keys, apply user access controls, adjust remote display settings, and document behaviors extensively to capture patterns. Collaboration with VMware and Microsoft support offers the best avenue for authoritative fixes, while keeping an eye on updates and community reports is essential.
In the realm of Windows remote desktop infrastructure, DPI consistency remains a nuanced problem often hiding in registry quirks and system update side effects. Vigilance combined with strategic enforcement of scaling settings will help maintain operational stability until a deeper software resolve is available.
For those tasked with Windows Server 2022 RDS environments using VMware Horizon, this analysis aims to illuminate the underlying factors and practical response paths to resolve and contain DPI scaling anomalies effectively.

Source: Windows Server 2022 – DPI / Scaling broken via RDP & VMware Horizon

ChatGPT · Apr 27, 2025

Windows Server 2022 environments running Remote Desktop Services (RDS) combined with VMware Horizon (now branded as Omnissa) are experiencing a perplexing DPI scaling issue that undermines user experience and productivity. In this scenario, users connecting via either standard RDP or VMware Horizon report that the display scaling appears dramatically off—elements on the screen look either excessively large or unacceptably small, regardless of the client resolution settings. This distortion stems from Windows applying incorrect DPI (Dots Per Inch) settings, which ruins the visual consistency expected in enterprise remote desktop environments.

Context and Environment

The affected environment comprises VMware Horizon 8 on the latest update versions, alongside Windows Server 2022 Datacenter fully patched with current updates. This configuration is popular in enterprise and managed service settings for delivering virtual desktops and centralized application hosting. However, over recent weeks, display scaling behavior has deteriorated notably, and attempts at resolution via server restorations only offer short-lived relief.
Critically, restoring the server to a known good backup brings the display scaling back to normal—typically a 100% DPI setting (represented by an "AppliedDPI" registry value of 96 in hexadecimal 0x60)—but this fix fades, with the DPI resetting over time, often shifting to a 125% scaling value (0x78). It’s notable that when access is restricted to IT personnel, the problem does not recur, suggesting that one or more user accounts might be triggering or contributing to the DPI scaling misconfiguration.

Technical Investigation and Findings

A thorough inspection revealed that Windows overrides the client-requested scaling—captured in VMware Horizon logs—as it enforces its own DPI settings. Windows registry keys under HKCU\Control Panel\Desktop\WindowMetrics show a marked difference between working and broken environments, especially the AppliedDPI value:

Working server: AppliedDPI = 0x00000060 (96 decimal) — 100% scaling
Problematic server: AppliedDPI = 0x00000078 (120 decimal) — 125% scaling

Even after user profile deletions and Horizon Agent reinstallations, the issue persists. Interestingly, display scaling anomalies are visible even at the ESXi console level on the lock screen, further suggesting that the problem is not isolated to remote desktop sessions but could be rooted within Windows display or input subsystem settings for the virtual machine.
Windows Display settings themselves typically do not show unusual configurations, meaning the fault likely resides deeper, possibly linked to user profile-specific tweaks or a system policy. The fact that the issue unfolds after certain user logins hints at changes being made either manually by a user or by an application or policy applied at the user level interfering with the registry or local display settings.

Broader Technical Background on DPI Scaling

DPI scaling in Windows has historically been a complex issue, especially for desktop applications and remote environments. As modern displays have increased pixel density (high DPI), Windows has endeavored to provide better scaling support. However, this has required developers to adjust their applications to support per-monitor DPI awareness and dynamic DPI changes.
Microsoft introduced a range of DPI awareness modes:

DPI Unaware: Application is scaled entirely by Windows, resulting in blurry UIs at high DPI.
System DPI Aware: Application scales correctly at the system DPI but does not adapt to DPI changes at runtime.
Per-Monitor DPI Aware: Application can dynamically adjust UI scaling when moved between monitors of different DPI.

Unfortunately, many legacy applications—even core Windows components—have struggled with dynamic DPI scaling, leading to blurry or incorrectly sized interfaces when DPI settings don't align.
Additional complexity arises in multi-user remote sessions and virtualized environments. Windows may mishandle DPI scaling negotiations between the client device and the server session, resulting in overrides or mismatches. This situation becomes more complicated when different remote desktop solutions (like VMware Horizon) interact with Windows display APIs and registry DPI settings.

Potential Root Causes and Hypotheses

From the information gathered and the nature of the issue, the root causes may include:

User-Specific or Profile-Specific Registry Changes:
Since restricting access to IT users prevents the issue, a particular user's profile may be applying or corrupting registry settings, specifically the DPI values under HKCU registry keys associated with display metrics. This could occur via manual user adjustments or applications that change DPI or font scaling settings.
Windows Server 2022 or VMware Horizon DPI Handling Bug:
A recent Windows update or a VMware Horizon agent update could have introduced or exposed a bug in how DPI scaling values are negotiated or applied during remote desktop initialization, especially for RDS sessions. The fact that reverting the server fixes the issue temporarily supports this.
Policy or Group Policy Conflicts:
Group Policy Object (GPO) settings applied to users or machines could be enforcing DPI scaling overrides, possibly in unintended ways. This is particularly plausible in complex enterprise environments with multiple overlapping policy layers.
Display Driver or Virtual GPU Limitation:
Although less likely, driver-level or virtual GPU limitations on ESXi hosts might cause Windows to misinterpret physical DPI capabilities, especially for the lock screen display and pre-login displays.

Troubleshooting and Mitigation Strategies

Given the nature of the issue, a multi-pronged approach is advised:

1. Registry and User Profile Analysis

Export the registry settings related to DPI from both working and non-working profiles. Compare values meticulously.
Script automated checks or resets of the AppliedDPI registry key during user login, forcing it back to 96 if it shifts.
Consider creating a controlled test user with locked-down display settings to isolate the problem.

2. Examine and Adjust RDP and VMware Horizon Settings

For RDP connections, investigate whether the "Override high DPI scaling behavior" options are enabled in RDP client settings.
Ensure that Horizon Agent versions are the latest and monitor for vendor updates addressing DPI scaling bugs.
Test connections from various client devices with confirmed DPI settings to determine if the server is consistently overriding them.

3. Enforce Group Policies to Prevent Unwanted Scaling Changes

Create Group Policy Objects that lock down DPI settings or disallow changes to display scaler settings at the user level.
Block standard users from accessing display settings that can alter DPI scaling.

4. Engage Vendor Support Continuously

Work with VMware/Omnissa support to share logs and evidence that the client-scale factor request is correct but overridden by Windows.
Consult Microsoft support to determine known DPI scaling issues on Windows Server 2022 and validate whether recent updates may be involved.

5. Document and Monitor Session Events

Increase Windows Event Logging around display and user session events to capture potential triggers for DPI changes.
Correlate user logins and DPI changes to identify potentially problematic accounts.

6. Consider OS Patching and Update Rollbacks

Evaluate recent Windows Server 2022 updates. There have been instances where cumulative updates affect RDP or display behavior. Testing rollback or waiting for updated patches might be necessary.

Broader Implications for Remote Desktop Display Management

This scaling issue highlights persistent challenges in managing seamless user experiences across a mix of server OS versions, virtualization platforms, and remote desktop clients. As display technology advances and users demand high-DPI, multi-monitor support in remote sessions, compatibility and consistency challenges grow.
Enterprises relying on Remote Desktop Services must maintain strict control over user profiles and registry settings to prevent inadvertent scaling changes. They should also plan for continuous collaboration with vendors to promptly address bugs and update releases affecting DPI and session stability.

Conclusion

The DPI scaling irregularities on Windows Server 2022, particularly when accessed through RDP and VMware Horizon, reveal a stubborn blend of user-profile influences, registry settings, OS behavior, and virtualization nuances. Simple restorations provide temporary relief, but the root cause likely combines a specific user profile or action with underlying Windows or VMware display scaling mechanics.
Rectifying this issue requires methodical registry auditing, secure locking-down of scaling options, collaboration with vendor support teams, and vigilant monitoring of updates. IT administrators facing similar scenarios should script DPI enforcement policies, test restrictive environments, and maintain comprehensive logs of scaling changes correlated with user activity. In doing so, they can hike the steep path toward consistent DPI scaling and a stable, visually coherent remote desktop remote working environment.
By recognizing the subtle interplay between client DPI requests and Windows server processing, and by subscribing to disciplined administrative controls, organizations can better manage this tricky DPI scaling puzzle in modern remote desktop ecosystems.

This in-depth exploration stems from detailed community observations and best practice diagnostics from Windows environments dealing with this scaling issue in virtualized remote desktop contexts,.

Source: Windows Server 2022 – DPI / Scaling broken via RDP & VMware Horizon

ChatGPT · Apr 27, 2025

Display scaling issues in Windows Server 2022, especially within Remote Desktop Services (RDS) environments accessed via RDP or VMware Horizon, have emerged as a critical pain point for many IT professionals. A recent detailed case shared on Spiceworks provides a window into the complexity and nuance of this problem, where DPI scaling behaves erratically—visual elements rendered either disproportionately large or tiny, depending on how users connect and the resolution settings involved. This phenomenon is frustrating not only because of diminished usability but due to the underlying confusing mechanism whereby Windows appears to override client DPI settings, causing unexpected inconsistencies that cripple user experience.

Environment and Manifestation of the DPI Scaling Issue

The affected environments often share common configurations: Windows Server 2022 Datacenter edition with all updates applied, and remote access provided through VMware Horizon (recently rebranded as Omnissa) or standard RDP clients. Users report that display scaling anomalies began abruptly—a sudden shift from proper sizing to either oversized or undersized elements in the interface, dependent on display resolutions used in connections.
Empirically, the DPI setting in the Windows registry emerges as a key culprit. Investigations reveal that the registry path HKCU\Control Panel\Desktop\WindowMetrics holds a critical value called AppliedDPI, which governs the scaling factor. In malfunctioning instances, this value shifts from the standard 96 (equivalent to 100% scaling) to 120 (interpreted as 125% scaling). This registry modification manifests visually as altered scaling that Windows seemingly forces on all remote sessions and even on console login screens viewed directly on the ESXi management console.
The fact that restoring server snapshots or backups temporarily fixes the display scaling, only for the issue to resurface after several days linked to specific user logins, strongly indicates the problem lies in user profile-level modifications or behaviors. Restricting server access solely to IT personnel prevents recurrence, pointing toward user-specific settings or accidental DPI overrides within profiles.

Troubleshooting Efforts and Insights

The standard troubleshooting arsenal has been exhausted with little success in permanent resolution. These have included:

Deleting local user profiles to discard corrupted or errant profile settings
Reinstalling and updating the VMware Horizon agent to rule out client-side or agent-related DPI handling faults
Adjusting VM resources such as video RAM, which proved ineffectual
Examining Windows display settings, which appear normal and do not reveal the abnormal scaling

Notably, VMware Horizon server logs indicate the client explicitly requests the appropriate scaling, yet Windows overrides it—a behavior that hints at possible bugs in Windows Server 2022’s remote DPI management or an incompatible interaction with the Horizon agent's DPI handling.

Deeper Technical Analysis

Stripping down the problem to its core reveals several layers:

Registry-Based DPI Handling: Windows stores DPI scaling factors in user registry keys, which can be altered manually or programmatically. The unexpected shift to 125% scaling represents an aberrant state where the server disregards the client’s native DPI request.
Remote Desktop DPI Negotiation Complexity: RDP and Horizon agents have different methods for DPI detection and negotiation. Ideally, DPI contexts propagate from clients to hosts, but system policies, user configurations, or bugs may disrupt this flow, causing servers to apply default or unintended DPI values.
User Profile Influence: Since DPI is a per-user setting and manifests after user login, individual profiles might have automatic scripts, applications, or even user actions that inadvertently trigger the DPI change, which then persists beyond the session.
Potential Windows Server 2022 Bugs or Security Patch Effects: Continuous Windows updates may have introduced unintended side effects where DPI scaling for remote sessions is improperly applied. Similar bugs and regressions have arisen in past updates, demanding cautious update management.

Practical Recommendations for Mitigating the Issue

Until a verified fix is provided via Microsoft or VMware, administrators can apply a combination of the following:

Registry Monitoring and Enforcement: Maintain a documented baseline of registry DPI settings (AppliedDPI = 96) and deploy login scripts or Group Policy Objects (GPOs) that forcibly reset the DPI value at user logon or session start, overriding any rogue changes by users or applications.
Group Policy Lockdown on Display Scaling: Impose policies that prevent users from modifying DPI scaling settings, which can be implemented via registry lockdown or system configuration to standardize display behavior.
User Profile Sanitation and Controlled Testing: Isolate user profiles that cause the issue by removing non-essential customizations, testing new profiles with enforced DPI settings, and closely monitoring for reoccurrences.
Review RDP and Horizon Settings: Experiment with RDP client options such as "Override high DPI scaling behavior" or "Use all my monitors," and in Horizon, verify agent versions and configuration patches are up to date. Persistent issues might warrant engaging vendor support for specialized options or patches.
Collaborate with VMware/Omnissa and Microsoft Support: Proactively escalate the issue through official support channels, as these companies can offer insights into recent patches, known bugs, and advanced troubleshooting tailored to complex RDS environments.

Broader Implications and Industry Relevance

The problem seen in Windows Server 2022’s DPI scaling behavior over remote desktop sessions highlights critical challenges faced by enterprise IT in a hybrid and virtual work world. With remote desktops becoming frontline tools for administrators and users, display fidelity and usability directly influence user satisfaction and productivity.
Moreover, this issue sheds light on the delicate balance between modern high-DPI display environments and legacy or server-grade operating systems that were historically optimized for different display models. Moving forward, Microsoft and software vendors must harmonize remote session DPI awareness with scalable and robust mechanisms that gracefully handle diverse client environments.
Additionally, this case demonstrates the necessity of rigorous patch testing, user profile hygiene, and layered policy governance in maintaining stable server infrastructure. Organizations must have contingency workflows to address errant updates or user-induced configuration changes that undermine remote access consistency.

Related Windows Updates and Remote Desktop Challenges

It is worth noting that Microsoft has faced several remote desktop-related bugs in recent releases, including session freezes and disconnects caused by recent security patches on Windows 11 and Windows Server variants. Emergency Known Issue Rollbacks (KIR) and Group Policy workarounds emerged as interim solutions while permanent fixes are developed. Although these issues are not directly the same as DPI scaling, they underline the fragility and interdependence of Windows remote desktop components under evolving Windows update regimes.

Conclusion

Windows Server 2022's DPI scaling anomalies in RDP and VMware Horizon environments present a multifaceted challenge linked to registry DPI values, user-specific actions, and perhaps underlying platform bugs. Temporary relief through backups and limiting user access confirms user profiles as a significant vector for the problem. Administrators facing these issues should employ vigilant registry management, apply Group Policy restrictions, and coordinate closely with vendors to track emerging fixes.
Ultimately, the DPI scaling problem serves as a cautionary tale about the complexity of modern remote desktop environments, especially when hosted on evolving server platforms. A disciplined, methodical approach blending technical controls, user management, and vendor collaboration is key to ensuring these systems remain visually consistent and user-friendly for remote sessions.
For Windows Server 2022 administrators and professionals working with RDS in VMware Horizon setups, staying informed through community forums, vendor updates, and sharing experiences will remain vital while awaiting definitive patches or best practice guidelines to close this vexing DPI scaling gap.

Source: Windows Server 2022 – DPI / Scaling broken via RDP & VMware Horizon

ChatGPT · Apr 27, 2025

The mysterious DPI scaling issue encountered in Windows Server 2022 environments when connecting via RDP or VMware Horizon (now Omnissa) has become a troubling puzzle for system administrators and IT professionals. Users report erratic display scaling behavior, where visual elements appear either excessively large or undesirably small — a symptom indicative of Windows applying an incorrect DPI setting in remote sessions. This problem has critical implications for Remote Desktop Services (RDS) environments that depend heavily on consistent, high-fidelity display rendering for productivity and usability.

Understanding the Issue Context and Environment

Recent reports from community forums confirm the affected environments typically use the latest VMware Horizon 8 client (Omnissa rebrand) coupled with fully updated Windows Server 2022 Datacenter editions. The distortion appears in both standard RDP connections and Horizon sessions. Notably, the DPI scaling failure manifests variably depending on the client device’s resolution settings, indicating a failure in synchronizing DPI parameters between client and server.
Investigation reveals the root of the anomaly resides in Windows applying an erroneous registry-stored DPI value under the user's settings at:
HKCU\Control Panel\Desktop\WindowMetrics
In faulty scenarios, the AppliedDPI DWORD has been seen set to hexadecimal 0x00000078 (decimal 120), equating to a 125% scaling factor, which conflicts with the expected standard DPI setting of 0x00000060 (decimal 96), or 100% scaling. This disparity causes the server's graphical interface to inflate or shrink disproportionately, leading to unusable visual experiences for connected users.
Interestingly, restoring the affected server to an earlier state temporarily rectifies the DPI scaling problem. However, the issue resurfaces after some days of normal operation, suggesting that either user profiles or system processes dynamically alter DPI settings during session activity. Limiting access to only IT personnel after restoration has prevented recurrence, further pointing to specific user actions or profiles as triggers for the DPI override.

What Has Been Tried and Observed

Several intensive troubleshooting steps have been implemented without success:

Profile Re-creation: All local user profiles were deleted to rule out persistent corruption or misconfiguration in user data.
Horizon Agent Reinstall: Complete removal and reinstallation of VMware Horizon Agent failed to impact the issue.
vRAM Adjustment: Altering the VM’s memory allocation had no bearing on DPI scaling outcomes.
Direct Console Observations: Even on the ESXi console—outside the context of remote sessions—the Windows lock screen displayed scaling abnormalities. Normal display scaling only resumed upon successful user login via console, indicating the problem was not entirely contingent on RDP or Horizon agents.
Horizon Logs: According to VMware’s logs, client DPI scaling requests are correctly received but Windows internally overrides these, implying that the DPI handling bug resides within the Windows platform layer during remote desktop session initialization.

Deep Dive into Root Causes

User Profile-Triggered DPI Changes

The correlation between restricted access to IT users and absence of issues strongly hints at manual or inadvertent DPI adjustments by certain end-users causing registry changes. Since DPI settings reside per-user, any scaling tweaks made by a user affect subsequent logins and sessions. This behavior aligns with the observations that server restoration resets the DPI value, but user activity eventually re-applies the incorrect DPI.

DPI Handling in RDP and Horizon Sessions

Remote Desktop Protocol and VMware Horizon agents employ somewhat distinct approaches to managing display scaling compared to local sessions. Ideally, client scaling preferences should propagate and enforce consistently on server-side sessions. However, Windows Server 2022 appears to be mishandling or forcibly overriding these settings — potentially a regression introduced in recent updates or an unaddressed bug in how DPI is processed during session initiation.

Software Bugs or Inadvertent Update Side-Effects

Given Windows Server 2022's regular updates, it is plausible that a recent cumulative update, security patch, or driver change altered DPI scaling behavior, accidentally enforcing incorrect DPI values regardless of client requests. Such subtle update-linked regressions are common in complex OS environments and require coordinated vendor support to diagnose and fix.

Recommended Diagnostic and Mitigation Strategies

1. Registry and User Profile Monitoring

System administrators should routinely review the AppliedDPI registry key across all user profiles to detect anomalous values. Logging or scripting solutions can enforce or reset this value to the desired 96 (100%) prior to user login. Consider creating login scripts that automatically correct DPI registry entries, especially for users not in the IT group.
Comparative analysis of profiles that cause DPI distortion versus clean profiles may reveal patterns or user activities triggering DPI changes.

2. RDP and Horizon Configuration Optimization

Server admins should experiment with RDP client options such as overriding DPI scaling rules in the connection settings. Group Policy Objects (GPOs) can be deployed to lock display scaling settings to prevent user modifications.
Monitor vendor releases for Horizon Agent updates or patches explicitly designed to improve DPI handling on Windows Server 2022.

3. Engage Vendor Support and Community Collaboration

Since logs from both VMware and Windows indicate correct scaling requests are made but overridden on server-side, filing support tickets with Microsoft and VMware is crucial. Sharing detailed logs, session metrics, and registry snapshots can accelerate identification of root causes.
The Spiceworks community and similar forums provide excellent platforms for peer support and sharing emerging workarounds or patches.

4. Document and Analyze Event Logs and Usage Patterns

Enabling increased session logging can reveal exact moments when DPI values shift, especially if correlated with specific users or applications. Event Logs may capture errors or informational entries related to display settings changes that help isolate offending triggers.
Pattern recognition — for example, changes happen after logging in as a particular user or after running certain software — can direct remediation efforts.

Broader Implications for Windows Remote Desktop Environments

As remote and virtualized computing become ubiquitous, stable and accurate DPI scaling in RDS environments is more vital than ever. Flaws such as these disrupt productivity, degrade user experience, and increase support overhead. This DPI scaling anomaly in Windows Server 2022 highlights broader challenges in managing modern display scaling:

Windows' legacy DPI awareness models are inherently complex, often conflicting with dynamic multi-monitor and remote session contexts.
Developers and platform providers must continuously improve per-monitor DPI awareness and smooth scaling transitions to prevent blurry or distorted UI.
User-driven configuration changes remain a persistent source of DPI-related support issues.
Coordinated patching and validation cycles for operating system updates, remote desktop software, and display drivers are essential to prevent regression cycles.

Practical Workaround: Step-by-Step Guide

For administrators seeking near-term relief while longer-term solutions are developed, the following measures are advisable:

Backup the Current Registry DPI Settings: Export the registry path HKCU\Control Panel\Desktop\WindowMetrics before making any changes for recovery.
Manually Set AppliedDPI to 96: Either manually via regedit or through a logon script, set the DPI scaling value to the standard 96.
Implement Group Policies: Configure policies to restrict user ability to alter display scaling settings or lock registry keys related to DPI.
Test with a Clean User Account: Create and monitor behavior under a new user profile where DPI is controlled, to identify if the problem recurs.
Check Remote Desktop Client Settings: Ensure RDP or Horizon client is set to "Use all my monitors" or "Optimize for best appearance" to respect high-DPI scaling properly.
Maintain Logs and Notify Vendors: Keep detailed change and issue logs for future diagnostics or support cases.

Conclusion

The Windows Server 2022 DPI scaling anomaly through RDP and VMware Horizon sessions exemplifies the multifaceted challenge of managing display scaling in complex virtualized environments. The root cause, a persistent overriding of client DPI requests by incorrect registry-based AppliedDPI values, coupled with user profile interactions, hints at both user behavior and possible Windows system regressions as contributors.
Until an official patch or vendor fix is issued, IT administrators must adopt vigilant registry monitoring, use policy enforcement, and collaborate closely with support channels. This problem serves as a reminder of the delicate balance in enterprise systems between user flexibility, platform compatibility, and remote session fidelity.
For anyone managing Windows Server RDS environments, a methodical, data-driven approach combined with community engagement offers the best chance of mitigating DPI scaling frustrations—ensuring crisp, accurate, and consistent user experiences across remote desktops.
By maintaining awareness of the issue’s nuances and applying targeted safeguards, administrators can help keep remote access smooth and visually consistent in even the most demanding Windows Server 2022 environments.

For reference and expanded technical detail, see the original community discussion and aggregated findings in the Spiceworks forum post titled "Windows Server 2022 DPI / Scaling broken via RDP & VMware Horizon".

Source: Windows Server 2022 – DPI / Scaling broken via RDP & VMware Horizon

ChatGPT · Apr 27, 2025

Windows Server 2022's display scaling issues when accessed via RDP or VMware Horizon (now Omnissa) have emerged as a vexing problem for IT professionals, creating significant challenges in maintaining a consistent and usable remote desktop experience. The problem manifests as distorted DPI scaling where display elements appear either excessively large or uncomfortably small depending on the client's resolution. This behavior is symptomatic of erroneous DPI settings being applied on the server side during remote sessions, causing a mismatch of expected visual interfaces.

Understanding the Issue in Context

In environments combining VMware Horizon 8 and Windows Server 2022 Datacenter with current updates, multiple users have reported inconsistent DPI scaling during RDS sessions. Whether connecting through Horizon or standard RDP clients, users observe the entire desktop environment either enlarged beyond reason or shrunk to minuscule proportions. A deeper dive into the Windows registry, specifically the key HKCU\Control Panel\Desktop\WindowMetrics, reveals a discrepancy in the AppliedDPI value—a critical factor controlling display scaling.
On a healthy system, AppliedDPI typically holds a value of 96 (hex 0x60), which corresponds to 100% scaling. Problematic systems instead reflect a value of 120 (hex 0x78), aligning with a 125% scale factor, causing the disproportion seen in clients' sessions. Intriguingly, restoring the server from a backup resets the scaling to the correct state but only temporarily. After several days, the aberrant DPI setting reasserts itself, indicating something triggers the setting post-restore. Limiting server access exclusively to IT personnel appears to prevent recurrence, suggesting user-specific actions or profiles might inadvertently alter the scaling setting.

Dissecting the Root Causes

Several interrelated factors converge to create this malfunction:

User Profile DPI Overrides

Each user’s profile maintains individual settings that affect display parameters, including DPI. It is feasible that one or multiple user accounts modify DPI scaling either intentionally or inadvertently—perhaps by adjusting display settings or launching applications that alter scaling. Because these changes persist in the user’s registry hive, they surface upon login, overriding defaults and applying unexpected scaling across the session.

Windows Registry and DPI Enforcement

The Windows operating system’s reliance on registry keys like AppliedDPI and LogPixels in HKCU\Control Panel\Desktop or HKCU\Control Panel\Desktop\WindowMetrics means any changes here directly impact visual display. Attempts to delete user profiles or reinstall Horizon agents do not prevent the scaling from drifting back to 125%, implying a persistent configuration or script adjusts these settings post-login or during session initiation.

RDP and VMware Horizon DPI Negotiations

While RDP and VMware Horizon clients pass DPI requests, logs show that Windows Server ends up applying a scale factor different from that requested. This suggests an internal override or bug causes Windows to ignore client scaling during session setup. Though reinstalling or updating Horizon Agent shows no effect, there is a possibility that how Windows Server 2022 processes DPI scaling in remote environments differs from expectations or previous Windows versions.

Potential Bug or Update Regression

Windows Server 2022, with ongoing security and feature patches, might have an update that inadvertently introduced this DPI scaling anomaly. Similar issues have surfaced in different remote desktop features after updates, hinting at a regression or newly introduced DPI management quirk.

Practical Troubleshooting and Workarounds

System administrators facing this challenge can consider a multi-pronged approach:

Registry Audits and Baseline Enforcement

Export the working AppliedDPI registry value (96 decimal) and use it as a baseline configuration.
Develop a logon script that enforces this value upon each user login, thereby preventing rogue changes from persisting.
Regularly audit registry keys for unexpected scaling alterations.

Lockdown DPI Settings via Group Policy

Implement Group Policy Objects (GPOs) to restrict user ability to change display scaling settings, either by locking registry access or disabling the relevant UI controls.
This enforces consistency across user sessions and prevents accidental or intentional DPI overrides.

Adjust RDP and Horizon Configuration

Review RDP client settings for DPI scaling override options; experiment with toggling these to ensure the server respects client DPI requests.
Stay vigilant for patches or updates from VMware/Omnissa addressing known DPI scaling issues.

Controlled User Testing

Create controlled test users with strict DPI setting enforcement to monitor whether issues recur.
Monitor server behavior when different user profiles log in to detect processors of scaling reset triggers.

Collaboration with Vendors and Community

Engage Microsoft and VMware support channels for escalated troubleshooting and bug tracking.
Leverage Windows forums and IT communities such as Spiceworks for shared diagnostic experiences and emerging patches.

Broader Implications for Remote Server Environments

This DPI scaling dilemma highlights challenges faced in remote desktop usability amid increasingly complex virtualized and cloud environments. Users demand consistent graphical fidelity regardless of client devices or displays, but legacy and new systems alike struggle to harmonize DPI awareness across networked sessions.
User profiles remain a common source of session personalization but also potential instability when system-wide consistency is critical. Balancing individual customization with organizational stability is a key ongoing concern for IT departments.
Moreover, patch management is essential; security releases and feature updates may introduce unintended side effects on remote display behaviors. Vigilant testing in controlled environments before broad deployment protects production workflows from disruptive DPI or display regressions.

Conclusion: Navigating the DPI Scaling Puzzle

The Windows Server 2022 DPI scaling issue when accessed via RDP or VMware Horizon presents a complex interplay of user-configured settings, system registry enforcement, and remote session negotiation failures. The root cause seems tied to particular user actions or profiles inadvertently setting the AppliedDPI to 125%, which Windows then rigidly applies across sessions.
While temporary resets via server restoration or IT-only access offer respite, a permanent fix requires instituting registry enforcement, group policy lockdowns, careful RDP and Horizon configuration, and continued vendor collaboration.
For administrators managing critical Remote Desktop Services environments, a methodical, data-driven troubleshooting strategy offers the best defense—leveraging registry baselines, user testing, configuration tweaking, and engagement with official support channels. Transparency in documenting and sharing findings not only accelerates remediation in individual setups but also contributes to broader ecosystem improvements.
By embracing incremental fixes while awaiting comprehensive patches from software vendors, IT professionals can maintain user productivity and system stability despite the tricky nuances of DPI scaling in remote Windows Server 2022 contexts.

This narrative not only captures the problem's technical essence but also blends practical advice and insightful commentary relevant for Windows Server administrators facing DPI scaling troubles in virtual desktop and remote session scenarios.

Source: Windows Server 2022 – DPI / Scaling broken via RDP & VMware Horizon

ChatGPT · Apr 27, 2025

Windows Server 2022 users operating in Remote Desktop Services (RDS) environments have reported perplexing issues with display scaling when connecting via Remote Desktop Protocol (RDP) or VMware Horizon (recently rebranded as Omnissa). This glitch manifests as either overwhelmingly large or undesirably small screen elements, linked to errant DPI (Dots Per Inch) scaling configurations applied by Windows rather than the client’s requested settings.

Understanding the Nature of the DPI Scaling Issue

The problem has been chiefly observed on server environments running the latest versions of VMware Horizon 8 atop Windows Server 2022 Datacenter with all current updates installed. Depending on the client resolution, the display contents on the server are improperly scaled, which severely degrades usability. This is especially notable in setups where users connect remotely using either VMware Horizon or the native Windows RDP client.
Key findings from system audits reveal that Windows is imposing a DPI scaling value of 125% (reflected as 0x00000078 in the registry key HKCU\Control Panel\Desktop\WindowMetrics\AppliedDPI), which contrasts with the correct baseline of 100% scaling (0x00000060). This misconfiguration persists even though logs from VMware Horizon indicate the client correctly requests the intended scaling—pointing squarely at Windows overriding these requests internally.
Temporary restoration of the server from backup resets the AppliedDPI to the correct 100% value with normal display scaling restored. However, the issue invariably recurs after several days, unless server access is restricted exclusively to IT personnel. This behavioral pattern strongly suggests that a specific user action or a user's profile is possibly triggering registry changes or system policies that corrupt the DPI setting.

Investigating the Root Causes

Several avenues clarify the complex root of this scaling anomaly:

User Profile Impact and Registry Tweaks: DPI settings in Windows can be governed by individual user profiles via registry keys. The problematic DPI setting indicates that either a user profile, during login or session, modifies the DPI setting, or a user-initiated change (perhaps inadvertent) is applied globally or per-user. Deleting local profiles did not resolve the issue, indicating possible policy or automated script-based alterations.
RDP and VMware Horizon DPI Handling Disparities: Both RDP and Horizon have mechanisms for negotiating DPI. Ordinarily, the client's DPI request should be respected by the server session, but Windows Server 2022 appears to override this negotiation, possibly due to internal DPI scaling logic introduced or altered in recent Windows updates. Reinstalling the Horizon Agent did not correct the problem, further implicating the server-side DPI management rather than the client or agent tool.
Potential Software Bugs and Update Interactions: Continuous update cycles for Windows Server 2022 might have introduced regressions or bugs affecting DPI scaling, particularly in remote session contexts. Such unintended side effects may override or ignore client DPI requests during session initialization or shortly thereafter.

Diagnostic and Remediation Strategies for Administrators

Administrators contending with this display scaling conundrum may pursue a structured troubleshooting methodology:

Registry Baseline and Monitoring: Regularly export and monitor the AppliedDPI values in the HKCU\Control Panel\Desktop\WindowMetrics registry path for all user profiles. Automate the reset of this value to 96 upon user login via scripts or Group Policy Object (GPO) enforcement.
User Profile Analysis: Since scaling issues cease when only IT access is permitted, create test accounts within the environment and enforce the correct scaling registry value. Monitor over time to identify profiles or user behaviors that trigger the problem.
Adjust Remote Session Settings: Explore and tweak RDP advanced settings that control DPI behavior, such as “Override High DPI scaling behavior” on clients. Investigate VMware Horizon settings for DPI scaling to ensure no conflicting parameters interfere.
GPO and Policy Lockdown: Deploy Group Policies that prevent users from modifying display scaling settings or lock down registry sections related to DPI scaling to curtail unauthorized changes.
Stay Engaged with Vendors and Communities: Engage both Microsoft and VMware/Omnissa support channels with detailed logs and reproduction steps. Participation in IT forums and community knowledge bases like Spiceworks can provide insights into potential workarounds or patches.

Broader Implications of Remote Display DPI Challenges

This DPI scaling issue is a symptom of broader complexities in remote desktop and virtual desktop infrastructure where multi-monitor setups and high-DPI displays are common. Challenges documented in Windows 10 and 11’s handling of DPI scaling, including those involving "Per-Monitor DPI Awareness" and "Mixed-Mode DPI scaling," highlight difficulties for both application developers and system administrators in managing seamless high-DPI experiences.
Windows historically managed DPI scaling on a system-wide basis, and only in more recent iterations introduced per-monitor awareness. However, remote desktop sessions often complicate DPI management because the client and server must negotiate scaling settings dynamically, which can be volatile or inconsistently implemented. VMware Horizon agents and RDP clients factor in on the client side, but ultimately the server must honor these settings for a good user experience.

Practical Tips and Workarounds While Awaiting Fixes

While the root cause may hinge on Microsoft or VMware issuing patches or configuration guidance, the following interim steps can help admins maintain usable environments:

Always backup current registry DPI settings before making changes.
Set the AppliedDPI registry value manually to 96 (100% scaling) either via login scripts or GPO.
Use Group Policy to block user ability to change display scaling settings.
Monitor event logs for entries indicating scaling or display setting changes, which may help trace the source of the unwanted reset.
Encourage users to avoid changing display scaling in remote sessions.
Check for updates to Horizon Agent and Windows Server patches that address DPI behavior, as vendors continue to work on these issues.

Conclusion: Navigating DPI Scaling in Windows Server 2022 Remote Environments

The Windows Server 2022 DPI scaling issue via RDP and VMware Horizon underscores the ongoing intricacies of delivering stable, consistent user experiences in modern remote access environments. The core problem appears to center on Windows overriding client DPI requests and imposing a scaling setting (typically 125%), adversely affecting the remote display presentation.
Resolution requires a balanced approach combining registry monitoring, user management, GPO lockdowns, and vigilant vendor engagement. As remote desktop and virtualization technologies continue evolving, these DPI scaling glitches highlight the critical need for robust system policies, thorough testing, and community collaboration to drive durable fixes.
For IT professionals managing RDS on Windows Server 2022, adopting methodical diagnostics and carefully controlling user profiles and settings are essential in maintaining productivity and usability. While the issue remains an irritant, the combination of practical workarounds and upcoming patches will hopefully restore reliable scaling behaviors in these complex virtualized remote desktop ecosystems.

This detailed analysis incorporates community reports and technical insights drawn from recent discussions and troubleshooting experiences shared in IT forums dedicated to Windows Server and VMware Horizon environments,.

Source: Windows Server 2022 – DPI / Scaling broken via RDP & VMware Horizon

ChatGPT · Apr 27, 2025

Windows Server 2022 administrators using Remote Desktop Services (RDS) with VMware Horizon (recently rebranded to Omnissa) have been encountering a perplexing DPI scaling issue that significantly impacts user experience and productivity. The problem manifests when users connect to the server via either VMware Horizon or the native Remote Desktop Protocol (RDP). Depending on the display resolution, the desktop environment appears either excessively large or too small, signaling a clear misapplication of DPI scaling settings by the server operating system.
This article delves deeply into the nature of this DPI scaling anomaly, explores diagnostic observations, and outlines practical workarounds and strategic recommendations to combat this ongoing issue within modern remote desktop environments.

Understanding the Environment and the Problem

The affected configuration typically involves:

Windows Server 2022 Datacenter, fully updated with the latest patches.
VMware Horizon version 8 or its latest iteration under the Omnissa name.
Clients connecting through either VMware Horizon clients or traditional RDP clients.

Despite being equipped with the latest software versions and updates, administrators began noticing that after a certain time period, sometimes just days after a fresh system restore, DPI scaling devolves incorrectly. This leads to user interfaces that appear either shrunk or enlarged beyond reasonable limits, making the desktop hard to use and potentially impairing productivity.
Interestingly, restoring the server from a backup momentarily resolves the issue, resetting DPI scaling to normal. However, the problem reemerges after a few days or user logins. When administrators limited access to the system to IT personnel only, the abnormal scaling did not reoccur, suggesting that the actions or preferences of a particular user or group of users might be inadvertently triggering the DPI scaling anomaly.

The Crucial Registry Insight: AppliedDPI

A critical discovery in diagnosing this issue was the difference in registry values between functional and problematic user sessions. Specifically, the registry key:
HKCU\Control Panel\Desktop\WindowMetrics\AppliedDPI
shows distinct values:

Correct (normal) scaling: AppliedDPI = 0x00000060 (decimal 96), which corresponds to 100% scaling.
Broken scaling: AppliedDPI = 0x00000078 (decimal 120), representing 125% scaling.

This disparity reveals that Windows is applying a DPI scaling setting inconsistent with the client request, enforcing an unintended 125% scaling factor that distorts the remote desktop experience.

Attempts to Fix and Observations

Despite various troubleshooting steps, the issue persists:

Deleting local user profiles: No change in the DPI behavior.
Reinstalling VMware Horizon Agent: No effect on scaling.
Adjusting VM resources such as video RAM: No improvement.
Observing the issue on the ESXi console’s login screen where scaling is also incorrect before logon, but normalizes after console login.

Additionally, the display settings within Windows Server 2022 itself appear normal, offering no clues as to the causes of the overriding DPI scaling.

Potential Root Causes

User-Specific Registry Modifications

Given that the issue dissipates with restricted user access, one hypothesis is that a particular user's session modifies the DPI registry settings, possibly via inadvertent changes in display preferences or application behavior that triggers the DPI override.

Windows DPI Scaling Mechanics and Remote Sessions

Windows manages DPI scaling through several layers including system-wide settings, per-user registry entries, and session-specific policies. Remote sessions using RDP or Horizon may negotiate scaling parameters differently, and Windows might apply system or user-specific values that supersede client requests.
Logs from VMware Horizon confirm that the client requests the correct DPI scaling but Windows ultimately overrides this, suggesting an internal Windows mechanism or bug is misapplying DPI settings.

Software Bugs or Update Side Effects

Since Windows Server 2022 regularly receives cumulative updates and patches, it is plausible that a recent update introduced a regression affecting DPI scaling behavior under remote sessions. Vendor collaboration and escalation are necessary to confirm if this behavior is an acknowledged bug.

Diagnostic and Mitigation Strategies

For IT administrators faced with this DPI scaling issue, the following steps offer a structured approach:

1. Registry and Profile Auditing

Examine user profiles for registry deviations under HKCU\Control Panel\Desktop\WindowMetrics.
Establish a baseline of proper AppliedDPI values (usually 96 for 100% scaling).
Use scripts or Group Policy to enforce or reset AppliedDPI to 96 on user logon to prevent overrides.

2. RDP and Horizon Configuration Review

Investigate and experiment with RDP advanced settings that enforce scaling behaviors.
Confirm Horizon Agent is updated and review any vendor-provided configuration options relating to DPI scaling within VMware Horizon/Omnissa.
Consider disabling DPI scaling override options that might conflict with client settings.

3. User Access Controls

Limit user access to troubleshoot which user profile produces the problematic scaling.
Test with controlled user accounts where DPI is locked or preset.
Monitor user sessions for registry or setting changes in real time.

4. Logging and Pattern Analysis

Enable enhanced logging for RDP and Horizon sessions focusing on DPI negotiation.
Check Windows Event Viewer for any display configuration errors or warnings during or after login.
Identify sessions or events preceding DPI overrides to isolate causes.

5. Engage with Vendors and Community

Open support cases with Microsoft and VMware/Omnissa to report the issue.
Collaborate with community feedback forums such as Spiceworks or WindowsForum.com for workaround sharing.
Stay updated on hotfixes or patches addressing DPI behavior in remote sessions.

Broader Implications in Remote Desktop Environments

This DPI scaling problem is symptomatic of a larger challenge in modern remote desktop setups: maintaining consistent and user-friendly display experiences across a wide variety of client devices and display configurations.
As remote work and virtualization become ubiquitous, the way Windows handles DPI scaling in remote desktop sessions gains critical importance. Mismanagement of DPI can cause user frustration, reduce productivity, and complicate IT support.
Some key lessons and recommendations involve:

Ensuring user profiles are standardized and cleaned regularly to avoid errant customizations.
Testing OS updates in a lab environment before deploying in production, especially for remote desktop hosts.
Applying group policies or login scripts to govern DPI scaling consistently.
Encouraging vendor cooperation to improve DPI negotiation protocols and fix known bugs swiftly.

Practical Workaround: Step-by-Step

While awaiting permanent fixes, administrators can implement the following workaround to alleviate the DPI scaling issue:

Export the current registry settings under HKCU\Control Panel\Desktop\WindowMetrics for backup.
Manually set the AppliedDPI registry value to 96 for all user profiles showing misconfiguration. This can be automated with login scripts or Group Policy Preferences.
Consider applying Group Policy to prevent users from altering display scaling settings, restricting override capabilities.
Customize RDP connection settings to optimize for high-DPI displays, ensuring options like “Use all my monitors” or “Optimize for best appearance” are correctly set.
Monitor the affected user sessions to confirm whether the setting persists and if the problem recurs.
Document all changes and interactions with vendor support to build a case for a permanent patch.

Conclusion

The Windows Server 2022 DPI scaling issue when accessed via RDP or VMware Horizon highlights an intricate challenge with remote desktop display management. It exposes how registry settings like AppliedDPI can be unexpectedly altered, potentially by user actions or internal system processes, causing poor scaling outcomes that affect usability.
Though temporary measures such as server restoration or limiting user access offer short-term relief, they do not address the root cause. A layered approach involving registry enforcement, session configuration, user management, and vendor collaboration is essential to resolve and prevent recurrence.
Administrators must remain vigilant, regularly monitor DPI configurations, and engage with both Microsoft and VMware support for updates or official fixes. Meanwhile, communities like Spiceworks offer valuable peer insight and shared experiences that can accelerate diagnosis and mitigation.
Ultimately, the complexities of DPI scaling in virtualized and remote environments underscore the importance of careful configuration, continuous observation, and proactive troubleshooting to sustain a seamless Windows Server 2022 remote desktop experience.

This feature article combines a thorough summary of the issue shared by users at Spiceworks with deeper technical insights and practical advice for Windows Server administration. By understanding the registry bases of DPI scaling, the behavior of remote session protocols, and effective management strategies, IT professionals can navigate this challenging error with greater confidence and effectiveness.
For further community discussion and support, consider visiting the original thread here:
Windows Server 2022 – DPI / Scaling broken via RDP & VMware Horizon
And see detailed diagnostic and corrective recommendations in recent forum collationsand.

Source: Windows Server 2022 – DPI / Scaling broken via RDP & VMware Horizon

ChatGPT · Apr 27, 2025

Windows Server 2022 users leveraging Remote Desktop Services (RDS) through VMware Horizon (now known as Omnissa) have been encountering a perplexing and disruptive issue related to DPI scaling and display behavior. This phenomenon, where visual elements either become too large or too small depending on the resolution and client connection method, has significantly impacted user experience and productivity in remote environments. Despite attempts to resolve the problem by restoring server backups and reinstalling key components, the core issue persists, demanding a closer look at the underlying causes, diagnostic challenges, and mitigation strategies.

Environment and Problem Overview

The issue appears in environments running VMware Horizon 8 (latest version) paired with Windows Server 2022 Datacenter edition fully patched with the latest updates. Users connect both by VMware Horizon client and by traditional Remote Desktop Protocol (RDP) sessions to Remote Desktop Session Hosts (RDSH). The key symptom is that the DPI scaling is being incorrectly applied: the display either becomes excessively scaled up or down, making text, icons, and interface elements unusable at times.
Investigations have indicated that the root problem lies in how Windows Server 2022 applies and overrides DPI settings negotiated through RDP or Horizon, with the server applying an incorrect DPI scaling factor irrespective of client requests. Importantly, the issue is reproducible across different access methods (VMware Horizon, direct RDP, and even the ESXi console lock screen), which strongly suggests a server-side DPI application issue rather than a client-side misconfiguration.

Observations and Technical Insights

A critical clue to the problem’s nature comes from the Windows Registry under the path:
HKCU\Control Panel\Desktop\WindowMetrics
Two distinct values of the AppliedDPI registry key have been observed:

On affected servers: 0x00000078 (120) – this corresponds to 125% DPI scaling.
On non-affected (working) servers: 0x00000060 (96) – representing the standard 100% DPI.

Restoring the server from a backup resets AppliedDPI to the correct 96 value and temporarily fixes the issue. However, once users—particularly non-IT staff—begin accessing the server, the value changes back to 120, causing the scaling problem to reappear. Restricting access to only IT personnel prevents the issue from recurring, further pointing to a particular user or user behavior inadvertently altering DPI settings.
Other troubleshooting steps have included:

Deleting all local user profiles to remove potentially corrupt or misconfigured user DPI profiles.
Reinstalling or updating the VMware Horizon Agent on the server.
Adjusting virtual machine hardware resources like video RAM (vRAM).
Verifying that Windows display settings showed no anomalies.
Confirming through Horizon logs that the client correctly requests the appropriate DPI scaling.

Nonetheless, Windows persists in overriding the client-requested DPI scaling.

Potential Causes

Several factors seem to contribute to this persistent DPI scaling anomaly:

User-Profile Level DPI Overrides:
The alteration of the AppliedDPI registry value appears tied to specific user profiles or user actions that change DPI settings, possibly even inadvertently. Since user-specific settings reside under HKCU, it aligns with one or more users saving or triggering a display scaling override during their session.
Windows Server 2022 DPI Handling in RDP Sessions:
DPI scaling in remote desktop sessions involves negotiation between client and server protocols. While RDP supports passing DPI information, Windows Server 2022 may handle this negotiation differently compared to previous server versions. It might apply system defaults or legacy behaviors that cause DPI values to revert or ignore client requests.
Possible Software Bugs or Recent Updates Impact:
Given that Windows Server 2022 is continuously updated, there could be bugs or regressions in the DPI scaling mechanisms introduced by recent cumulative or feature updates. These updates might unintentionally affect how DPI values are calculated or enforced per user session.
VMware Horizon Agent and RDP Client Interactions:
Although reinstalling Horizon Agent had no impact, the interaction between VMware Horizon’s display drivers and Windows DPI scaling remains complex and could introduce unforeseen inconsistencies.

Broader Context of DPI Scaling Challenges in Remote Desktop Environments

DPI scaling has long been a challenge in the Windows ecosystem, especially with the emergence of high-resolution displays and multiple monitors with differing scale factors. Windows 10 and Windows Server versions introduced improvements with per-monitor DPI awareness and better registry-based controls, yet remote desktop environments continue to face issues.
Particularly, when scaling settings are saved in user profiles, per-user registry hive differences can lead to conflicting DPI values being applied. This complexity increases in multi-user, terminal server-like environments where numerous sessions with varying client device characteristics occur concurrently.
Moreover, Windows’ rendering of some UI components like window chrome, dialogs, and fonts may require additional handling to ensure correct scaling. Legacy components or third-party software such as VMware Horizon might not always fully align with Windows’ DPI awareness models.

Recommended Troubleshooting and Mitigation Strategies

For IT administrators facing this DPI scaling puzzle in Windows Server 2022 RDS environments, a multi-pronged approach combining technical auditing, registry enforcement, policy controls, and user management is advisable:

1. Baseline and Monitor Registry Settings

Perform initial exports of the registry keys under:
HKCU\Control Panel\Desktop\WindowMetrics
and specifically monitor AppliedDPI before and after user sessions. Automate checks using scripts to detect when AppliedDPI changes occur, helping identify users or sessions triggering DPI overrides.

2. Enforce DPI Values via Login Scripts or Group Policy

To keep DPI consistent, enforce a standard AppliedDPI value (typically 96) by using scripts or Group Policy Registry Preferences that run at user login. This approach resets any user changes to the desired DPI scaling.

3. Lock Down Display Scaling Settings via Group Policy

Implement Group Policy Objects (GPOs) that restrict users from changing display scaling or prevent DPI overrides. This may require registry lockdowns or disabling certain control panel features.

4. Review and Adjust RDP and VMware Horizon Client Settings

Enable or disable DPI scaling overrides on the RDP client side as per the environment's needs.
Experiment with RDP's "Override high DPI scaling behavior" options.
Keep VMware Horizon and its Agents updated.
Consult VMware/Omnissa support for any recent patches or known DPI-related issues.

5. Isolate User Profiles

Create a test user with restricted settings and monitor if DPI scaling issues recur. This can help isolate whether the problem is profile-specific or system-wide.

6. Keep Systems Updated but Test Updates

Monitor Windows Server 2022 updates for patches relating to display scaling or Remote Desktop bugs. Test patches in controlled environments before rolling out to production servers.

7. Coordinate with Vendor and Community Support

Seek help from Microsoft and VMware/Omnissa support teams. Additionally, engaging IT communities like Spiceworks, expert forums, and Windows-focused user groups can yield practical, crowdsourced solutions and workarounds.

Further Observations and Industry Perspective

This DPI scaling issue highlights the intricate challenges IT teams face when combining advanced virtualization platforms with modern Windows Server versions. Remote desktop technologies continuously evolve, accommodating new device resolutions, network protocols, and security requirements, yet compatibility and user experience issues linger.
Administrators must balance user flexibility with environment stability, often by locking critical settings in enterprise setups. This instance emphasizes that DPI scaling—once a simple local display setting—has become a complex matter in remote multi-user virtualized infrastructures.
Moreover, this DPI quirk emerges at a time when Microsoft is addressing other Remote Desktop Service-related challenges like unexpected disconnects and freezing in Windows 11 and Server 2022/2025 environments, pointing to a broader need for stability and protocol robustness in remote access technologies.

Conclusion

The Windows Server 2022 DPI scaling issue experienced through VMware Horizon and RDP connections is a notable example of modern remote desktop administration hurdles. At its core, the problem stems from Windows server-side DPI settings changes, seemingly triggered by specific user profiles or actions, which override the correct DPI scaling values negotiated or requested by clients.
Although temporary fixes such as restoring server backups or limiting user access have mitigated the problem transiently, a sustainable resolution requires:

Careful monitoring and enforcement of DPI registry settings,
Rigorous policy-driven control of display scaling alterations,
Vendor collaboration,
Thorough testing of server and agent updates.

This scenario underscores the importance for IT professionals to remain vigilant about display configuration management in remote desktop environments and to cultivate proactive troubleshooting and documentation practices. The integration of virtualization platforms with Windows Server continues to deepen, making such display issues increasingly impactful on end-user productivity.
Lastly, by learning from community-sourced reports and aligning with vendor advisories, administrators can maintain smoother, more consistent remote desktop displays, preserving the effectiveness of their Windows Server 2022 RDS deployments for a diverse set of users.
,,,

Source: Windows Server 2022 – DPI / Scaling broken via RDP & VMware Horizon

ChatGPT · Apr 27, 2025

Windows Server 2022, in conjunction with remote desktop environments like RDS (Remote Desktop Services), VMware Horizon (now Omnissa), has been experiencing a perplexing and disruptive DPI scaling issue. The problem, as shared by a user in a popular IT community forum, manifests as inconsistent and incorrect display scaling during remote connections, where visuals look either excessively large or unexpectedly small. This display anomaly is triggered through both VMware Horizon connections and regular RDP (Remote Desktop Protocol) sessions, indicating a systemic issue in how Windows Server 2022 handles DPI settings during remote sessions.

Understanding the DPI Scaling Issue on Windows Server 2022

The core of the problem lies in the DPI setting that Windows applies upon user logon via remote sessions. Typically, Windows manages display scaling through DPI (dots per inch) values, and the standard "normal" DPI setting is 96, which corresponds to 100% scaling. However, in these problematic environments, registry checks reveal that the DPI is set unusually—and incorrectly—to 120, equivalent to 125% scaling. This registry key is found under:
HKCU\Control Panel\Desktop\WindowMetrics
Here the AppliedDPI registry entry on faulty systems reads 0x00000078 (120 decimal), versus 0x00000060 (96 decimal) on correctly scaling machines. The scaling discrepancy directly affects user experience, making interfaces and fonts look distorted and compromising usability.
Interestingly, rolling back to an earlier server state (restoring from backup) resolves the issue temporarily, but it tends to resurface after some days of operation. Limiting access to IT personnel after restoration appears to prevent recurrence, suggesting that the problem might be user-profile specific or triggered by certain user actions that adjust DPI settings unintentionally.

Possible Causes and Technical Considerations

Several explanations have emerged from community discussions and diagnostic efforts:

User Profile-Specific DPI Modifications: Since the issue does not happen when only IT personnel are allowed access, it is highly likely that one or more user profiles apply customized display scaling settings. This behavior may be accidental or caused by software/applications modifying display parameters post-login.
Windows Server 2022 DPI Handling Bugs: Given that Windows Server 2022 is relatively new and continuously updated, it is plausible that recent patches contain regressions affecting DPI scaling, particularly in RDP or virtual desktop environments. Windows' overriding of client scaling requests, as shown in VMware Horizon logs, suggests a system-level DPI enforcement issue.
Remote Desktop and Horizon Agent Interactions: The VMware Horizon Agent, responsible for managing remote sessions, including DPI negotiation, does not seem to resolve the problem when reinstalled, implying that the root cause may lie within Windows’ DPI processing rather than the agent.
Registry and Policy Overrides: Windows' display settings, and specifically the AppliedDPI registry key, might be overridden by group policies or local configurations that adapt DPI to certain conditions or sessions. If these are improperly managed, unintended scaling is forced on user sessions.

Diagnostic Insights and Attempts at Resolution

The issue’s investigation involves key diagnostic findings:

Registry Inspection and Enforcement: Administrators observed that forcibly setting the AppliedDPI registry value to 96 does restore normal scaling. Attempts to delete user profiles and reinstall the Horizon Agent didn’t resolve the problem, indicating persistence within active user session settings.
VM Console Behavior: The VM’s console displays the lock screen with incorrect scaling as well, but after login through the console, the display normalizes, adding complexity to the issue — suggesting it is linked to user session initiation or profile loading.
DPI Negotiations Ignored: VMware Horizon logs show that the client requests proper DPI scaling, but Windows ignores this and imposes its override. It points to a disconnect between client-side expectations and server-side enforcement.
User Behavior Hypothesis: Since restricting login to IT users prevents the DPI problem from reappearing, it is suspected that some non-IT users, inadvertently or intentionally, are changing DPI-related settings that then persist or corrupt the session state.

Recommended Troubleshooting and Workarounds

Administrators grappling with this problem have considered and implemented various strategies:

Routine Registry and Profile Audits: Monitoring and comparing user profile registry keys at login can help identify which accounts cause DPI shifts. Automating enforcement of a safe AppliedDPI value during user logon, via login scripts or Group Policy, can mitigate inconsistent scaling.
Group Policy Lock-Down: Implementing policies to prevent users from modifying display scaling settings or locking down registry paths related to DPI can maintain consistency.
Testing with Controlled Accounts: Creating controlled user accounts configured with correct DPI settings provides a baseline to monitor if the issue resurfaces, thereby isolating the offending profile(s).
Adjusting RDP and Horizon Settings: Administrators are encouraged to review Remote Desktop client options, such as overriding client DPI scaling, and ensure Horizon Agent versions are up to date, despite the current lack of a clean fix from the agent side.
Vendor Collaboration: Engaging with Microsoft and VMware/Omnissa support teams helps identify if a patch or update addresses this DPI scaling irregularity.

Broader Implications in Remote Windows Environments

DPI and display scaling issues in Windows Server environments are increasingly critical, particularly with the proliferation of remote desktop and virtualized workspaces. Users connect via various endpoints with differing screen resolutions and scaling preferences, which must be harmonized by the server to maintain a smooth user interface.
The Windows Server 2022 case highlights the fragility of these DPI negotiation mechanisms, and reflects broader challenges when remote protocols, operating system updates, and user configurations collide. In enterprise settings, where multiple concurrent sessions operate with mixed profiles and client devices, such scaling glitches can generate significant support overhead and hinder productivity.

Final Thoughts and Best Practices

While no official permanent fix is publicly confirmed for this DPI scaling anomaly in Windows Server 2022 remote sessions, a methodical approach focused on registry management, user profile controls, and vendor communication is advisable. Preventative measures such as disabling user ability to modify DPI settings and scripting DPI enforcement at login can provide interim relief.
The phenomenon also serves as a reminder for IT professionals to carefully test updates and service deployments in controlled environments to detect such subtle but impactful issues before broad rollout. It underscores the importance of understanding DPI scaling intricacies in modern Windows environments, especially as virtualization and remote access technologies remain paramount.
Managing Windows Server 2022 DPI scaling issues requires a blend of registry vigilance, user profile caution, and collaboration with Microsoft and VMware. Through such diligence, administrators can navigate these scaling challenges to provide consistent, user-friendly remote desktop experiences.

This detailed overview is drawn from a recent IT community discussion describing the symptoms, diagnostics, and troubleshooting efforts around Windows Server 2022 DPI scaling problems via RDP and VMware Horizon (Omnissa). It synthesizes known findings and proposes practical management strategies to mitigate this frustrating issue,.

Source: Windows Server 2022 – DPI / Scaling broken via RDP & VMware Horizon

ChatGPT · Apr 27, 2025

Windows Server 2022 users administering Remote Desktop Services (RDS) environments via VMware Horizon (now Omnissa) and standard RDP have reported a vexing DPI scaling issue that disrupts normal visual experience. The problem manifests as an inconsistent display scaling, where interface and text elements appear either excessively large or tinily small depending on the client’s display resolution. This aberration reflects an incorrect DPI setting applied by the server’s Windows configuration, causing usability challenges in critical virtualized desktop and application delivery contexts.

Understanding the DPI Scaling Issue in Windows Server 2022

The affected environment typically includes a Windows Server 2022 Datacenter edition fully updated to the latest patches, operating as an RDS host for users connecting either through VMware Horizon or native Remote Desktop Protocol (RDP). Disconcertingly, the scaling distortion does not discriminate by connection type. Whether through VMware Horizon or classic RDP, users find that the interface scaling is misapplied from the server side.
A key diagnostic insight arises from checking the registry key:
HKCU\Control Panel\Desktop\WindowMetrics\AppliedDPI
In a normal working scenario, this AppliedDPI value remains at 96 decimal (0x00000060 hexadecimal), reflecting the standard 100% display scaling. However, on problematic systems, this rises to 120 decimal (0x00000078 hexadecimal), corresponding to 125% scaling. The elevated DPI setting causes UI elements to enlarge significantly, distorting the session appearance.
Notably, simply restoring the server from a backup yields a temporary fix, resetting the DPI scaling to the expected 100%. This indicates that the problem arises over time due to changes occurring during user sessions. Subsequent limitation of access to IT personnel suggests that certain user profiles or activities may inadvertently trigger DPI configuration changes.

Attempts and Observations to Resolve the Problem

Several approaches have been undertaken to diagnose and mitigate the issue:

Registry Comparison: Examining the AppliedDPI registry value between working and problematic user contexts highlighted the scaling difference.
User Profile Reset: Deleting all local user profiles did not yield lasting changes, indicating the problem might not be tied to simple profile corruption.
Reinstallation of Horizon Agent: Removing and reinstalling VMware Horizon Agent on the server did not affect the DPI behavior, hinting that the agent itself is not directly responsible.
Console Observation: Even on the ESXi hypervisor's VM console, the server lock screen displayed excessive scaling, though logging in locally restored expected visuals.
Display Settings: The native Windows display settings control panel did not reveal abnormal parameters or values.
Hardware Adjustments: Adding or reducing the VM's video RAM did not affect scaling, further focusing suspicion on software/registry or user profile variables.

Horizon support logs confirm that client devices correctly request their intended DPI scaling. Still, Windows Server apparently disregards these requests, forcibly overriding with a higher DPI setting. The fact that the lock screen in the console also appears scaled suggests that this DPI override occurs very early in the session lifecycle.

Potential Causes and Hypotheses

User Profile-Induced Settings: Since restricting access to IT personnel prevents reoccurrence, it’s plausible that certain users unknowingly alter DPI settings during sessions—possibly by adjusting display scaling through their session or compatibility settings on legacy applications.
Windows DPI Scaling Behavior in Remote Sessions: Windows Server 2022, like its predecessors, manages DPI scaling through layered mechanisms targeted at local, RDP, and virtual sessions. The interaction between client DPI requests (from Horizon or RDP clients) and server-side processing is complex. Servers may fallback to default or user profile registry settings, overriding client parameters.
Registry Persistence and Group Policy: The persistence of the AppliedDPI setting in the user hive (HKCU) indicates user-specific overrides. Lack of group policies or login scripts enforcing consistent DPI scaling permits undesirable modifications.
Software Bugs or System Updates: System updates may introduce regressions. Although the Horizon Agent was reinstalled, VMware or Microsoft may have pending patches addressing DPI scaling negotiation nuances. The possibility of a recently introduced bug cannot be excluded.

Broader Context of DPI Scaling in Windows and Remote Sessions

Windows uses several concepts to handle DPI in multi-monitor and remote environments:

System DPI Awareness: Legacy model where all displays and sessions assume a uniform DPI.
Per-Monitor DPI Awareness: Introduced starting Windows 8.1 and evolving through Windows 10 and later, where applications and sessions adapt dynamically to the DPI of the specific monitor.
Mixed-Mode DPI Scaling: Enables application UI elements and non-client window areas to scale suitably on DPI changes.

Despite these enhancements, many desktop applications (including legacy ones) do not fully support per-monitor or dynamic DPI adjustments, leading to scaling artifacts such as blurry or improperly sized UI.
In remote desktop environments, the DPI setting affects the session’s bitmap rendering. RDP and VMware Horizon both negotiate DPI during session setup; however, inconsistencies between client requested DPI and server-applied DPI can cause severe usability problems like those reported.

Practical Troubleshooting and Workarounds

To address this perplexing issue, system administrators can adopt the following strategic measures:

Audit and Enforce DPI Registry Settings: Monitor and set the AppliedDPI value within user profiles by exporting registry settings from a known good environment, and applying a login script or Group Policy Object (GPO) that resets HKCU\Control Panel\Desktop\WindowMetrics\AppliedDPI to 96.
Restrict User Access to DPI Settings: Use policies or environment lockdown methods to prevent users from changing display scaling settings, either through the Windows GUI or third-party tools.
Test with Controlled User Accounts: Create a new user account with enforced DPI settings and observe if the problem reoccurs, isolating whether specific user profiles trigger the shift.
Modify RDP / Horizon Client Settings: Configure remote desktop client connections to override DPI scaling on the client side. For example, in the RDP client, experiment with options like disabling display scaling or enabling "Use all my monitors," or adjusting the "Optimize for appearance" options. VMware Horizon settings might also expose DPI-related parameters.
Engage with Vendor Support and Community Forums: Collaborate with Microsoft and VMware/Omnissa support services for insights on known DPI scaling bugs and upcoming fixes. Community forums such as Spiceworks provide valuable peer experiences and suggested workarounds.
Monitor System and Event Logs: Increase logging verbosity around user profile loading and display settings changes. Identifying exact triggers of the DPI override can aid in troubleshooting.

Why This Issue Matters in Modern Remote Desktop Environments

As virtualization and remote desktop access become ubiquitous in the modern workplace, the user experience consistency across diverse devices and resolutions is critical. DPI scaling problems severely impair usability, especially for precision tasks or when using high-DPI displays such as 4K monitors.
The Windows Server 2022 DPI scaling conundrum illustrates the nuanced challenges facing administrators managing mixed client environments. While server updates and virtual desktop infrastructure (VDI) software continue to improve, subtle interactions between user profiles, Windows DPI policy, and remote desktop protocols can lead to frustrating regressions.
This scenario serves as a reminder that a holistic approach—balancing system configuration, user policy, application compatibility, and vendor collaboration—is required to maintain optimal display performance.

Conclusion

The DPI scaling issue encountered on Windows Server 2022 in RDS sessions accessed via VMware Horizon or RDP is a multifaceted problem rooted in incorrect DPI registry settings and possible user profile-induced overrides. Despite client devices requesting proper DPI scaling, server-side Windows settings prevail, leading to misrendered desktop environments.
Temporary fixes like server restoration and user restriction hint at the root cause lying in user profile behavior. Best practices involve rigorous registry monitoring, user policy enforcement, remote client configuration tweaks, and close coordination with vendor support to identify patches or updates addressing underlying DPI scaling logic in remote desktop sessions.
Windows administrators facing this challenge should adopt a systematic troubleshooting framework, leveraging automated scripting to enforce DPI consistency and restrict unauthorized scaling changes, thereby preserving a stable and visually consistent environment for all remote users.
By staying vigilant and methodical, IT teams can navigate this complex DPI scaling puzzle effectively, ensuring smooth scalability and productivity in their Windows Server 2022 RDS and VMware Horizon deployments.

References to community insights and detailed analysis on this DPI scaling issue were drawn from a recent Spiceworks thread chronicling affected users’ experiences and troubleshooting steps, and the broader context on Windows DPI scaling mechanisms from Windows 10 and beyond .

Source: Windows Server 2022 – DPI / Scaling broken via RDP & VMware Horizon

ChatGPT · Apr 27, 2025

Windows Server 2022 users running Remote Desktop Services (RDS) in environments utilizing VMware Horizon (now Omnissa) have recently been grappling with peculiar DPI scaling problems. This issue manifests when users connect to Windows Server 2022 either via standard Remote Desktop Protocol (RDP) or VMware Horizon clients; display elements appear blurry or incorrectly sized — either excessively large or notably small — signaling aberrations in Windows’ handling of DPI (Dots Per Inch) scaling. This perturbation disrupts a critical functionality in RDS environments, where accurate and consistent remote session display scaling is paramount for user experience and productivity.

The Nature of the DPI Scaling Issue

Administrators discovered that after connecting remotely to a Windows Server 2022 system, display scaling deviated from expected norms, influenced by the client device’s resolution but culminating in an erroneous DPI setting. These scaling anomalies were traced to the Windows registry, specifically the key at:
HKCU\Control Panel\Desktop\WindowMetrics
On problematic servers, the subkey "AppliedDPI" showed a value of 0x00000078 (120 decimal), corresponding to 125% scaling. Contrastingly, stable servers exhibited the default 100% scaling value of 0x00000060 (96 decimal). When this applied DPI setting drifts to 125%, everything on the remote desktop is rendered larger than intended; when it misses alignment with session parameters, it can become inconsistently sized or improperly scaled.
Interestingly, this issue was intermittent; restoring servers from backups temporarily reset scaling values to 100%, correcting the display anomaly. But after a few days and more user sessions, the problem recurred. When administrators limited access exclusively to IT personnel, the problem ceased, signaling that particular user profiles or actions might inadvertently alter the DPI scaling settings, possibly through local display adjustment or inadvertent registry changes.
Moreover, VMware Horizon logs confirmed that the client correctly requested appropriate scaling values, but Windows appeared to override and enforce a divergent DPI configuration, even affecting the ESXi console’s lock screen scaling display prior to user login.

Investigating Potential Causes

User-Specific or Profile-Induced DPI Changes

The observation that DPI scaling normalization persisted when the environment was restricted to IT access strongly suggests that certain user profiles or session activities are the culprits. This could arise from accidental modification of display settings within remote session environments or from logged-in users triggering DPI-related adjustments, intentionally or otherwise.
The persistence of incorrect AppliedDPI values despite deleting local user profiles and reinstalling Horizon Agents further complicates the root cause analysis. It suggests the DPI override is implemented somewhere beyond superficial user profile corruption or agent misconfiguration.

RDP and VMware Horizon Agent Interaction

Remote Desktop Protocol and VMware Horizon employ different mechanisms for negotiating display attributes such as resolution and DPI. While ideally, the client's requested scaling should be fully honored by the server session, logs illustrate Windows Server 2022 seemingly overrides these settings, suggesting either a bug in Windows' DPI handling under remote sessions or an incompatibility with how Horizon agents relay or apply DPI scaling hints.
Reinstallation of VMware Horizon Agents failed to resolve the anomaly, indicating the issue might not lie solely at the agent software layer, but potentially in deeper Windows Server 2022 DPI scaling logic or interaction between RDP/Horizon client requests and Windows session configuration.

Windows Server 2022 Updates and Potential Bugs

Given Windows Server 2022's frequent cumulative updates and security patches, there is potential that a recent update introduced an unintended regression affecting DPI scaling. Such regressions, while rare, have been documented in Windows environments where patching network or display subsystems imperfectly accommodates client DPI negotiation, forcing servers to adopt a non-default DPI setting.

Troubleshooting and Remediation Strategies

From the investigations and community-sourced insights, a range of diagnostic and mitigation approaches have emerged:

Registry Examination and Enforcement:
Administrators should audit and compare registry keys under HKCU\Control Panel\Desktop\WindowMetrics across user profiles for the AppliedDPI value.
Automate registry enforcement where necessary, e.g., via login scripts, to reset AppliedDPI to 96 (100%) upon user login.
Back up registry settings prior to modification for rollback if unintended consequences arise.
User Profile Management:
Evaluate user accounts and restrict access to those necessary while monitoring session behavior.
Research which user settings or actions might trigger DPI changes, including manual adjustments in Display Settings or accessibility options.
Test with clean or dedicated user accounts running under known-good settings to isolate offending configurations.
RDP and VMware Horizon Client Settings:
Review remote session options, specifically DPI and resolution override settings in RDP and Horizon clients.
Adjust options such as "Use all monitors" and "Optimize for best appearance" to observe effects on scaling.
Experiment with RDP's advanced settings to override client DPI scaling and enforce server-side scaling rules.
Group Policy Optimization:
Implement Group Policy Objects (GPOs) to lock down DPI scaling controls and prevent individual users from modifying display scaling.
Policies can also be utilized to prevent changes in key registry entries or restrict access to display scaling settings.
Vendor Collaboration and Patch Monitoring:
Engage VMware and Microsoft support channels for assistance, reporting the issue with detailed logs and reproduction steps.
Stay alert for vendor-released patches or guidance specifically addressing DPI scaling or Horizon-related display issues.
Monitor community forums such as Spiceworks and Windows community feedback for emerging workarounds or official fixes.

Broader Context: DPI Scaling in Remote Desktop Environments

Managing DPI scaling in remote sessions is an inherently challenging task due to the range of client devices (from high-DPI laptops and tablets to external monitors) and the interaction of multiple drivers and system components.
Windows desktop applications operate under one of several DPI awareness contexts—unaware, system-aware, or per-monitor DPI aware—which determine how UI elements scale on displays with varying pixel densities. This complexity multiplies in remote sessions since the server must interpret DPI requests from clients and adjust accordingly.
Moreover, legacy applications and system components often lack proper DPI independence, forcing Windows to use bitmap scaling—a workaround that can result in blurred or improperly sized interfaces.
Windows 10 and Server 2022 have incorporated improved DPI scaling support, but limitations remain, especially in mixed remote session environments. This is compounded by differing DPI implementations and bugs in RDP, Horizon agents, and session management layers.

Analysis: Risks and Implications

The scaling issue has significant implications:

User Experience: Incorrect scaling severely hampers usability, especially for productivity applications widely deployed in RDS environments.
Operational Disruption: Administrators may spend excessive time diagnosing and remediating what should be straightforward display configuration issues.
Security Risks: Frustration may drive users to circumvent controls or employ unauthorized tools to correct display problems.
Patch Management Challenges: New updates intended to improve security or performance may inadvertently exacerbate DPI handling flaws, underscoring the importance of controlled update testing.

Final Thoughts and Recommendations

The Windows Server 2022 DPI scaling problem via RDP and VMware Horizon exemplifies the fragility of remote session display management in evolving desktop and virtualization ecosystems. While the root cause often hinges on unexpected interactions between user profiles, registry settings, update regressions, and remote display protocols, systematic troubleshooting can identify and temporarily remediate the issue.
Administrators should adopt a multi-pronged strategy encompassing registry enforcement, policy-driven configuration control, client and server software alignment, and vigilant collaboration with vendors. Maintaining a clear log of changes and user behaviors leading to DPI shifts will also assist long-term resolution.
Given the complexity and potential for software regressions, waiting for formal patches from Microsoft or VMware may be necessary, but interim best practices can mitigate the user impact. The ongoing dialogue in community forums and vendor support channels remains invaluable for sharing discoveries and solutions.
Above all, understanding that DPI scaling in virtualized remote desktop environments is a nuanced challenge helps set realistic expectations and inspires methodical, detail-oriented problem-solving.

This detailed review and analysis of the Windows Server 2022 DPI scaling issue within RDS environments connected via VMware Horizon and RDP offers vital insights for system administrators desperate for solutions. It also fits within broader Windows ecosystem challenges surrounding high-DPI support, remote session display fidelity, and cross-product compatibility.
By staying informed, implementing disciplined configurations, and fostering community engagement, IT professionals can navigate this tricky area confidently until a durable server-side fix emerges,,,.

Source: Windows Server 2022 – DPI / Scaling broken via RDP & VMware Horizon

ChatGPT · Apr 27, 2025

Windows Server 2022 administrators running Remote Desktop Services (RDS) environments are encountering a perplexing and disruptive issue related to DPI (dots per inch) scaling when users connect via Remote Desktop Protocol (RDP) or VMware Horizon (rebranded as Omnissa). This problem manifests as inconsistent display scaling where UI elements appear either excessively large or too small depending on the client resolution. The root cause appears tied to Windows applying incorrect DPI settings, overriding the scaling values requested by the client software. As remote desktop computing becomes a linchpin for enterprise productivity, understanding and resolving this malfunction is critical.

Overview of the DPI Scaling Issue in Windows Server 2022 RDS Environments

The problem has been reported in environments running Windows Server 2022 Datacenter edition fully patched, coupled with VMware Horizon 8 (latest version, now Omnissa). Users connecting through either native RDP clients or Horizon clients find that after initial access, the desktop scaling is incorrect: some users see screen elements blown up disproportionately, while others see them cramped and minuscule.
Registry inspection reveals a crucial divergence. On affected servers, the registry key HKCU\Control Panel\Desktop\WindowMetrics\AppliedDPI exhibited a value of 0x00000078 (decimal 120), translating to a 125% scaling factor. Conversely, correctly scaling servers showed an AppliedDPI value of 0x00000060 (decimal 96), equating to the standard 100% scaling. This difference suggests that somewhere during the remote session initiation or user login process, Windows sets DPI information improperly for user sessions.
A peculiar symptom is that even at the ESXi console lock screen (outside of any RDP session), the display appears unusually scaled, indicating the problem percolates beyond just remote sessions. However, once logged in locally at the console, display scaling reverts to normal.
Attempts to fix the problem by restoring server images temporarily solve the issue, but after several days and user access, the DPI setting drifts again. Intriguingly, limiting access to only IT personnel on a freshly restored machine prevented the reappearance of the problem. This points toward a user profile or specific user action inadvertently triggering the DPI scaling override.
Efforts such as deleting user profiles and reinstalling the VMware Horizon Agent did not yield permanent remediation. Additionally, Windows' own Display Settings dialog did not reveal anomalous configurations, nor did adjustments in the virtual machine’s video RAM allocation.

Technical Insights: Scale Negotiation Failure Between Client and Windows Server

Logs from VMware Horizon clients show that the client correctly requests a particular DPI scaling during session setup; however, Windows on the server disregards this and imposes its own DPI setting. This behavior indicates a disconnect in the negotiation or enforcement mechanism between the client’s DPI preferences and Windows Server’s DPI management for remote sessions.
Windows internally manages DPI not only through local display settings but via per-user registry keys. Specifically, the AppliedDPI registry value under each user's hive affects font and UI scaling. In remote sessions, Windows Remote Desktop (RDP) and VMware Horizon agents have the responsibility of bridging client-side DPI requests with server-side implementations. Any bugs or misconfigurations in this chain—whether introduced by Windows updates or agent versions—can cause scaling mismatches.
Given that the Horizon Agent reinstall did not solve the issue, and that the problem occurs with both Horizon and native RDP sessions, the root cause likely lies in how Windows Server 2022 processes DPI scaling for remote sessions rather than the client agents themselves.

Similar Challenges in Windows DPI Scaling and Remote Desktop

Handling DPI scaling properly in Windows—especially in mixed display environments and remote sessions—has historically been complex. Windows provides various DPI awareness modes:

DPI Unaware: Applications receive no DPI handling and are simply bitmap scaled when resolution or DPI changes.
System DPI Aware: Applications are aware of the DPI of the primary display at launch time but do not dynamically adjust for scale factor changes.
Per-Monitor DPI Aware: Applications adapt their scaling dynamically when moved between displays with different DPIs.

Windows 10 initially lacked robust dynamic DPI scaling support, which led to many applications rendering blurry or incorrectly sized UI elements when display scale factors changed or when connected via remote sessions with mismatched DPI. Since then, Microsoft has introduced enhanced APIs like EnableNonClientDpiScaling and messaging such as WM_DPICHANGE to improve DPI awareness for desktop applications.
However, even with these improvements, inconsistencies remain, especially in RDS and virtual desktop infrastructure (VDI) contexts where client and server DPI settings must be negotiated and synchronized seamlessly. Incorrectly handled DPI awareness modes or registry overrides at a user or system level can cause persistent scaling problems in remote sessions.

Possible Origins and Causes in Windows Server 2022 Context

User Profile DPI Overrides: DPI settings are stored per-user in the registry. An affected user profile might be applying or resetting the DPI scaling to 125%, causing display distortions upon login. This matches the observation that limiting access to IT users (presumably with no erroneous settings) halts the issue’s recurrence.
Group Policy or Local Policy Changes: There is a possibility some profile or login script modifies DPI settings inadvertently or intentionally, triggering scaling overrides that affect the user experience.
Windows Server 2022 DPI Handling Bugs or Regression: Since Windows Server 2022 is relatively new and regularly updated, particular cumulative security or feature updates may introduce DPI scaling regressions under specific remote desktop scenarios.
Remote Desktop and Horizon Agent Implementation Gaps: The DPI synchronization features in Horizon agents or RDP may not be fully compatible or may be overridden by Windows behaviors, leading to DPI settings being ignored or forcibly altered post-session establishment.
Display Driver or Virtual Display Adaptation Issues: The fact that scaling appears broken even on ESXi console’s lock screen suggests a possible interaction between virtualization drivers, display hardware emulation, and Windows DPI scaling subsystems.

Recommended Troubleshooting Steps and Partial Workarounds

Registry and User Profile Analysis

Inspect Each User’s DPI Registry Settings: Compare HKCU\Control Panel\Desktop\WindowMetrics\AppliedDPI in profiles to identify any that force incorrect DPI values.
Scripting Enforcement of Correct DPI: Implement login scripts that forcibly set the AppliedDPI registry value to 96 (100%) for all users, resetting any rogue DPI overrides.
Profile Reset or Re-creation: Since deleting and recreating user profiles alone did not work, focus might shift towards group policies or login scripts affecting the DPI registry keys post-login.

RDP and Horizon Client/Agent Configuration

Override Client DPI Scaling in RDP Settings: Experiment with RDP advanced settings for client scaling override to enforce server-side DPI scaling or vice versa.
Keep Horizon Agent Updated: Monitor VMware (Omnissa) releases for fixes related to DPI handling. Coordinate with vendor support for diagnostics.
Verify Use all my monitors and Optimize for best appearance Settings: Correct multi-monitor and visual settings can influence DPI behavior.

Group Policy and System Settings

Implement Group Policies to Lock DPI Scaling Settings: Prevent users or applications from changing DPI-related registry keys or display scaling.
Restrict Display Scaling Changes: Block access to Windows display settings for scaling, especially in RDS environments.

Monitor Logs and Windows Event Viewer

Enable Detailed Logging for Display and Remote Desktop Events: Look for correlated events when DPI scaling changes or when user profiles are loaded.
Track User Sessions and Identify Trigger Patterns: Note if DPI reversion aligns with particular user logins or application launches.

Temporary Use of Server Restore Points

Restore Known Good States: Server restoration resets DPI scaling but is only a stopgap as settings drift back.
Limit User Access Post-Restore: Only grant access to profiles verified clean of DPI overrides to maintain correct scaling.

Broader Lessons and Considerations for Remote Desktop Environments

The Windows Server 2022 DPI scaling issue underscores broader challenges in supporting high DPI and mixed DPI display environments within virtual and remote desktop infrastructures. Enterprises must:

Regularly audit and clean user profiles to avoid rogue visual setting persistence.
Establish clear policies around display scaling alterations.
Rigorously test Windows updates that affect Remote Desktop Services and display components before production deployment.
Engage vendor support (Microsoft and VMware/Omnissa) to report issues and obtain patches.
Educate users to avoid accidental or intentional DPI scaling changes.
Consider alternative client configurations or policies that enforce server or client DPI dominance for consistent user experience.

Context and Similar Issues in Windows Ecosystem

This DPI problem is part of a series of DPI and remote desktop troubles reported by the community over time. Past Windows 10 and Windows 11 versions have exhibited DPI scaling bugs, no doubt compounded by the complexity of per-monitor DPI awareness, bitmap scaling fallback, and registry overrides. Some applications and UI components still struggle to handle dynamic DPI changes, especially under RDP constraints.
Mixed-mode DPI handling introduced in Windows 10 Anniversary Update and later attempts to improve DPI awareness try but often fall short in virtualized or multi-monitor scenarios. Apps like Notepad had to be manually modified to properly scale non-client areas and fonts on DPI shifts, highlighting inherent platform complexities.
Windows 11 and 2022 Server editions continue to wrestle with similar challenges, especially as remote work environments proliferate.

Conclusion: Navigating the DPI Scaling Challenge in Windows Server 2022 RDS

The DPI scaling malfunction in Windows Server 2022 RDS sessions accessed via Horizon or RDP represents a combination of user profile configurations, Windows DPI processing, and remote display protocol misalignments. With registry keys like AppliedDPI unexpectedly shifting, users experience distorted display sizes, leading to usability and productivity impacts.
Fixes require a blend of direct registry enforcement, controlled user access, configuration tightening, and vendor collaboration. Administrators should proactively monitor DPI-related registry settings, impose group policies to restrict scaling changes, and engage with Microsoft and VMware for patches or updates.
Maintaining consistent, crisp visual display in remote desktop environments remains a technically challenging, evolving frontier. Through vigilant troubleshooting, configuration management, and community sharing, IT professionals can mitigate these disruptions and help pave the way for stable future improvements.
By staying methodical and well-informed, system administrators can better ensure that once scaled correctly, their remote desktops stay that way — keeping DPI frustrations at bay in an increasingly virtual workspace.

This analysis and recommendations are grounded in public community reports, official logs from Horizon clients, and accumulated Windows DPI scaling knowledge, reflecting widespread user experience and best practices from WindowsForum.com and Spiceworks communities.

Source: Windows Server 2022 – DPI / Scaling broken via RDP & VMware Horizon

ChatGPT · Apr 27, 2025

Windows Server 2022 environments leveraging Remote Desktop Services (RDS), especially when accessed through VMware Horizon (rebranded as Omnissa), are currently facing perplexing DPI scaling issues affecting display rendering via RDP sessions. This problem is significant because it undermines user experience and productivity, causing screen elements to appear either excessively large or inappropriately small depending on resolution and client device. Such erratic behavior is symptomatic of Windows applying incorrect DPI settings during remote sessions, despite client-side requests signaling the intended scaling factor.

Understanding the DPI Scaling Problem in Windows Server 2022 RDS

In an affected setup using VMware Horizon 8 (or Omnissa) paired with Windows Server 2022 Datacenter fully patched, users experience scaling failures during remote sessions. Whether the connection is made via Horizon or traditional RDP, the server appears to override the proper DPI scaling, leading to distorted visuals. For example, Windows registry inspections at the key HKCU\Control Panel\Desktop\WindowMetrics reveal mismatched AppliedDPI values—problematic servers register a value of 120 decimal (0x78 hex), which corresponds to a 125% scaling factor, whereas stable systems reflect the standard 96 decimal (0x60 hex) equating to 100% scaling. This discrepancy points directly to DPI override as the cause of the display anomalies.
A notable detail is that restoring the server from backup resets the scaling behavior to normal temporarily, but the problem tends to reoccur after several days or user interactions. Interestingly, restricting logins to only IT personnel has prevented recurrence on a restored system, hinting strongly at the possibility that specific user profiles or user actions might be inadvertently triggering the DPI scaling changes through either manual adjustment or software interactions.

Investigative Steps and Technical Observations

Several approaches have been taken to diagnose and mitigate the issue, including:

User Profile and Registry Examination: Analysts reviewed multiple user profiles and the corresponding registry keys affecting DPI. Despite local user profile deletions, the problem persisted, suggesting the DPI scaling override is either reintroduced via other means or cached outside user profiles.
Horizon Agent Reinstallation: To rule out corrupted remote display agent components, the Horizon agent was uninstalled and freshly reinstalled without resolving the DPI override.
Server Console Behavior: Even directly via the ESXi console, the Windows lock screen exhibits overscaling, but once fully logged in, the display appears correct. This suggests the DPI scaling issue might be applied very early during session start or related to user session initialization logic.
Display Settings and Hardware Resources: Standard Windows display settings showed no anomalies; adjusting the VM's video memory allocated also did not influence the issue, further isolating this to software-level DPI handling.
DPI Negotiation Logs: VMware Horizon logs confirm that clients request the correct scaling settings, meaning the server ultimately decides to ignore the client preference and enforce an inaccurate DPI setting.

Technical Analysis: DPI Handling and Display Scaling in Remote Sessions

Windows manages DPI settings based on both system-wide and user-specific configuration, including registry keys under HKCU\Control Panel\Desktop\WindowMetrics. The AppliedDPI value controls the DPI scaling percentage (96 for 100%, 120 for 125%). In remote desktop contexts, the DPI scaling can be negotiated by the client-server pair to best match client display characteristics.
However, the configuration becomes complex when factoring per-monitor DPI awareness, session-based DPI settings, and overriding policies. Windows Server 2022 and its associated RDS infrastructure, combined with remote access technologies like VMware Horizon, can sometimes fail to harmonize these DPI requests correctly. The observed root cause appears to be Windows itself (or any applied patches) overriding requested DPI settings after login, regardless of client signals.
This behavior may relate to known shortcomings in earlier Windows DPI management models (System DPI Awareness and Per-Monitor DPI Awareness), which historically struggled with dynamic or multipart display environments and remote session scaling. Such legacy limitations mean desktop applications or system UIs might not adapt smoothly to scale changes during session initialization or post-login phases.

Troubleshooting and Remediation Strategies

For administrators encountering this DPI scaling conundrum, several practical steps and strategies have emerged from community discourse and technical investigations:

Baseline Registry Setting Enforcement:
Export and document AppliedDPI and related DPI registry keys after restoring a known-good system state.
Deploy scripts or Group Policy Object (GPO) login scripts to enforce AppliedDPI=96 (100%) to combat unintentional overrides.
User Profile Auditing:
Monitor which user accounts cause AppliedDPI to revert to 120 or other unintended values.
Create test profiles with locked DPI settings to isolate any rogue profile changes.
Group Policy Management:
Implement Group Policies that restrict users from changing display scaling settings to maintain consistency.
Consider locking down the related registry paths to prevent user modification of DPI-relevant values.
RDP and Horizon Client Settings:
Review RDP options to enable or disable DPI scaling overrides, ensuring that client requests for DPI are respected.
Try toggling settings like "Override DPI scaling" or "Use all my monitors" to observe their influence.
Vendor and Community Engagement:
Report the issue to VMware/Omnissa and Microsoft support, including detailed logs.
Leverage peer forums such as Spiceworks where professionals share workarounds and collective intelligence.
Update Vigilance:
Monitor Windows Server 2022 cumulative updates for patches addressing DPI or RDS scaling.
Validate Horizon agent updates or patches that might rectify DPI negotiation or session scaling.

Context: DPI Scaling Challenges Beyond Windows Server 2022

The fundamental challenge of DPI scaling in remote or virtualized desktop environments is not unique to Windows Server 2022. Earlier Windows versions, including Windows 10 and Windows Server 2019, have exhibited similar issues, especially when shifting multiple monitor configurations or when using remote desktop protocols.
Windows introduced various DPI awareness modes:

System DPI Awareness: Assumes a single DPI for the entire session, suitable for static display environments but not dynamic multi-display setups.
Per-Monitor DPI Awareness: Enables applications to dynamically adapt to individual monitor DPI settings but requires explicit support from applications and OS subsystems.

Despite these modes, applications and Windows system components sometimes fail to properly scale UI elements like non-client window areas, fonts, and dialogs when DPI changes occur or when sessions are virtualized over RDP/Horizon. This leads to blurry or disproportionately scaled interfaces.
Microsoft's enhancements with Windows 10 Anniversary Update and later versions introduced mixed-mode DPI scaling, thread-specific DPI awareness, and APIs such as EnableNonClientDpiScaling to help developers achieve better scaling fidelity. Still, the complexity often results in compatibility gaps that surface prominently in enterprise remote desktop deployments.

Broader Implications and Best Practices

The mishandling of DPI scaling in RDS and VMware Horizon environments reflects broader IT challenges:

User Experience: Poorly scaled sessions degrade usability, increasing eye strain and operational errors during remote work.
IT Overhead: Repeated back-and-forth troubleshooting of DPI settings drains resources and delays critical tasks.
Software and Update Risks: As Microsoft pushes security patches and feature updates, unintended side effects on display and RDP functions remain risks requiring careful change management and monitoring.

Administrators are advised to adopt a vigilant and methodical approach, including standardized user profiles, controlled patch testing, and proactive engagement with vendor support.

Conclusion

The Windows Server 2022 DPI scaling anomaly in VMware Horizon and RDP sessions underscores the nuances and technical hurdles in delivering seamless remote user experiences across heterogeneous display environments. At the core lies the conflict between client-requested DPI settings and server-applied overrides, modulated by registry configurations and system behaviors.
A temporarily effective but unsustainable fix involves restoring server images and limiting user access—both highlighting the need for deeper understanding and a systematic solution. Until vendors release definitive patches, administrators must implement registry-based lockdowns, monitor affected user profiles, and optimize RDP and Horizon client settings.
Through collaborative troubleshooting, documenting patterns, and leveraging community insights, Windows professionals can better navigate the DPI scaling labyrinth and maintain resilient, user-friendly remote desktop infrastructures.
By continuing to track vendor updates and pursuing best practices in remote session configuration, enterprises can mitigate DPI-related frustrations and ensure clarity and consistency in their virtual desktop environments.

This overview draws on detailed community reports and technical analysis of Windows Server 2022 DPI scaling issues with VMware Horizon, as documented in professional forums and knowledge bases.

Source: Windows Server 2022 – DPI / Scaling broken via RDP & VMware Horizon

ChatGPT · Apr 27, 2025

Windows Server 2022 users operating remote desktop environments via VMware Horizon or traditional RDP have been encountering a perplexing and disruptive DPI scaling issue. This problem causes the display scaling to malfunction unpredictably: sometimes, screen elements appear excessively large, other times minuscule, all seemingly triggered by incorrect DPI settings applied after login. Despite the environment requesting proper scaling values from clients, Windows overrides these, resulting in inconsistent and frustrating remote desktop experiences.

Understanding the Issue in Windows Server 2022 RDS Environments

The affected environment typically features:

VMware Horizon 8 (latest version, now Omnissa)
Windows Server 2022 Datacenter fully updated

Symptoms include display scaling that shifts erratically on connection via Horizon or standard RDP. The problem is not tied specifically to either display resolution or client device and manifests as either "overscaled" or "underscaled" display contents.
An investigation reveals that this display inconsistency correlates strongly with Registry DPI values under:
HKCU\Control Panel\Desktop\WindowMetrics
where on problematic instances, the key AppliedDPI is set to 120 (0x00000078) — representing 125% scaling. By contrast, stable systems exhibit this value as 96 (0x00000060), which aligns with the expected 100% scaling.
Interestingly, this DPI shift occurs over time after server restoration from backup defaults. When the server is restored and limited exclusively to IT users, the problem does not recur, suggesting that a particular user profile or an unintentional user action might be triggering the undesired DPI scaling adjustment.

Attempts and Observations to Address the Problem

Several troubleshooting steps have been employed:

Restoring the server temporarily resets the issue until some user interaction possibly triggers the scaling change again.
Restricting access to IT only prevents reappearance.
Checking Horizon logs confirms that clients properly request the correct DPI scaling, but Windows still applies overriding settings.
Deleting user profiles to remove user-specific registry customizations has minimal or no effect.
Reinstalling Horizon Agent fails to solve the issue, signalling that the problem may not lie with the RDS agent layer itself.
Checking via ESXi console shows unusual scaling present even before login at the lock screen, further implicating system-level DPI settings.
Adjusting virtual RAM parameters in the VM does not impact DPI scaling.

Windows’ own display settings UI doesn’t surface any unusual DPI configurations, making diagnosis less straightforward.

Potential Root Causes

User Profile DPI Settings: Given the user-specific registry key differences and the problem's correlation with user logins, one likely cause is that some user(s) or user profiles are modifying DPI settings — whether accidentally or as part of their session activities.
Windows DPI Scaling Behavior in Remote Sessions: Windows Server 2022 appears to apply DPI settings somewhat differently for local versus remote sessions. Despite client requests logged by Horizon, Windows applies its own scaling value, potentially triggered by user session or profile policies.
Update-Induced Bugs or Regression: The issue might stem from recent Windows Server updates that unintentionally modified how DPI scaling is managed, particularly in RDP or Horizon sessions.

Broader Context and Similar Issues

This Windows Server 2022 DPI scaling issue echoes broader challenges reported around remote desktop and DPI handling in multi-monitor, virtualized, or remote environments:

Developers have long struggled to get per-monitor DPI scaling stable, especially when switching monitors or resolutions.
Mixed-DPI environments impose complexity on scaling dialogs, font sizing, and non-client window areas in Windows applications (e.g., as detailed in font dialogs and window placement handling).
Windows’ DPI scaling awareness contexts cause varied behaviors in dialogs and fonts depending on the scale factor of the primary display or system context.
Remote Desktop Protocol (RDP) and vendor extensions like VMware Horizon agents handle DPI scaling negotiations differently and can conflict with local Windows settings.
Some recent Windows updates introduced RDP session freeze or disconnection issues, showing how complex remote display management can be and how fragile remote session stability remains under frequent updates.

What System Administrators and IT Teams Can Do

While waiting for definitive Microsoft or VMware fixes, some practical steps can be taken to mitigate or diagnose this issue:

1. Monitor and Enforce Registry DPI Values

Create scripts or Group Policies to check the AppliedDPI registry value on user login and enforce it to 96 to maintain 100% scaling:

Export baseline registry DPI settings.
Use login scripts or scheduled tasks to reset AppliedDPI to 96.
Create or enforce Group Policy Objects (GPO) that restrict users from changing scaling settings.

2. Segregate Problematic User Profiles

Since limiting access to IT users prevented the issue occurring, identify and isolate users whose profiles might be triggering the DPI override.

Test with newly created user accounts applying baseline DPI.
Gradually reintroduce users or profile changes to identify the culprit.

3. Adjust RDP and Horizon Client Settings

Experiment with client-side display settings:

Disable or enable DPI scaling override options in RDP connections.
Adjust Horizon Agent display settings, although reinstallations seem ineffective.
Test configuration options around high DPI aware scaling.

4. Increase Logging and Monitor Session Behavior

Enhance Windows Event logging and Horizon logs around display settings changes at user session start:

Identify if particular user actions, applications, or configurations coincide with the DPI value change.
Look for non-obvious triggers such as policies applied on login, remote control sessions, or third-party utilities.

5. Collaborate with Vendor Support and Community

Continue engagement with VMware/Omnissa and Microsoft support channels:

Report detailed logs and findings.
Monitor for patches specifically addressing DPI or display scaling in RDS environments.
Use community forums like Spiceworks and WindowsForum.com to share experiences and gather potential workarounds.

Implications for Remote Desktop Environments and User Experience

As virtual desktop infrastructure (VDI), Remote Desktop Services (RDS), and remote work ramp up, ensuring consistent DPI scaling across diverse endpoint devices is critical for usability.

DPI issues impact readability, UI usability, and perception of performance.
Users might suffer from eye strain, reduced productivity, or application layout issues.
Administrators face the challenge of balancing user flexibility with environment consistency.
Vendor compatibility and Windows update cycles can break remote session behaviors unexpectedly.

Future Outlook and Conclusion

The Windows Server 2022 RDS DPI scaling issue remains a tricky problem rooted in interplay between user profiles, Windows DPI management, and remote desktop agents. Temporary measures like server restoration or access limitation offer relief but do not solve the root cause.
Long-term resolution will likely involve:

Microsoft addressing DPI session scaling in updates or hotfixes.
VMware updating Horizon Agent to better integrate DPI negotiation and enforcement.
IT admins adopting tighter user profile management and policy enforcement.

Meanwhile, administrators must adopt methodical monitoring and intervention strategies to maintain service quality and system usability.
This case highlights the complexities of modern remote desktop environments where legacy Windows internals and new virtualization approaches intersect. Persisting with community engagement and vendor collaboration remains essential to navigate and resolve these nuanced display challenges.
By understanding the DPI scaling landscape, correctly interpreting registry settings, and systematically isolating user-specific causes, Windows Server 2022 administrators can reduce disruptions and improve remote session consistency while awaiting a permanent patch from key vendors.
Happy troubleshooting, and may your DPI settings stay stable and correct!

Source: Windows Server 2022 – DPI / Scaling broken via RDP & VMware Horizon

ChatGPT · Apr 27, 2025

Windows Server 2022 users running Remote Desktop Services (RDS) environments with VMware Horizon (recently rebranded as Omnissa) have encountered a perplexing and frustrating display scaling issue manifesting through Remote Desktop Protocol (RDP) and Horizon client sessions. The core symptom involves the desktop appearing incorrectly scaled — either excessively large or abnormally small — depending on the resolution of the connecting client. This behavior is traced to Windows applying an incorrect DPI (dots per inch) setting during remote sessions. In practical terms, users see distorted visuals, making routine tasks difficult and causing potential productivity losses in virtualized or remote environments.

The Issue in Detail: Misapplied DPI Scaling in Windows Server 2022 RDS

Environment specifics where this scaling bug has been reported include Windows Server 2022 Datacenter with all current updates installed, and VMware Horizon 8 (now Omnissa) as the connection broker. The problem is reproducible via both Horizon client and standard RDP connections.
At the registry level, the exact anomaly is linked to the HKCU\Control Panel\Desktop\WindowMetrics\AppliedDPI value for user sessions. In healthy systems that display correctly scaled desktops, AppliedDPI remains at the standard 96 (decimal), corresponding to 100% scaling. In contrast, affected sessions incorrectly show an AppliedDPI of 120 (hex 0x78), or 125% scaling.
This discrepancy causes elements on the screen to appear either oversized or undersized, creating usability issues:

Restoring the server from a backup temporarily resolves the issue, but the DPI distortion returns within a few days.
Restricting logins to IT staff alone prevents the problem from reappearing, pointing toward a particular user or user action as a potential trigger.
VMware Horizon logs confirm that the correct scaling is requested by the client but is overridden or ignored by Windows once the session starts.
Even the ESXi console view of the server’s lock screen displays the scaling issue before user login, yet displays normally after console login, indicating that the problem is systemic in how Windows applies DPI during graphical session initialization.
Attempts to reset profiles, reinstall Horizon agents, adjust virtual RAM, or manipulate Windows display settings locally have all failed to correct the problem.

Investigating Causes: User Profiles, DPI Settings, and Remote Session Behavior

The core issue appears rooted in how Windows Server 2022 manages DPI scaling per user session in an RDS context involving remote clients with diverse display resolutions. The AppliedDPI registry value alters the desktop scaling factor — but while the Horizon client correctly requests a scaling factor, Windows seemingly disregards that request and applies its own default or previously stuck DPI setting.
This leads to these probable contributing factors:

User-Initiated DPI Changes: Since limiting login access to IT users halted the problem temporarily, it suggests a particular user profile or action sets DPI scaling locally or triggers a registry override. DPI can be modified accidentally through user display settings or remotely via certain applications. The persistence of the issue after deleting local profiles hints that roaming or mandatory profiles might contribute to this odd behavior.
RDS and Horizon Agent DPI Handling: Remote Desktop Protocol and VMware Horizon agents differ from local console sessions in DPI processing. While the client negotiates DPI scales during connection establishment, server-side DPI awareness and update mechanisms may fail to interpret or honor these settings consistently in Windows Server 2022.
Windows Server 2022 Software Bugs or Update Regressions: Since Windows Server continuously rolls out patches, it is plausible that recent cumulative updates or security patches inadvertently affected DPI handling in remote sessions. Such regressions could cause override of user-requested DPI settings with incorrect defaults.

Troubleshooting Strategies and Workarounds

IT administrators facing this DPI scaling conundrum can adopt a methodical approach combining technical and administrative remedies:

Registry and Profile Monitoring

Monitor the HKCU\Control Panel\Desktop\WindowMetrics\AppliedDPI value across all user profiles, especially those used during remote sessions.
Document and script periodic enforcement of a baseline DPI value (96) by applying registry modifications at user logon.
Create controlled test user accounts to verify DPI behavior in RDP and Horizon sessions.

Group Policy and RDS Configuration

Utilize Group Policy to restrict users from changing DPI and display scaling settings, thereby locking down configurations.
In the RDP client settings, experiment with options to override client DPI scaling or enforce server-side scaling parameters.
Maintain the Horizon Agent updated, and monitor official VMware/Omnissa patches addressing DPI scaling problems.

Vendor Collaboration and Community Engagement

Report the issue to Microsoft support and VMware/Omnissa to verify ongoing investigations or upcoming patches addressing DPI scaling.
Engage with user communities (such as Spiceworks) where peer professionals exchange possible workarounds or similar case studies.

Logging and Diagnostic Analysis

Increase logging of remote session events via Windows Event Viewer and Horizon logs to correlate DPI changes with session events or user actions.
Identify patterns regularizing the DPI reversion, such as specific users, software, or time intervals.

Broader Implications and Best Practices for Remote Desktop Environments

This DPI scaling issue in Windows Server 2022 RDS environments highlights the complexities of managing high-DPI user experiences across virtual and remote sessions, especially as organizations increasingly embrace hybrid and virtual work models. The user interface consistency and legibility remain critical for productivity and user satisfaction.
Administrators should consider the following general best practices:

Regularly clean and standardize user profiles and roaming profile settings to prevent unintended DPI overrides.
Establish rigorous testing environments for Windows updates before wide deployment to catch regressions in DPI or remote session handling.
Foster ongoing dialogue with Microsoft and VMware to report bugs and receive staging hotfixes or updates.
Prepare fallback options such as local console access or alternative remote management tools when DPI and display scaling issues affect session usability.

Conclusion: Navigating a Modern DPI Scaling Challenge on Windows Server 2022

The DPI scaling issue over RDP and VMware Horizon on Windows Server 2022 presents a challenging puzzle requiring a coordinated troubleshooting strategy involving registry inspection, user profile control, remote connection settings tuning, and vendor collaboration. While temporary fixes like server restoration and limiting access offer short-term relief, the problem’s root cause likely involves a complex interplay between user actions and how Windows Server 2022 processes DPI scaling in remote sessions.
For IT professionals, persistence in monitoring, configuring group policies, and working closely with software vendors will be key to overcoming the disruption. Keeping informed of updates and patches from Microsoft and VMware, along with community knowledge sharing, will help mitigate these display scaling issues as Windows Server 2022 continues to mature in enterprise deployments.
By carefully managing DPI registry settings and remote desktop configurations, organizations can maintain reliable and well-scaled desktop experiences essential for modern virtualized infrastructures.

This article responds to a detailed community report of the DPI scaling issue and synthesizes key findings and recommended best practices with insights into the underlying technology challenges. For practical application and detailed implementation guidance, administrators should refer to official Microsoft and VMware documentation and stay engaged with technical communities for emerging fixes.

Source: Windows Server 2022 – DPI / Scaling broken via RDP & VMware Horizon

Navigation section

Resolving DPI Scaling Issues in Windows Server 2022 via RDP & Horizon

Understanding the Environment and the Issue​

Key Observations:​

Investigating the Root Causes​

1. DPI Settings and Registry Tweaks​

2. RDP and Horizon Agent Behavior​

3. Potential Software Bugs or Update-Induced Changes​

Strategies to Diagnose and Resolve the Issue​

A. Registry and Profile Checks​

B. RDP and Horizon Configuration Adjustments​

C. Engage Vendor and Community Support​

D. Monitor and Document​

Broader Implications for Windows RDS and Remote Display Technologies​

Practical Workaround: A Step-by-Step Guide​

Conclusion​

AI

The DPI Scaling Anomaly in Windows Server 2022​

Diagnosing the Root Cause​

Contextualizing DPI and Remote Sessions​

Potential Causes and Speculations​

Troubleshooting and Mitigation Strategies​

1. Registry Auditing and Enforcement​

2. User Profile Controls​

3. RDP and Horizon Configurations​

4. Vendor Collaboration and Community Support​

5. Monitor Windows Server Updates​

Broader Implications for Remote Display Environments​

Conclusion​

AI

Understanding the Environment and Problem​

Investigating the Root Causes​

1. User-Specific Registry Changes​

2. RDP and VMware Horizon Agent Interactions​

3. Patch-Induced or Software Bugs​

Troubleshooting and Remediation Strategies​

A. Registry and Profile Management​

B. RDP and Horizon Settings​

C. Vendor and Community Support​

D. Diagnostic Logging and Pattern Analysis​

Broader Implications for Remote Desktop and DPI Scaling​

Practical Workaround Guide​

Conclusion​

AI

The DPI Scaling Problem in Windows Server 2022 RDS Environments​

Technical Insights: Causes and Mechanisms Behind DPI Anomalies​

Troubleshooting and Mitigation Steps​

1. Monitor and Audit DPI Registry Settings​

2. Restrict User Modifications​

3. Adjust Remote Desktop Client and Horizon Agent Settings​

4. Isolate User Impact​

5. Monitor Windows Update and Patch Notes​

6. Consider Temporary Workarounds​

Broader Context: DPI Scaling Challenges in Remote Desktop and Virtualization Environments​

Conclusion​

AI

The Scaling Problem in Windows Server 2022 RDS Sessions​

Attempts at Resolution and Observations​

Technical Analysis of Root Causes​

Recommended Troubleshooting and Mitigation Approaches​

Broader Implications for Remote Desktop Environments​

Conclusion​

AI

The Nature of the DPI Scaling Issue​

Investigations and Tried Solutions​

Root Causes: User Actions or System Bugs?​

Broader Context: DPI Scaling Challenges in Windows Remote Environments​

Recommended Mitigation Strategies for IT Professionals​

The Importance of DPI Scaling Stability in Remote Work​

Conclusion​

AI

Context and Environment​

Technical Investigation and Findings​

Broader Technical Background on DPI Scaling​

Potential Root Causes and Hypotheses​

Troubleshooting and Mitigation Strategies​

1. Registry and User Profile Analysis​

2. Examine and Adjust RDP and VMware Horizon Settings​

3. Enforce Group Policies to Prevent Unwanted Scaling Changes​

4. Engage Vendor Support Continuously​

Understanding the Environment and the Issue

Key Observations:

Investigating the Root Causes

1. DPI Settings and Registry Tweaks

2. RDP and Horizon Agent Behavior

3. Potential Software Bugs or Update-Induced Changes

Strategies to Diagnose and Resolve the Issue

A. Registry and Profile Checks

B. RDP and Horizon Configuration Adjustments

C. Engage Vendor and Community Support

D. Monitor and Document

Broader Implications for Windows RDS and Remote Display Technologies

Practical Workaround: A Step-by-Step Guide

Conclusion

The DPI Scaling Anomaly in Windows Server 2022

Diagnosing the Root Cause

Contextualizing DPI and Remote Sessions

Potential Causes and Speculations

Troubleshooting and Mitigation Strategies

1. Registry Auditing and Enforcement

2. User Profile Controls

3. RDP and Horizon Configurations

4. Vendor Collaboration and Community Support

5. Monitor Windows Server Updates

Broader Implications for Remote Display Environments

Conclusion

Understanding the Environment and Problem

Investigating the Root Causes

1. User-Specific Registry Changes

2. RDP and VMware Horizon Agent Interactions

3. Patch-Induced or Software Bugs

Troubleshooting and Remediation Strategies

A. Registry and Profile Management

B. RDP and Horizon Settings

C. Vendor and Community Support

D. Diagnostic Logging and Pattern Analysis

Broader Implications for Remote Desktop and DPI Scaling

Practical Workaround Guide

Conclusion

The DPI Scaling Problem in Windows Server 2022 RDS Environments

Technical Insights: Causes and Mechanisms Behind DPI Anomalies

Troubleshooting and Mitigation Steps

1. Monitor and Audit DPI Registry Settings

2. Restrict User Modifications

3. Adjust Remote Desktop Client and Horizon Agent Settings

4. Isolate User Impact

5. Monitor Windows Update and Patch Notes

6. Consider Temporary Workarounds

Broader Context: DPI Scaling Challenges in Remote Desktop and Virtualization Environments

Conclusion

The Scaling Problem in Windows Server 2022 RDS Sessions

Attempts at Resolution and Observations

Technical Analysis of Root Causes

Recommended Troubleshooting and Mitigation Approaches

Broader Implications for Remote Desktop Environments

Conclusion

The Nature of the DPI Scaling Issue

Investigations and Tried Solutions

Root Causes: User Actions or System Bugs?

Broader Context: DPI Scaling Challenges in Windows Remote Environments

Recommended Mitigation Strategies for IT Professionals

The Importance of DPI Scaling Stability in Remote Work

Conclusion

Context and Environment

Technical Investigation and Findings

Broader Technical Background on DPI Scaling

Potential Root Causes and Hypotheses

Troubleshooting and Mitigation Strategies

1. Registry and User Profile Analysis

2. Examine and Adjust RDP and VMware Horizon Settings

3. Enforce Group Policies to Prevent Unwanted Scaling Changes

4. Engage Vendor Support Continuously

5. Document and Monitor Session Events

6. Consider OS Patching and Update Rollbacks

Broader Implications for Remote Desktop Display Management

Conclusion

Environment and Manifestation of the DPI Scaling Issue

Troubleshooting Efforts and Insights

Deeper Technical Analysis

Practical Recommendations for Mitigating the Issue