Profile Editor navigation icons render as square/missing glyphs on Windows 11 25H2

[Pav-Osmolski]

Description

Several icons in the Profile Editor navigation sidebar are rendered as square/missing-glyph boxes instead of the intended symbols.

The affected icons include entries such as:

• Back to Profiles
• Button Mapping
• Special Actions
• Controller Readings
• Axis Config
• Lightbar
• Touchpad
• Gyro

The text itself renders correctly.

Environment

• Windows 11 25H2
• Fully updated
• Segoe Fluent Icons Regular is installed and visible in the Windows Fonts control panel
• DS4Windows version/build: RC 4.6.2

Steps to reproduce

1. Launch DS4Windows.
2. Open Profiles.
3. Edit an existing profile.
4. Look at the navigation icons on the left side of the Profile Editor.

Actual behaviour

Several navigation icons are displayed as square/missing-character glyphs.

Screenshot

Expected behaviour

All Profile Editor navigation entries should display their intended icons correctly on a standard fully updated Windows 11 installation.

Suspected cause

The navigation template uses:

FontFamily="Segoe Fluent Icons"

However, several of the navigation entries currently use ordinary Unicode characters as their Tag value, for example:

<ListBoxItem Content="Back to Profiles" Tag="&#x2190;" />
<ListBoxItem Content="Button Mapping" Tag="&#x25A3;" />
<ListBoxItem Content="Special Actions" Tag="&#x2726;" />
<ListBoxItem Content="Controller Readings" Tag="&#x223F;" />
<ListBoxItem Content="Axis Config" Tag="&#x2194;" />
<ListBoxItem Content="Lightbar" Tag="&#x25C9;" />
<ListBoxItem Content="Touchpad" Tag="&#x25A1;" />
<ListBoxItem Content="Gyro" Tag="&#x25CE;" />
<ListBoxItem Content="Advanced" Tag="&#x2699;" />
<ListBoxItem Content="Log" Tag="&#x2261;" />

Because these are being rendered specifically with Segoe Fluent Icons, some of those Unicode code points do not appear to have corresponding glyphs in the current Windows 11 version of that font, resulting in the missing-glyph squares.

Interestingly, some entries already use Segoe Fluent Icons private-use glyphs, for example:

<ListBoxItem Content="Audio Haptics" Tag="&#xE767;" />
<ListBoxItem Content="Nintendo Options" Tag="&#xE7FC;" />

Those appear to follow the intended Segoe Fluent Icons usage.

Possible fix

It may be better to use actual Segoe Fluent Icons glyph code points consistently for the Profile Editor navigation entries rather than ordinary Unicode symbols.

Alternatively, the UI could:

• use Segoe UI for entries that deliberately use standard Unicode symbols
• provide a font fallback
• use vector/path icons instead of font glyphs

Using actual Fluent icon glyphs throughout would probably be the most consistent solution with the existing UI design.

Additional notes

I initially suspected a missing font, but Segoe Fluent Icons Regular is definitely installed on the affected Windows 11 25H2 system.

The issue therefore appears to be related to the glyph/code-point selection rather than the font itself.