RDP connection fails when Duo is not set to start automatically

[keychain2db]

Currently, Duo must be configured to start automatically at boot in order for Remote Desktop Protocol connections to the host PC to succeed. When Duo is not set to run at system startup, RDP fails to initialize correctly, resulting in an inability to remotely access the machine. However, when Duo is manually started after the system boots, RDP functionality is restored, and remote connections succeed without issue. This behavior is consistent across reboots, pointing to the RDP being dependent on Duo being initialized for proper operation.

System Configuration:

• OS: Windows 11 24H2
• Duo Version: v1.5.3
• Remote access client: Windows Remote Desktop Connection

Steps to Reproduce:

1. Configure the system so that Duo does not start automatically at boot.
2. Reboot the system.
3. Attempt to connect via RDP (black screen)
4. Log in locally or via another method, manually start Duo.
5. Attempt to connect via RDP again (output works)

[Black-Seraph]

This issue is no longer valid / reproducible.