Summary
This article explains why, when you use a Windows Server 2025 Remote Desktop Session Host (RDSH) server, remote desktop users might experience a lag in the performance of the Start menu. This lag occurs only the first time that a user opens the Start menu during a remote desktop session. This article also explains how to configure the RDSH server to prelaunch Start menu processes if the delay is noticeable for users.
Symptoms
You have a Remote Desktop Service deployment that uses Windows Server 2025-based computers as Remote Desktop Session Host (RDSH) servers. Users report that the first time that they open the Start menu after they sign in to a remote desktop session, the menu doesn't appear immediately. Instead, the menu might take several seconds to open. After the initial attempt, the Start menu appears quickly, as expected.
Cause
This behavior is expected. Windows Server 2025 and later versions don't prelaunch the processes that facilitate the Start menu experience. These processes include the following examples:
- SearchHost.exe
- StartMenuExperienceHost.exe
- Other infrastructure processes, such as RuntimeBroker, and other per-user services
Resolution
You can configure Windows Server to use the previous behavior by changing the PrelaunchOverride registry entry.
Caution:
Use the default setting unless users experience a noticeable delay when they first open the Start menu. The purpose of the default setting is to prevent heavy CPU load during "start of the workday" scenarios. In such scenarios, multiple users are likely to sign in to sessions on the same RDSH server at the same time. WhenPrelaunchOverrideis set to1, these processes start for all these users at the same time, causing longer sign-in times and reduced responsiveness for signed-in users.
Important: This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For protection, back up the registry before you modify it so that you can restore it if a problem occurs. For more information about how to back up and restore the registry, see How to back up and restore the registry in Windows.
To change the setting, follow these steps:
-
On the RDSH server, open Registry Editor, and locate the
HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\StartMenusubkey. -
Under this subkey, modify the following entry (if it doesn't exist, create it):
-
Name:
PrelaunchOverride -
Type: REG_DWORD
-
Value data:
1[!NOTE]
PrelaunchOverridehas the following possible values:0: Use the new default behavior. Don't start StartMenuExperienceHost.exe, SearchHost.exe, or similar processes until the user selects Start.1: Use the previous behavior. StartMenuExperienceHost.exe SearchHost.exe, and similar processes start as soon as a user signs in.
-
Source: Microsoft Learn / IT Pro troubleshooting by Microsoft and contributors. Documentation licensed CC BY 4.0. Code samples are covered by the MIT License. Converted from Markdown, with links normalized and embedded media omitted.
