in issue with Windows servver 2022 ,RDP Environmnet User not able to open start windows home button, start button is disable, Windows search disable, taskbaar search is disable for newly created RDP user

Question

in issue with Windows servver 2022 ,RDP Environmnet User not able to open start windows home button, start button is disable, Windows search disable, taskbaar search is disable for newly created RDP user

Hitesh Chawra 0

We have windows server 2022 RDP is setup there,user are able to login and work, starting while createing new user it's work perfectly, but now when i create a new user and when user are login into the server as RDP they are unable to search any think in folder search option , windows home button search option. and toolbar search baar to there is 15 GB space i C drive how to remain active it from new user . there is no issue with old employee profile but its issue with new user profile how to fix it

Start menu search
Taskbar search
Search inside C:\Users
Search inside Documents
Search for notepad
Search for an existing Excel/Word file

0 comments

2 answers

Your answer

Answer 1

For newly created RDP users on Windows Server, check these areas first:

Verify the Windows Search service
- Press Windows + R, type services.msc, and press Enter.
- Open Windows Search.
- Set Startup type to Automatic (Delayed Start).
- Select Apply > Start > OK.
- This is required when Start menu search returns no results or inconsistent results.
Check whether Search is being disabled by policy for new users
- The NoFind policy can remove the Search link from Start and disable some File Explorer search elements.
- If enabled, users can lose Start menu Search, Windows key + F, F3, and Ctrl+F behavior in File Explorer.
- If this affects only newly created users and not older profiles, review the user policy assignment for new accounts.
If the Start menu itself does not respond, verify the required service
- In Services, ensure Background Tasks Infrastructure Service (BrokerInfrastructure) is set to automatic startup.
- If it fails to start, verify the PDC driver exists and is not disabled.
- Run:
```
     sc query pdc
```
- Expected result: the pdc service should be present and running.
If the issue is only with affected new profiles, rebuild the Search app data for one affected user
- Warning: this includes deleting a user package folder and a registry key. Incorrect registry changes can cause further problems.
- Sign in with another account or use Windows Recovery Environment.
- For Windows 11, delete: %USERPROFILE%\AppData\Local\Packages\MicrosoftWindows.Client.CBS\_cw5n1h2txyewy
- Open Registry Editor and go to: HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Search
- Delete the Search key.
- Open elevated PowerShell and run:
```
     Add-AppxPackage -Path "C:\Windows\SystemApps\MicrosoftWindows.Client.CBS_cw5n1h2txyewy\Appxmanifest.xml" -DisableDevelopmentMode -Register
```
- Restart the server or sign back in and test search again.
If Search works for old profiles but not new ones, test with one newly created Windows account
- Confirm whether the problem reproduces on every new account.
- If it does, that points more strongly to a service or user policy issue than to a single corrupted profile.

References:

Answer 2

Hello Hitesh,

The behavior you’re describing is tied to how the Windows Search service and the Start Menu experience are initialized for new user profiles in a Windows Server 2022 RDS environment. Since existing users are unaffected, the issue is not global but specific to profile creation and search index availability.

First, confirm that the Windows Search service is running. Open services.msc and check that “Windows Search” is set to Automatic and is started. If this service is disabled or set to Manual, new profiles won’t initialize search correctly. Restart the service if necessary.

Next, verify that the User Profile Service is not failing during logon. Event Viewer under Applications and Services Logs > Microsoft > Windows > User Profile Service will show if the profile creation is incomplete. A corrupted default profile (C:\Users\Default) can cause Start Menu and search to be broken for new users. Compare the contents of C:\Users\Default with a healthy system, and ensure permissions are intact (Administrators, SYSTEM, and Users should have proper rights).

Also check Group Policy settings. In RDS environments, policies under User Configuration > Administrative Templates > Start Menu and Taskbar can disable search or the Start button. Specifically, confirm that “Do not allow pinning items in Jump Lists” or “Do not allow search” are not enforced. Run gpresult /h report.html inside the affected user session to see if any GPO is blocking search.

If the Start Menu is still disabled, re-register the shell experience for the new user. Log in as the affected user, open PowerShell as Administrator, and run:


Get-AppxPackage -AllUsers | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"}

This forces re-registration of Start Menu and search components. After running, sign out and back in.

Finally, ensure disk space is not the limiting factor. You mentioned 15 GB free on C:, which is sufficient, but confirm indexing is not restricted. Open Control Panel > Indexing Options and check that C:\Users is included. If indexing is disabled, new users won’t be able to search files or applications.

In summary, the most common root causes are: Windows Search service disabled, corrupted default profile, or restrictive GPO. Addressing those should restore Start Menu and search functionality for newly created RDP users.

I hope you've found something useful here. If it helps you get more insight into the issue, it's appreciated to accept the answer. Should you have more questions, feel free to leave a message. Have a nice day!

HP.