Share via

WINDOWS 11 24H2 LTSC MARCH UPDATE 2026 BUG serach for users does not administrator rights

Cedric EYRAUD 0 Reputation points
2026-03-26T10:24:57.04+00:00

Hello,

With the march update normal users (without administrator right) taskbar search and menu search not work.

if i put the users in the local administrators group taskbar and menu search works

There is a right file problem on delete files when register MicrosoftWindows.Client.CBS_cw5n1h2txyewy with an account who dont have administrator right.

My users have roaming profile and delete roaming cache at sign out

Windows for business | Windows Client for IT Pros | User experience | Other
0 comments No comments

2 answers

Sort by: Most helpful
  1. VPHAN 28,740 Reputation points Independent Advisor
    2026-03-28T08:48:48.5233333+00:00

    Hi Cedric EYRAUD,

    How is your issue going? Has it been resolved yet? If it has, please consider accepting the answer as it helps others sharing the same problem benefit too. Thank you :)

    VP

    0 comments No comments

  2. VPHAN 28,740 Reputation points Independent Advisor
    2026-03-26T10:57:57.71+00:00

    Hi Cedric EYRAUD,

    The issue you are experiencing with the Taskbar and Start Menu search stems from how standard user profiles interact with Windows Appx package registration during the login process. Specifically, the search interface relies heavily on the MicrosoftWindows.Client.CBS_cw5n1h2txyewy package, which acts as the core framework for the Windows Experience Host. Because your corporate environment uses roaming profiles configured to delete the local profile cache at sign-out, the operating system is forced to unpack and re-register this specific package from scratch every time you log back in.

    The recent March update introduced underlying modifications to the file and registry permissions required for this specific package deployment. When your standard user account attempts to write the necessary files to the C:\Users[Username]\AppData\Local\Packages directory and populate the required registry keys under HKEY_CURRENT_USER\Software\Classes, the system halts the operation due to insufficient privileges. This leaves the search components unregistered and completely unresponsive. When an administrator logs in, their elevated security token allows the package deployment to complete successfully, which is exactly why the search functions perfectly for those specific accounts.

    Attempting to force a bypass of these local administrator requirements is not possible without violating your network's security protocols. This issue requires intervention from your IT department to resolve centrally. Your administrators will need to either temporarily adjust the Group Policy that clears the roaming profile cache to bypass the daily re-registration requirement, or deploy a subsequent Microsoft cumulative update that officially corrects these Appx deployment permission structures for standard user contexts.

    Hope this answer brought you some useful information. If it did, please hit “accept answer”. Should you have any questions, feel free to leave a comment.

    VP

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.