Introduction

Windows Server 2025, Microsoft's latest server operating system, has recently encountered critical issues affecting enterprise IT environments. Notably, administrators have reported problems with firewall profile misconfigurations on domain controllers and freezing Remote Desktop Protocol (RDP) sessions following recent updates. Understanding these issues, their implications, and available solutions is essential for maintaining system stability and security.

Firewall Profile Misconfiguration on Domain Controllers

Issue Overview

After restarting Windows Server 2025 domain controllers, the servers may incorrectly apply the standard or public firewall profile instead of the domain firewall profile. This misconfiguration can lead to:

  • Inaccessibility of Domain Controllers: Servers may become unreachable within the domain network.
  • Service Disruptions: Applications and services dependent on these domain controllers may fail or become inaccessible.
  • Security Vulnerabilities: Ports and protocols that should be restricted by the domain firewall profile may remain open, exposing the network to potential threats.

Technical Details

The root cause lies in the domain controllers failing to apply the correct network profile upon reboot. Instead of loading the 'Domain Authenticated' profile, the servers default to the 'Public' or standard firewall profile. This behavior disrupts critical Active Directory functions such as replication, Group Policy application, and user authentication. (learn.microsoft.com)

Workaround and Recommendations

Until a permanent fix is released, administrators can implement the following workaround:

  1. Manually Restart the Network Adapter: After each reboot, execute the following PowerShell command to restart the network adapter:

``INLINECODE0 ``

  1. Automate the Workaround: To reduce manual intervention, create a scheduled task that runs the above command automatically upon system startup.

It's crucial to monitor domain controller connectivity and avoid unnecessary reboots until a permanent solution is provided by Microsoft. (learn.microsoft.com)

Remote Desktop Protocol (RDP) Freezing Post-Update

Issue Overview

Following the installation of the February 2025 security update (KB5051987), Windows Server 2025 users have reported that Remote Desktop sessions freeze shortly after connection. During these freezes, mouse and keyboard inputs become unresponsive, necessitating users to disconnect and reconnect. (bleepingcomputer.com)

Technical Details

The freezing issue appears to be linked to recent security hardening measures affecting the Remote Desktop Protocol stack, potentially interfering with input data processing over RDP sessions. While a similar issue was observed in Windows 11 version 24H2 and addressed with the KB5052093 update, the Windows Server 2025 problem remains unresolved as of now. (bleepingcomputer.com)

Workaround and Recommendations

While awaiting an official fix, administrators can consider the following actions:

  • Monitor for Updates: Regularly check for updates from Microsoft that address this issue.
  • Alternative Remote Management Tools: Utilize other remote management solutions to maintain server administration capabilities.
  • Test Updates in Controlled Environments: Before deploying updates broadly, test them in a controlled setting to assess their impact on RDP functionality.

Staying informed through Microsoft's official channels and community forums is essential for timely updates and shared experiences. (bleepingcomputer.com)

Conclusion

The firewall profile misconfiguration and RDP freezing issues in Windows Server 2025 highlight the complexities of maintaining system stability amid ongoing updates. By implementing the recommended workarounds and closely monitoring official communications, IT administrators can mitigate the impact of these issues and ensure the continued reliability and security of their server environments.