For Always On VPN administrators using the Routing and Remote Access Service (RRAS) on Windows Server 2025, you’ve likely encountered issues with service restarts and system reboots since migrating to the latest release of the Windows server operating system. I’ve experienced this myself, and many of my customers and Discord users have raised the same complaints.
Important Note! The fix for this issue is included in the April 2026 security updates. See below for more details.
Service Hang
Attempting to restart the RemoteAccess service after the server has accepted at least one VPN connection causes the service to hang. In addition, many have reported that the server hangs and eventually blue-screens during a shutdown or restart.
Resolution
Microsoft included a fix for this issue in the April 2026 security updates. However, the fix is not enabled by default. After applying the April 2026 updates, administrators must activate the fix by setting the following registry key.
Key: HKLM\SYSTEM\CurrentControlSet\Policies\Microsoft\FeatureManagement\Overrides\
Name: 3247592078
Type: DWORD
Value: 1
You can enable this setting by opening an elevated PowerShell command window and running the folowing commands.
$RegPath = 'HKLM:\SYSTEM\CurrentControlSet\Policies\Microsoft\FeatureManagement\Overrides'If (-not (Test-Path $RegPath)) { New-Item -Path $RegPath -Force | Out-Null}Set-ItemProperty -Path $RegPath -Name '3247592078' -Value 1 -Type DWORD -ForceOnce the registry has been updated, reboot the server for the change to take effect.
Edward
/ April 17, 2026May I ask when you first became aware of the RRAS issues with Server 2025? Also would really be appreciated if you could post a follow-up when the updates are relesed (I don’t believe they got included in the April 2026 update).
We’ve had a case (non-premier, regular Microsoft support) open since July 2025 and are yet to receive any response at all, let alone any info about when an update may possibly be available.
Richard M. Hicks
/ April 17, 2026I first became aware of this issue after upgrading my lab to Windows Server 2025 earlier this year. The information I had from Microsoft indicated a fix was due to be released with the April security updates. I’ve updated my machines and still have this problem. I’m chasing it down with Microsoft now to find out what happened. I’ll update you when I have more information. Thanks!
Richard M. Hicks
/ April 17, 2026Mystery solved. The fix is in the April 2026 but not enabled by default. It must be activated by registry key. I’ve updated the post to include this new information. I’ve tested and it works great. Let me know how it goes for you. 🙂