Dentrix UI Fix: Restoring Cut Off Windows and Missing Buttons

6 min. read

The Ticket: The "Invisible" Print Button

A usual "can't print" ticket... The front desk staff can't print Patient Visit Forms or run Day Sheets. But this time its not a driver! The Office Manager window opens, but the bottom section, where the "OK" and "Print" buttons live, is completely cut off by the Windows taskbar. The users are frustrated, trying to drag the window up, but it’s stuck. Tier 1 usually tries changing the monitor resolution, which just makes everything look like a blurry mess. This isn't a resolution issue; it's a High DPI scaling conflict between legacy Dentrix code and modern high-resolution displays.

Pre-Flight Check

• Permissions: Local Administrator.
• Tools: Windows File Explorer, Dentrix Office Manager.
• Impact: Low - Only affects the visual rendering of the application. No database impact.

The Solution: Adjust High DPI Scaling

This fix forces the Windows Desktop Window Manager (DWM) to take over the "drawing" of the window size, rather than letting the Dentrix application guess based on outdated fixed-pixel logic.

Step-by-Step Instructions

1. Locate the Executable: Right-click the Office Manager icon on the desktop (or the CustApp.exe in the Dentrix folder) and select Properties.
2. Compatibility Settings: Click on the Compatibility tab at the top of the window.
3. DPI Settings: Click the button near the bottom labeled Change high DPI settings.
4. Apply the Override: Under the "High DPI scaling override" section, check the box: Override high DPI scaling behavior.
5. Scaling Choice: In the dropdown menu labeled "Scaling performed by:", select System.
   • Note: Avoid "Application," as that is the default behavior causing the cutoff.
6. Save and Test: Click OK on the DPI window, then Apply and OK on the Properties window. Relaunch Office Manager.

The "Why" (Root Cause)

Dentrix is built on legacy framework architecture that utilizes "absolute positioning" for its UI elements. This means the code says, "Draw the OK button exactly 600 pixels from the top of the window."

On older 4:3 aspect ratio monitors, this worked fine. However, modern workstations often ship with 1440p or 4K monitors set to 125% or 150% Windows Scaling. When Dentrix (the Application) tries to scale itself, it calculates the window border correctly but fails to scale the internal coordinate system for the buttons. The result is a window that thinks it is 800 pixels tall, but the buttons are drawn at a coordinate that is now "off-screen" relative to the scaled window frame. By switching the scaling to System, Windows ignores the application's internal coordinate math and simply stretches the entire rendered bitmap of the window to fit the screen properly.

Under the Hood (Technical Deep Dive)

When you check that override box, you are modifying the AppCompatFlags in the Windows Registry. Specifically, Windows looks at: HKCU\Software\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers

Windows adds a string value for the Dentrix executable path with the data ~ HIGHDPIAWARE. This flag tells the Application Compatibility Toolkit to intercept the GetDeviceCaps and GetSystemMetrics API calls that Dentrix makes. Instead of letting Dentrix see the "true" pixel density of the monitor (which it doesn't know how to handle), Windows lies to the application, telling it it's running on a standard 96 DPI display. Windows then intercepts the output buffer and scales the graphics up itself.

If you see the "System (Enhanced)" option, use it for newer Dentrix versions. "System" mode simply stretches the pixels, which can lead to "fuzzy" text. System (Enhanced) uses a newer GDI-based scaling method that re-renders text and vector elements after the scaling is applied, keeping the UI sharp while ensuring the buttons stay within the visible bounds of the window.

RMM & Automation Tips

Don't wait for the office manager to complain about every single workstation. You can push this fix via a registry import through your RMM.

• Bulk Deployment: Create a .reg file or a PowerShell script that targets the AppCompatFlags for common Dentrix executables like Comm.exe, CustApp.exe, and DENTRIX.EXE.
• PowerShell One-Liner: New-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers" -Name "C:\Program Files (x86)\Dentrix\CustApp.exe" -Value "~ DPIUNAWARE" -PropertyType String -Force
• Note: Use DPIUNAWARE to force the System scaling behavior via the registry.

Troubleshooting & Edge Cases

• Edge Case 1: Non-Standard Scaling: If the user has set a custom scaling percentage (e.g., 117%), Dentrix will almost always break. Ensure the client stays on standard increments: 100, 125, or 150.
• Edge Case 2: Remote Desktop (RDP): If the user is accessing Dentrix via RDP, the scaling is often inherited from the local machine. You may need to apply the DPI override on the local PC’s RDP client shortcut rather than the server-side executable.
• The "Blind" Workaround: If you are in a rush and can't reboot or change settings: You can usually hit Tab repeatedly until the focus moves to the "invisible" OK button, then hit Enter. It's a "blind" fix, but it'll get that report printed in a pinch!

More Dentrix Questions? Check for Answers right here!