How to Fix SearchUI.exe Suspended on Windows 10

SearchUI.exe suspended is often caused by your third-party antivirus software which usually interferes with your background processes. Search User Interface or SearchUI is a component of Microsoft’s search assistant called Cortana. If your searchUI.exe process is suspended, this means you won’t be able to use Cortana. Some people like to make use of Microsoft’s search assistant by giving it commands through their microphones. Though, some certain things or apps will stop you from utilizing it.

This doesn’t pop up as an error dialog notifying you that the searchUI.exe file has been suspended but rather it can be found when you open your Task Manager and go through the processes listed there. This issue is not critical and can be solved via some easy and potent solutions. However, before we get into that, let’s have a look at the causes.

SearchUI Suspended Windows 10

What causes SearchUI.exe suspended on Windows 10?

Well, the suspension of searchui.exe can be caused by numerous factor such as –

  • Third-party antivirus. If you are using a third-party antivirus, you are most likely to see the file suspended because your antivirus is trying to stop it.
  • Outdated windows. If you haven’t updated your Windows for quite some time, then this could potentially be the factor of the file being suspended. The UI is not perfect and it needs constant updating.
  • Corrupt package folder. Occasionally, the reason the file is being suspended is a corrupt Cortana package folder which means you’ll have to delete it.

Before proceeding with the solutions, restart your system. Also, run the SFC command and then the DISM command.

Now, it is time to get into the solutions:

Solution 1: Update Windows to the Latest Build

As we mentioned earlier, an outdated Windows could be the cause of this. The User Interface has not been perfected yet and it requires constant updates from its manufacturer which it’ll only get if you update your Windows. Therefore, starting with the easy task, try updating your Windows if you haven’t. To check for updates, do the following:

  1. Press Winkey + I to open Settings.
  2. Click on ‘Update and Security’.
  3. Hit ‘Check for updates’.
    Check for Windows Update

If it prompts you with an update, do update your system.

Solution 2: Fixing Cortana’s Package Folder

A corrupt package folder might be stopping the file from running. In such a case, you’ll have to delete the folder in Safe Boot. Once you’ve booted up your system, do the following:

  1. Press Winkey + X and select ‘Command prompt (Admin)’ or ‘Windows Powershell (Admin)’.
  2. Once that loads up, enter the following command (replace {USERNAME} with your system’s username).
    1. Reset Cortana’s Package Folder through PowerShell
    RD /S /Q “C:\Users\{USERNAME}\AppData\Local\Packages\Microsoft.Windows.Cortana_cw5n1h2txyewy\RoamingState”
  3. Now, open up Windows Powershell (Admin) if you used the command prompt to enter the above-mentioned command.
  4. Once Windows Powershell loads up, enter the following command:
Get-AppXPackage -AllUsers |Where-Object {$_.InstallLocation -like “*SystemApps*”} | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register “$($_.InstallLocation)\AppXManifest.xml”}
Paste the command to get the package folder

Solution 3: Disable the Antivirus

Some users have reported that their third-party antivirus was interfering with the process due to which it was listed as suspended. This was mostly caused by Avast antivirus — so if you are using an Avast antivirus or any other, please turn off your antivirus and then reboot your system to see if the file is still listed as suspended or not.

Solution 4: Delete Roaming User Profile

If you are using a Roaming User profile on your system then the problem might be occurring because of your user profile as it can generate certain issues with SearchUI.exe file. If this is the case for you, you’ll just have to delete the Roaming User Profile. Here’s how to do it:

  1. Go to your Desktop, right-click ‘This PC’ and select ‘Properties’.
    Open PC Properties
  2. On the left-hand side, click ‘Advanced system settings’.
    Open Advanced System Settings
  3. A window will pop up, there click ‘Settings’ under User Profiles.
    Click Settings and delete roaming profile
  4. Locate your Roaming profile and delete it.

Solution 5: Reinstall iCloud

Lastly, another reason can be your iCloud installation. Your iCloud process might be interfering with the SearchUI.exe process in which case you’ll have to uninstall and then reinstall iCloud.

Solution 6: Use Cortana Troubleshooter

Microsoft has included many troubleshooters to help users in troubleshooting common Windows issues. There is also a troubleshooter for Search and Indexing. This troubleshooter first checks for issues Cortana configurations and if it sees any discrepancies, it automatically tries to reinitialize that specific module. Running the search and indexing troubleshooter may solve the problem.

  1. Press Windows key and type “Troubleshoot“. Now in the resulting list, click on “Troubleshoot Settings“.
    Open Troubleshoot Settings
  2. Now in the right pane of the window, find Search and Indexing and click on it. Then click on “Run the Troubleshooter“.
    Run the Search and Indexing Troubleshooter
  3. Now follow the instructions displayed on the screen to complete the troubleshooting process.

Solution 7: Create Another User Account And Rename UsrClass.dat File of the Effected Account

If nothing has helped you so far, then creating a new local administrator account and using it to rename Cortana files/folders of the affected account may solve the problem. We can also rename the files directly when logged in the affected account but this will not completely reintialize the file because a part of it is already in a running state. When we use another account, we can completely change it because it will not be loaded onto the system.

  1. Create a new local user administrator account.
  2. Log-in to that newly created account.
  3. Now navigate to
    C:Users/(the effected account )/AppData/Local/Microsoft/Windows

    where C is your system drive.

  4. Now find UsrClass.dat and rename it to UsrClass.dat.old.
    Rename UsrClass.dat
  5. Now log-out of the new account and log back into the affected account.
ABOUT THE AUTHOR

Kevin Arrows


Kevin Arrows is a highly experienced and knowledgeable technology specialist with over a decade of industry experience. He holds a Microsoft Certified Technology Specialist (MCTS) certification and has a deep passion for staying up-to-date on the latest tech developments. Kevin has written extensively on a wide range of tech-related topics, showcasing his expertise and knowledge in areas such as software development, cybersecurity, and cloud computing. His contributions to the tech field have been widely recognized and respected by his peers, and he is highly regarded for his ability to explain complex technical concepts in a clear and concise manner.

Comments

14
    JO
    Jon Jun 13, 2019

    Thank you SO MUCH!!! FINALLY I SOLVED THIS NOW AFTER MONTHS AND MONTHS OF DEALING WITH UI HANGS!!! You deserve an award!!!

    MA
    MainGoldDragon Aug 4, 2019

    I can’t actually fucking believe I fixed this. Had this problem for quite a while but I didn’t notice/care too much about it until I finally decided to sit down and fix it. I tried A Lot of things to fix this, but it wasn’t until Solution 2 that fixed it. Don’t know if it was a combination of other solutions, but it got fixed when I followed Solution 2.

    WR
    William Bonomo Rosa Feb 5, 2020

    PS C:Windowssystem32> RD /S /Q “C:UsersnhallAppDataLocalPackagesMicrosoft.Windows.Cortana_cw5n1h2txyewyRoamingState”
    Remove-Item : A positional parameter cannot be found that accepts argument ‘/Q’.
    At line:1 char:1
    + RD /S /Q “C:UsersnhallAppDataLocalPackagesMicrosoft.Windows.Cor …
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo : InvalidArgument: (:) [Remove-Item], ParameterBindingException
    + FullyQualifiedErrorId : PositionalParameterNotFound,Microsoft.PowerShell.Commands.RemoveItemCommand

      SW
      Shane Warren Author Feb 8, 2020

      Try to type in the command and check if that works

      OS
      OssianGrr Feb 9, 2020

      I know this one: The “RD” command needs to come from a regular CMD prompt, not PowerShell.

      Reply
    OS
    OssianGrr Feb 5, 2020

    Hi, I have this problem.
    I don’t have any antivirus installed; this is a relatively new Windows 10 PC and this problem just showed up.
    Trying Solution 2, but I’m stuck. The “RD” command worked, but the “Get-AppXPackage” step says it can’t run in Safe Mode. Any suggestions?

      SW
      Shane Warren Author Feb 8, 2020

      Get out of the safe mode and run the command over there.

        OS
        OssianGrr Feb 9, 2020

        Well, a couple of things:
        1) In “regular mode”, it said something to the effect of “Can’t replace packages. Try running this in Safe Mode”, while in Safe Mode it said “Can’t run this in Safe Mode”. So, round and round it went.

        2) The problem actually went away on its own, and then I read online that it was a “known” Microsoft problem for all users on that specific day, so I stopped pursuing it.

        In the future I might want to figure it out, but I’m all set now.
        Thanks for your reply.

    TA
    Tarun Feb 9, 2020

    It actually worked, damn bro, I never thought it would be successful, thank you so much bro!

    RM
    Rmichael Feb 29, 2020

    Cmd Prompt as Administrator gives the following message “The system can not find the path specified” to the following command” C:WindowsSystem32> RD /S /Q “C:UsersMikeAppDataLocalPackagesMicrosoft.Windows.Cortana_cw5n1h2txyewyRoamingState” OS Win 10, Widows Defender, Malwarebytes 4.0.4.049

      SW
      Shane Warren Author Feb 29, 2020

      Maybe u aren’t entering your username correctly? are u sure that you have entered the correct username?

        RM
        Rmichael Mar 1, 2020

        I did, 3 times.

          SW
          Shane Warren Author Mar 4, 2020

          Ok do the same in safe mode and check if it works.

          RM
          Rmichael Mar 5, 2020

          I didn’t have to… I wish I could remember where I found this info but there was a registry key with a setting that was wrong. It was set for 1. The info said to change the value to 0. I did, restarted my laptop and that was the fix. If I can remember or rediscover the source I will post it back here. I spent four and a half hours checking Google results after getting to here (which was a two or three hour research effort) and reading all the fine print before I ran across this post. It listed five or six items to check and do and the registry fix was about number four. Thank you for your time, help and support. I appreciate it.