locked
Windows Menu Search doesn't work on Windows Server 2019 RDS RRS feed

  • Question

  • Hi

    Since some days "Windows Menu Search" doesn't work on one of our Server 2019 RDS. If want to use it ans starty typing, nothing happens. Menu Search on the other Server works fine. The Servers have same settings and updates.

    Anyone an idea or had this problem too?

    greetings

    Thursday, July 9, 2020 8:21 AM

All replies

  • Hi,

    Sounds like an intermittent issue if it works some days?  I take it works fine all the time on your other RDS servers?

    Is the Windows Service enabled and running?  https://support.microsoft.com/en-ca/help/3204979/windows-search-is-disabled-by-default-in-windows-server-2016.  Whilst this re: 2016, it appears its the same for 2019.

    Thursday, July 9, 2020 9:42 AM
  • Hello,

    Try Search and Indexing troubleshooter, see if it helps you.

    Regards.


    Microsoft MVP (Windows and Devices for IT)

    Windows Insider MVP

    Windows Help & Support [www.kapilarya.com]

    Thursday, July 9, 2020 12:42 PM
  • Hi Stu

    Thank you for your answer. We have 6 RDS Server. 5 Server do work without problems. Only on 1 we have that issue. I can enable the search filed on taskbar, but can't click inside.

    On ALL RDS Server, Windows Search is DISABLED. Set the Service to AUTOMATIC on the Server that has the issue, doesn't help.

    greetings


    • Edited by ict_maen Thursday, July 9, 2020 1:56 PM
    Thursday, July 9, 2020 12:43 PM
  • Hello,

    Try Search and Indexing troubleshooter, see if it helps you.

    Regards.


    Microsoft MVP (Windows and Devices for IT)

    Windows Insider MVP

    Windows Help & Support [www.kapilarya.com]

    Hi Kapil

    I can't choose anything that describe my problem. Search doesn't work at all.


    • Edited by ict_maen Friday, July 10, 2020 6:04 AM
    Friday, July 10, 2020 5:52 AM
  • hi ,

    Just install the 'Windows Search Service' feature worked for me, with workaround of:
    1.Open elevated CMD, run “Dcomcnfg.exe” and press enter to open Component Service.
    2.Click Component Services – Computers – right click My Computer and click Properties.
    3.Choose the Default Properties tab.
    4.Select Connect in the Default Authentication Level drop down list if it is set to None. Choose OK, confirm selection in popup and close dcomcnfg.exe.

    Regards,

    Yvonne


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Friday, July 10, 2020 7:55 AM
  • Hi Yvonne

    To install Windows Search Service I have to do this workaround? Windows Search is not installed on any RDS Server.

    Monday, July 13, 2020 5:55 AM
  • hi,

     let's open Task manager to confirm whether the below files are in Details.
       a)SearchUI.exe      
       b)ShellExperienceHost.exe
       c)sihost.exe

     you can review event logs for addressing the problem:

    Open your Event Viewer and do the action below:
       a)Click Windows Logs\Application.
       b)Click Filter Current Log in  right of your screen
       c)Check in the box Critical and Error, then you will see all the error.
       d)Find the error with event ID:1000,just like the picture below(We only need to find 3 .exe files above in the step3.)

    This "Remote Desktop Services (Terminal Services)" Forum will be migrating to a new home on Microsoft Q&A, please refer to this sticky post for more details. 

    Best Regards,

    Yvonne


    "Remote Desktop Services (Terminal Services)" forum will be migrating to a new home on Microsoft Q&A!

    We invite you to post new questions in the "Remote Desktop Services (Terminal Services)"  forum's new home on Microsoft Q&A!

    For more information, please refer to the sticky post.
    Tuesday, July 14, 2020 9:49 AM
  • hi Yvonne

    Sorry for the late answer. I checked "TaskManager" and "Eventviewer"

    "SearchUI.exe" is not running.

    There is no error 1000 with one of the exes above.

    greetings 

    Wednesday, July 15, 2020 2:21 PM
  •    

    l Below is the System file checker and System image repair commands, so it fixes if there is any system health issue from the OS level.

    Please perform the below recommendation and try to take RDP and let us know the status.

    -Open the elevated command prompt and perform the “SFC /scannow”
    -Dism /Online /Cleanup-Image /CheckHealth
    -Dism /Online /Cleanup-Image /ScanHealth
    -Dism /Online /Cleanup-Image /RestoreHealth

    This "Remote Desktop Services (Terminal Services)" Forum will be migrating to a new home on Microsoft Q&A, please refer to this sticky post for more details. 


    "Remote Desktop Services (Terminal Services)" forum will be migrating to a new home on Microsoft Q&A!

    We invite you to post new questions in the "Remote Desktop Services (Terminal Services)"  forum's new home on Microsoft Q&A!

    For more information, please refer to the sticky post.


    Thursday, July 16, 2020 10:02 AM
  • Hi Yvonne

    I will do this now on weekend. Will let you know on Monday.

    greetings

    Friday, July 17, 2020 9:48 AM
  • Hi Yvonne

    I did the commands.

    Dism /Online /Cleanup-Image /CheckHealth
    - Task finished successful.

    Dism /Online /Cleanup-Image /ScanHealth
    Task finished successful.

    Dism /Online /Cleanup-Image /RestoreHealth
    - Stuck at 100%

    SFC /scannow- Here it founds lots of duplicated ownerships and comitted to repair
    - had some corrupted files too that couldn't be repaired (last part of the logs):

    2020-07-19 06:35:52, Info                  CSI    0000571b [SR] Verify complete
    2020-07-19 06:35:52, Info                  CSI    0000571c [SR] Repairing 8 components
    2020-07-19 06:35:52, Info                  CSI    0000571d [SR] Beginning Verify and Repair transaction
    2020-07-19 06:35:52, Info                  CSI    0000571e Hashes for file member [l:18]'Server Manager.lnk' do not match.
     Expected: {l:32 ml:4096 b:04be7e3045885bf08fc62466ff66b93bd801e1dcb0ca48b66ddff9b9f47bc020}.
     Actual: {l:32 b:f4184a4a70479c2d0cd15266a423692e828d8ebc2018187f108ba6cae50e2af8}.
    2020-07-19 06:35:52, Info                  CSI    0000571f [SR] Cannot repair member file [l:18]'Server Manager.lnk' of Microsoft-Windows-ServerManager-ProgramsMenuShortcut, version 10.0.17763.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
    2020-07-19 06:35:52, Info                  CSI    00005720 Hashes for file member [l:23]'tls_branding_config.xml' do not match.
     Expected: {l:32 ml:4096 b:c3b2a8c679b89829b173cd05bdfa46acb1b28a6d4da26fcf0295387a385a9262}.
     Actual: {l:32 b:5da8432457ba3f3867ea2e0f7cbea806011571e47f4b69ab613f16b2b5978c99}.
    2020-07-19 06:35:52, Info                  CSI    00005721 [SR] Cannot repair member file [l:23]'tls_branding_config.xml' of Microsoft-Windows-TerminalServices-LicenseServer-TlsBrand, version 10.0.17763.1075, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
    2020-07-19 06:35:52, Info                  CSI    00005722@2020/7/19:04:35:52.674 Primitive installers committed for repair
    2020-07-19 06:35:52, Info                  CSI    00005723 Hashes for file member [l:18]'Server Manager.lnk' do not match.
     Expected: {l:32 ml:4096 b:04be7e3045885bf08fc62466ff66b93bd801e1dcb0ca48b66ddff9b9f47bc020}.
     Actual: {l:32 b:f4184a4a70479c2d0cd15266a423692e828d8ebc2018187f108ba6cae50e2af8}.
    2020-07-19 06:35:52, Info                  CSI    00005724 [SR] Cannot repair member file [l:18]'Server Manager.lnk' of Microsoft-Windows-ServerManager-ProgramsMenuShortcut, version 10.0.17763.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
    2020-07-19 06:35:52, Info                  CSI    00005725 [SR] This component was referenced by [l:113]'Microsoft-Windows-ServerManager-UX-Package~31bf3856ad364e35~amd64~~10.0.17763.1.ServerManager-UX-Shell-Deployment'
    2020-07-19 06:35:52, Info                  CSI    00005726 Hashes for file member [l:18]'Server Manager.lnk' do not match.
     Expected: {l:32 ml:4096 b:04be7e3045885bf08fc62466ff66b93bd801e1dcb0ca48b66ddff9b9f47bc020}.
     Actual: {l:32 b:f4184a4a70479c2d0cd15266a423692e828d8ebc2018187f108ba6cae50e2af8}.
    2020-07-19 06:35:52, Info                  CSI    00005727 Hashes for file member [l:18]'Server Manager.lnk' do not match.
     Expected: {l:32 ml:4096 b:04be7e3045885bf08fc62466ff66b93bd801e1dcb0ca48b66ddff9b9f47bc020}.
     Actual: {l:32 b:f4184a4a70479c2d0cd15266a423692e828d8ebc2018187f108ba6cae50e2af8}.
    2020-07-19 06:35:52, Info                  CSI    00005728 [SR] Could not reproject corrupted file \??\C:\ProgramData\Microsoft\Windows\Start Menu\Programs\\Server Manager.lnk; source file in store is also corrupted
    2020-07-19 06:35:52, Info                  CSI    00005729@2020/7/19:04:35:52.690 Primitive installers committed for repair
    2020-07-19 06:35:52, Info                  CSI    0000572a@2020/7/19:04:35:52.690 Primitive installers committed for repair
    2020-07-19 06:35:52, Info                  CSI    0000572b Hashes for file member [l:23]'tls_branding_config.xml' do not match.
     Expected: {l:32 ml:4096 b:c3b2a8c679b89829b173cd05bdfa46acb1b28a6d4da26fcf0295387a385a9262}.
     Actual: {l:32 b:5da8432457ba3f3867ea2e0f7cbea806011571e47f4b69ab613f16b2b5978c99}.
    2020-07-19 06:35:52, Info                  CSI    0000572c [SR] Cannot repair member file [l:23]'tls_branding_config.xml' of Microsoft-Windows-TerminalServices-LicenseServer-TlsBrand, version 10.0.17763.1075, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
    2020-07-19 06:35:52, Info                  CSI    0000572d [SR] This component was referenced by [l:80]'Package_3643_for_KB4561608~31bf3856ad364e35~amd64~~10.0.1.9.4561608-6414_neutral'
    2020-07-19 06:35:52, Info                  CSI    0000572e Hashes for file member [l:23]'tls_branding_config.xml' do not match.
     Expected: {l:32 ml:4096 b:c3b2a8c679b89829b173cd05bdfa46acb1b28a6d4da26fcf0295387a385a9262}.
     Actual: {l:32 b:5da8432457ba3f3867ea2e0f7cbea806011571e47f4b69ab613f16b2b5978c99}.
    2020-07-19 06:35:52, Info                  CSI    0000572f Hashes for file member [l:23]'tls_branding_config.xml' do not match.
     Expected: {l:32 ml:4096 b:c3b2a8c679b89829b173cd05bdfa46acb1b28a6d4da26fcf0295387a385a9262}.
     Actual: {l:32 b:5da8432457ba3f3867ea2e0f7cbea806011571e47f4b69ab613f16b2b5978c99}.
    2020-07-19 06:35:52, Info                  CSI    00005730 [SR] Could not reproject corrupted file \??\C:\Windows\System32\\tls_branding_config.xml; source file in store is also corrupted
    2020-07-19 06:35:52, Info                  CSI    00005731@2020/7/19:04:35:52.705 Primitive installers committed for repair
    2020-07-19 06:35:52, Info                  CSI    00005732 [SR] Repairing corrupted file \??\C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Accessories\\Math Input Panel.lnk from store
    2020-07-19 06:35:52, Info                  CSI    00005733@2020/7/19:04:35:52.737 Primitive installers committed for repair
    2020-07-19 06:35:52, Info                  CSI    00005734 [SR] Repairing corrupted file \??\C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Accessories\\XPS Viewer.lnk from store
    2020-07-19 06:35:52, Info                  CSI    00005735@2020/7/19:04:35:52.799 Primitive installers committed for repair
    2020-07-19 06:35:52, Info                  CSI    00005736 [SR] Repairing corrupted file \??\C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Accessories\\Windows Media Player.lnk from store
    2020-07-19 06:35:52, Info                  CSI    00005737@2020/7/19:04:35:52.830 Primitive installers committed for repair
    2020-07-19 06:35:52, Info                  CSI    00005738 [SR] Repairing corrupted file \??\C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Accessories\\Steps Recorder.lnk from store
    2020-07-19 06:35:52, Info                  CSI    00005739@2020/7/19:04:35:52.846 Primitive installers committed for repair
    2020-07-19 06:35:52, Info                  CSI    0000573a [SR] Repairing corrupted file \??\C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Accessories\System Tools\\Windows Server Backup.lnk from store
    2020-07-19 06:35:52, Info                  CSI    0000573b@2020/7/19:04:35:52.862 Primitive installers committed for repair
    2020-07-19 06:35:52, Info                  CSI    0000573c [SR] Repairing corrupted file \??\C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Accessories\System Tools\\Character Map.lnk from store
    2020-07-19 06:35:52, Info                  CSI    0000573d@2020/7/19:04:35:52.893 Primitive installers committed for repair
    2020-07-19 06:35:52, Info                  CSI    0000573e [SR] Repair complete
    2020-07-19 06:35:52, Info                  CSI    0000573f [SR] Committing transaction
    2020-07-19 06:35:52, Info                  CSI    00005740 Creating NT transaction (seq 1)
    2020-07-19 06:35:52, Info                  CSI    00005741 Created NT transaction (seq 1) result 0x00000000, handle @0x1294
    2020-07-19 06:35:53, Info                  CSI    00005742@2020/7/19:04:35:53.02 Beginning NT transaction commit...
    2020-07-19 06:35:53, Info                  CSI    00005743@2020/7/19:04:35:53.018 CSI perf trace:
    CSIPERF:TXCOMMIT;27438
    2020-07-19 06:35:53, Info                  CSI    00005744 [SR] Verify and Repair Transaction completed. All files and registry keys listed in this transaction  have been successfully repaired


    Sunday, July 19, 2020 8:00 AM
  • hi, please kindly let me know after the repair command finished, if the isue persisits or not.

    Best Regards,

    Yvonne

    This "Remote Desktop Services (Terminal Services)" Forum will be migrating to a new home on Microsoft Q&A, please refer to this sticky post for more details. 


    "Remote Desktop Services (Terminal Services)" forum will be migrating to a new home on Microsoft Q&A!

    We invite you to post new questions in the "Remote Desktop Services (Terminal Services)"  forum's new home on Microsoft Q&A!

    For more information, please refer to the sticky post.
    Monday, July 20, 2020 9:58 AM
  • It's still not working. What about the "SearchUI.exe" it's not running.
    Tuesday, July 21, 2020 7:45 AM
  • hi, Start menu can be re-used after removing AppLocker policy since there is some relationship in applocker and start menu.

     

     Here is the Theory on Launch of SEH
    During logon, Explorer.exe invokes the Activation Manager (AAM)  in sihost.exe to active the UWP application Microsoft.Windows.ShellExperienceHost_cw5n1h2txyewy!App 
    Sihost.exe verifies the App package state and send request to RpcSs to active the UWP application. 
    RpcSs checks if the application is activated already, if not, it sends request to DcomLaunch to create the process. 
    DcomLaunch then creates the process ShellExperienceHost.exe.
    So there must be something wrong in step one. 

      

    Let’s run command below in PowerShell as Administrator to re-registry the Shellexperiencehost.exe and Cortana.

    Get-AppXPackage -allusers Microsoft.Windows.ShellExperienceHost  | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register “$($_.InstallLocation)\AppXManifest.xml”}

    Get-AppXPackage -allusers Microsoft.Windows.Cortana  | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register “$($_.InstallLocation)\AppXManifest.xml”}

    Then run cmd below and share the outcome with me:
            get-appxpackage -alluser *shellexperiencehost*

    This "Remote Desktop Services (Terminal Services)" Forum will be migrating to a new home on Microsoft Q&A, please refer to this sticky post for more details. 


    "Remote Desktop Services (Terminal Services)" forum will be migrating to a new home on Microsoft Q&A!

    We invite you to post new questions in the "Remote Desktop Services (Terminal Services)"  forum's new home on Microsoft Q&A!

    For more information, please refer to the sticky post.


    Thursday, July 23, 2020 9:58 AM
  • Hi Yvonne

    I could do both:

    Name                   : Microsoft.Windows.ShellExperienceHost
    Publisher              : CN=Microsoft Windows, O=Microsoft Corporation, L=Redmond, S=Washington, C=US
    Architecture           : Neutral
    ResourceId             : neutral
    Version                : 10.0.17763.1
    PackageFullName        : Microsoft.Windows.ShellExperienceHost_10.0.17763.1_neutral_neutral_cw5n1h2txyewy
    InstallLocation        : C:\Windows\SystemApps\ShellExperienceHost_cw5n1h2txyewy
    IsFramework            : False
    PackageFamilyName      : Microsoft.Windows.ShellExperienceHost_cw5n1h2txyewy
    PublisherId            : cw5n1h2txyewy
    PackageUserInformation : {S- [xxxr]: Installed,
                             S- [xxx]: Installed,
                             S- [xxx]: Installed,
                             S- [xxx]: Installed}
    IsResourcePackage      : False
    IsBundle               : False
    IsDevelopmentMode      : False
    NonRemovable           : True
    IsPartiallyStaged      : False
    SignatureKind          : Syst

    Windows Search is still not working.

    • Edited by ict_maen Monday, July 27, 2020 7:41 PM
    Monday, July 27, 2020 7:41 PM
  • hi, 

     per SearchUI.EXE not working, repairing it with deleting the subfolder under Packages:

    -Delete the directory:  C:\Users\<user>\AppData\Local\Packages\Microsoft.Windows.Cortana_cw5n1h2txyewy [REBOOT]

    -Run the following command from Powershell with Admin privileges:  Add-AppxPackage -Register "C:\Windows\SystemApps\Microsoft.Windows.Cortana_cw5n1h2txyewy\AppxManifest.xml" -DisableDevelopmentMode [REBOOT]

    For Step 1, you'll have to boot to a WinPE drive, or maybe Safe Mode because the directory will be locked.  But, if you do these two steps in this order it may work.

    Yvonne

    This "Remote Desktop Services (Terminal Services)" Forum will be migrating to a new home on Microsoft Q&A, please refer to this sticky post for more details. 


    "Remote Desktop Services (Terminal Services)" forum will be migrating to a new home on Microsoft Q&A!

    We invite you to post new questions in the "Remote Desktop Services (Terminal Services)"  forum's new home on Microsoft Q&A!

    For more information, please refer to the sticky post.
    Wednesday, July 29, 2020 9:43 AM
  • is it work now?

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Friday, July 31, 2020 8:29 AM