How do you disable SearchApp.exe from running so that you can enable SLI in the Nvidia Control Panel?

Anonymous
2020-08-21T21:11:28+00:00

I'm unable to shut down SearchApp.exe in task manager so that I can enable SLI in the Nvidia control panel.  I've performed a clean boot and stopped the Windows Search service. 

However as soon as I end task on  SearchApp.exe, it automatically restarts.  Because of this I'm unable to enable SLI in the Nvidia control panel.

SearchApp.exe is located in C:\Windows\SystemApps\Microsoft.Windows.Search_cw5n1h2txyewy

I'm unable to enable SLI if I boot into safe mode.  I already tried that.

When I had a version of Windows 10 pre version 2004, I had no problems ending task on everything running that prevented SLI from begin enabled.  I did a clean install of Windows 10 last night to fix a problem and now that the problem is fixed, I have a new one.  I really hope I don't have to install an older version of Windows 10 and upgrade to get around this problem.

Windows for home | Windows 10 | Cortana and search

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments
Answer accepted by question author
Anonymous
2020-09-06T13:11:25+00:00

The previous answer is unlikely to work because Cortana keeps searchapp.exe running all the time (causing cpus to get hot).

The following commands worked for me. You have to paste them into in Administrator-level Command Prompt again and again until the timing is right and the "move" works.

cd %windir%\SystemApps

taskkill /f /im SearchApp.exe

move Microsoft.Windows.Search_cw5n1h2txyewy Microsoft.Windows.Search_cw5n1h2txyewy.old

Optional: to remove Cortana completely (in addition to stopping searchapp.exe), run the following command in Administrator-level Powershell:

Get-AppxPackage -allusers Microsoft.549981C3F5F10 | Remove-AppxPackage

David Spector

Springtime Software

Was this answer helpful?

300+ people found this answer helpful.
0 comments No comments

67 additional answers

Sort by: Most helpful
  1. Anonymous
    2021-12-17T06:34:30+00:00

    Wow, you guys are really not understanding basic command prompt syntax and coming up with *complicated* ways of trying to restore the basic search functionality. It's not that complicated...

    All the commands in David_167's post did is:

    1. Switch to the SystemApps directory that sits in your Windows directory [cd %windir%\SystemApps]
    2. Kill the running SearchApp.exe task so that you can move.rename the file and stop it running again [taskkill /f /im SearchApp.exe]

    and...

    1. Rename the folder that has the SearchApp.exe executable in it to append ".old" to its name [move Microsoft.Windows.Search_cw5n1h2txyewy Microsoft.Windows.Search_cw5n1h2txyewy.old]

    So... to reverse it, you just need to switch to the SystemApps folder and rename the previously moved folder to remove the ".old" from it. Basically the same commands, except you don't need the 2nd one as there's no point trying to kill a task that isn't running, and just reverse the last command.

    ================================================================

    cd %windir%\SystemApps

    move Microsoft.Windows.Search_cw5n1h2txyewy.old Microsoft.Windows.Search_cw5n1h2txyewy

    ================================================================

    Of course you need to execute these 2 lines from a command prompt that has admin priveledges.

    After that you need to either restart your computer, or alternatively, simply manually run "SearchApp.exe" from the "C:\Windows\SystemApps\Microsoft.Windows.Search_cw5n1h2txyewy" folder to restart the task and search will be instantly restored.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments
  2. Anonymous
    2021-09-23T19:01:34+00:00

    Hi, so i recently fixed the problem that I was struggling with. When you tried Davids cmd, I did that too. It disabled my search.

    Solution: 1

    press Win+R

    type cmd and press Ctrl+Shift+Enter
    It should be in the administrator cmd prompt.

    Type sfc /scannow

    wait till its done and once it is, check if it says Windows Resource Protection found corrupted files and successfully repaired them. If it does, exit out of cmd prompt and see if search works.

    Solution 2

    If it does not work, try going into task manager and services. Then open services scroll down to windows search and click enabled if its disabled already.

    Solution 3

    If that does not work try to rebuild the search index by going into indexing options and pressing the button called rebuild.

    Once its done rebuilding, your problem should be fixed.

    Solution 4

    If that does not work, I would suggest to restore windows 10 to a previous point.

    Right click the search bar and open task manager. Then click file and run a new task. Type Control Panel and press enter. Go to recovery and click open system restore. Click next, and choose a date that you want to restore to. Then, the next is pretty self-explanatory. Your PC will start to rebuild to match up to the restore date. It may take a few hours or if you don't have many applications or if your PC is new, it will finish in a couple of minutes. You can step away from your computer because it will restart when its done by itself. After system restore is done, try to log in. If it works then its a success! Sorry if my English is bad. If you can't understand something clearly just reply.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments
  3. Anonymous
    2021-09-23T18:52:59+00:00

    Hi, so i recently fixed the problem that you were struggling with(and I for a while). When you tried Davids cmd, I did that too. It removed the searchapp. If the search app is removed, you can't enable or disable search because none of those things will work if there's no search.

    Solution: 1

    press Win+R

    type cmd and press Ctrl+Shift+Enter
    It should be in the administrator cmd prompt.

    Type sfc /scannow

    wait till its done and once it is, check if it says Windows Resource Protection found corrupted files and successfully repaired them. If it does, exit out of cmd prompt and see if search works.

    Solution 2

    If it does not work, try going into task manager and services. Then open services scroll down to windows search and click enabled if its disabled already.

    Solution 3

    If that does not work try to rebuild the search index by going into indexing options and pressing the button called rebuild.

    Once its done rebuilding, your problem should be fixed.

    Solution 4

    If that does not work, I would suggest to restore windows 10 to a previous point.

    Right click the search bar and open task manager. Then click file and run a new task. Type Control Panel and press enter. Go to recovery and click open system restore. Click next, and choose a date that you want to restore to. Then, the next is pretty self-explanatory. Your PC will start to rebuild to match up to the restore date. It may take a few hours or if you don't have many applications or if your PC is new, it will finish in a couple of minutes. You can step away from your computer because it will restart when its done by itself. After system restore is done, try to log in. If it works then its a success! Sorry if my English is bad. If you can't understand something clearly just reply.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments
  4. Anonymous
    2021-05-19T10:25:00+00:00

    As discussed in depth above, the free software called Everything is a wonderful search program that will catalog your entire disk in a few seconds then provide instant access to all your files by partial name. Unlike the Windows builtin Cortana/Searching, it will not load your cpu or increase disk accesses to anywhere near the same amount.

    This is my last posting here on this subject, so I hope that people who are searching for a solution to their overheating CPU (thanks to Microsoft) will read this entire thread.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments