Is there an existing issue for this?

• I have searched the existing issues

Description of the Issue

Font Ligature support is functioning on my Server 2025 install in other applications such as Windows Terminal, but in Notepad++ the DirectWrite option gets unchecked at startup, which I believe is causing font ligature support to be disabled.

I have ensured that the DirectX runtimes are installed and available, and have rebooted the machine.

I have tried running as both Administrator and standard user.

Steps To Reproduce

1. Use a font that supports ligatures (Cascadia Code or FiraCode)
2. Enabled DirectWrite support from the Settings menu
3. Restart Notepad++ to find the option toggled off

Current Behavior

DirectWrite option gets unchecked at application startup, which I believe is causing font ligature support to be disabled.

Expected Behavior

DirectWrite is supported on this OS and has all dependencies available for use

Debug Information

Notepad++ v8.7.4   (64-bit)
Build time : Dec  4 2024 - 23:50:05
Path : C:\Program Files\Notepad++\notepad++.exe
Command Line : "C:\Users\Administrator\AppData\Roaming\Notepad++\config.xml" 
Admin mode : ON
Local Conf mode : OFF
Cloud Config : OFF
Periodic Backup : ON
Placeholders : OFF
DirectWrite : OFF
Multi-instance Mode : monoInst
File Status Auto-Detection : cdEnabledNew (for current file/tab only)
Dark Mode : ON
OS Name : Windows Server 2025 Standard (64-bit)
OS Version : 24H2
OS Build : 26100.2314
Current ANSI codepage : 1252
Plugins : 
    mimeTools (3.1)
    NppConverter (4.6)
    NppExport (0.4)

Anything else?

Attached debug information is from a fresh startup, when the DirectWrite option was forced off.