Windows 10 Start Menu and searchbar not working along side settings application

1. Check whether the Start menu package is still registered for the affected user. In a non-elevated Windows PowerShell window, run:

      Get-AppxPackage -Name Microsoft.Windows.StartMenuExperienceHost
   

   • If the package is returned, Start is installed for that user.
   • If nothing is returned, check whether the package still exists on the PC.
2. If nothing is returned, open an elevated PowerShell window and run:

      Get-AppxPackage *StartMenu* -AllUsers
   

   • If app details are returned, the package exists on the machine and can be registered again for the user.
3. Re-register the Start menu package for the user. Important: run this from a non-elevated PowerShell window. If run elevated, the package is registered to the administrator instead of the user.

      Add-AppxPackage -Path "C:\Windows\SystemApps\Microsoft.Windows.StartMenuExperienceHost_cw5n1h2txyewy\AppxManifest.xml" -Register -DisableDevelopmentMode
   

4. Check whether the Start menu process is running. From an elevated PowerShell window, run:

      get-Process StartMenuExperienceHost -IncludeUserName
   

   • If multiple users are signed in, each user should have a StartMenuExperienceHost process in that session.
   • On Windows 10 version 1809 and earlier, check whether ShellExperienceHost.exe is running instead.
5. Check whether the Start menu is crashing. Review:
   • Application event log
   • Microsoft-Windows-TWinUI/Operational event log
   For crash symptoms, look for Event IDs 1000 and 1001 for StartMenuExperienceHost.exe.
6. Verify the service dependency required for a stable Start menu. Open Services and confirm Background Tasks Infrastructure Service (BrokerInfrastructure) is set to Automatic. Then verify the Power Dependency Coordinator driver from Command Prompt:

      sc query pdc
   

   Expected result includes STATE : 4 RUNNING. If BrokerInfrastructure does not start, or pdc is missing, disabled, or deleted, Start can stop responding.
7. If the issue looks like Start tile corruption, run the recovery command from Command Prompt:

      C:\Windows\System32\tdlrecover.exe -reregister -resetlayout -resetcache
   

   A restart is not required, but it can help clear residual issues afterward.
8. Since Settings also does not open and SFC, DISM, and PowerShell attempts already did not help, check whether the problem started after a recent update. Use:
   • PowerShell: [System.Environment]::OSVersion.Version
   • Command Prompt: winver
   Also check whether there were recent changes to:
   • registry keys or folders
   • GPO or MDM policies
   • Start menu customization settings
9. If the system was upgraded rather than clean-installed, confirm that with PowerShell:

      test-path "$env:windir\panther\miglog.xml"
   

   • If the file exists, the system is an upgrade.
   • If it does not exist, the system is a clean install.
10. If Start still fails after the checks above, use diagnostic tools and logs to narrow the cause:

• System event log
• Application event log
• Microsoft/Windows/Shell-Core*
• Microsoft-Windows-TWinUI*
• Microsoft/Windows/AppReadiness*
• Microsoft/Windows/AppXDeployment*
• Microsoft-Windows-PushNotification-Platform/Operational
• Microsoft-Windows-ShellCommon-StartLayoutPopulation*
• Microsoft-Windows-CloudStore*
• WER folders:
  • C:\ProgramData\Microsoft\Windows\WER\ReportArchive\
  • C:\ProgramData\Microsoft\Windows\WER\ReportQueue\

If the failure is consistent, ProcDump can be used to capture crash dumps and Procmon can be used to investigate permission-related startup failures.

References:

• Start menu troubleshooting guidance