Am curious if there's any downside to wiping out SearchApp.exe?
<1> Open an admin window
<2> cd %windir%\SystemApps
<3> taskkill /f /im SearchApp.exe
The next step has to be done within a second or two.
Otherwise a new SearchApp.exe process is spawned.
Keep trying until you get the timing fast enough.
Best to type the taskkill and paste the move instantly thereafter.
<4> move Microsoft.Windows.Search_cw5n1h2txyewy Microsoft.Windows.Search_cw5n1h2txyewy.old
Obviously I never use the Windows search feature (it doesn't do anything useful). Assuming that I don't care for Windows search, is there any
downside that you can think of before I do it for real?
Am curious if there's any downside to wiping out SearchApp.exe?
<1> Open an admin window
<2> cd %windir%\SystemApps
<3> taskkill /f /im SearchApp.exe
The next step has to be done within a second or two.
Otherwise a new SearchApp.exe process is spawned.
Keep trying until you get the timing fast enough.
Best to type the taskkill and paste the move instantly thereafter.
<4> move Microsoft.Windows.Search_cw5n1h2txyewy Microsoft.Windows.Search_cw5n1h2txyewy.old
If you really want to turn off search indexing, why not just go to Services.msc, select Windows Search, stop it, and then set it to
Disabled?
Hopefully, the ownership should stop you. It would not
be Windows, if that did not happen, right ?
In any case, I did it from Linux,
mv SearchApp.exe SearchApp.exe.old
and it worked.
Now, I reboot to Windows. No pissy notifications on the screen (surprising!).
The side effects include not being able to stick the cursor in
a search box in Windows. The system knows the search agent is
unregistered.
But the ease with which I did this from Linux, is puzzling.
I was expecting a fight.
fsutil behavior query disablecompression
DisableCompression = 0 (so it was not disabled by me)
Really weird, that it was so easy to do.
And I visited Windows Update, and it did not become wobbly. I
was expecting some "feedback" about search.
Summary: Clear sailing here. No problemo so far (in my W10 VM).
On 13 Feb 2023 at 9:59:16 AM, Stan Brown <the_stan_brown@fastmail.fm>
wrote:
If you really want to turn off search indexing, why not just go to
Services.msc, select Windows Search, stop it, and then set it to
Disabled?
Why not? Well. Sir. I'll tell you why not.
You asked bloody why not, right?
Ahem! You sir! You challenged me sir!
(I'm stalling. I'm trying to think of a witty reply while I'm stalling.)
Sheesh. The real answer is that I didn't know how to do that.
Not until you just said so. That's why.
I just did it.
<1> Windows+R services.msc
<2> Windows Search > General > Stop
<3> Windows Search > General > Startup type > Disabled
Thanks! :->
RJH wrote:
<1> Windows+R services.msc
<2> Windows Search > General > Stop
<3> Windows Search > General > Startup type > Disabled
Check after a reboot and see if that control has
been altered on you.
Check after a reboot and see if that control has
been altered on you.
Alternatively there's an "Indexing Options" icon within control panel,
you can tell it not to index any folders, then delete and rebuild the
index, which would be empty at that point, and take it no time to run
when it felt like doing so.
In the days of spinning discs, I used to disable it, now I don't notice
it running.
Alternative solution.
<1> Windows+R control.exe
<2> All control panel items > View by "Small icons" > Indexing Options
<3> ?
I've never found Windows search to be of any use at all. Have you?
<3> click Modify, then expand the folder tree and untick every folder
that you don't want indexed (possibly all of them)
<4> click advanced and then click rebuild
I've never found Windows search to be of any use at all. Have you?
No, because I've used different search tools that don't chang with every version of windows.
BTW, what is this "thing" anyway? Is it an executable?
On 14 Feb 2023 at 8:27:04 PM, Andy Burns <usenet@andyburns.uk> wrote:
<3> click Modify, then expand the folder tree and untick every folder
that you don't want indexed (possibly all of them)
<4> click advanced and then click rebuild
Got it. Thanks. This is a perfect example of how this newsgroup works for us! >This is useful for the archives too, so that it's useful for everyone later. >For that, I'll summarize the solution that remained after a Windows Update.
Recommended solution. (survives Windows Update)
<1> Windows+R services.msc
<2> Windows Search > General > Stop
<3> Windows Search > General > Startup type > Disabled
Alternative solution. (survives Windows Update)
<1> Windows+R control.exe
<2> All control panel items > View by > Small icons
<3> Indexing Options > Modify > then expand the folder tree
<4> Untick every folder that you don't want indexed (possibly all of them)
<5> Advanced > Rebuild
Deprecated solution. (does not survive Windows Update)
<1> Windows+R cmd {control+shift+enter}
<2> cd %Windir%\SystemApps
<3> copy (but do not yet paste!) this into your clipboard
move Microsoft.Windows.Search_cw5n1h2txyewy Microsoft.Windows.Search_cw5n1h2txyewy.old
<4> taskkill /f /im SearchApp.exe
<5> Immediately paste your clipboard contents into the window!
I've never found Windows search to be of any use at all. Have you?
No, because I've used different search tools that don't chang with every
version of windows.
Between you and me, I can't imagine that anyone finds Windows Search useful.
All it does, for me, is annoy me by wasting cpu cycles doing its indexing.
To Paul's concern, I happened to get a Windows Update yesterday.
<1> Windows+R winver (Version 21H2 (OS Build 19044.2604)
<2> Windows+R cmd > ver
Microsoft Windows [Version 10.0.19044.2604]
<3> Windows+R cmd > wmic os get buildnumber,caption,CSDVersion /format:csv
A,19044,Microsoft Windows 10 Pro,
<4> Windows+R cmd > wmic os get Caption,CSDVersion /value
Paul was correct about "funny stuff" happening after a Windows update.
The service remained disabled.
The indexing remained excluded.
But the SystemApps "thing" came back.
Directory of C:\Windows\SystemApps
02/15/2023 06:58 AM <DIR> Microsoft.Windows.Search_cw5n1h2txyewy
01/29/2023 04:56 AM <DIR> Microsoft.Windows.Search_cw5n1h2txyewy.old
BTW, what is this "thing" anyway? Is it an executable?
On 15 Feb 2023 at 7:23:25 AM, RJH <patchmoney@gmx.com> wrote:
BTW, what is this "thing" anyway? Is it an executable?
Apparently it's a "directory" of some sort.
But the more important report is that I spoke too soon.
The Valentines Day Windows Update undid some of the clever subterfuge.
I hadn't expected a hundred "SearchApp.exe" threads in the task manager.
But there they are. https://i.postimg.cc/4drfH6ts/clipboard01.jpg
Why are there a hundred searchapp.exe threads doing anything at all?
If the search is properly disabled, why would they be running?
Let me move it so that at least it won't activate all those threads.
Windows+R cmd {control+shift+enter}
cd %Windir%\SystemApps
C:\Windows\SystemApps> move Microsoft.Windows.Search_cw5n1h2txyewy Microsoft.Windows.Search_cw5n1h2txyewy.bck
The process cannot access the file because it is being used by another process.
0 dir(s) moved.
C:\Windows\SystemApps> taskkill /f /im SearchApp.exe
SUCCESS: The process "SearchApp.exe" with PID 2384 has been terminated.
C:\Windows\SystemApps> move Microsoft.Windows.Search_cw5n1h2txyewy Microsoft.Windows.Search_cw5n1h2txyewy.bck
1 dir(s) moved.
The move seems to have killed the hundred SearchApp.exe threads (how?). https://i.postimg.cc/y8K3QZdL/clipboard02.jpg
All that was left are the following threads (processes?).
procexp64.exe 1096 Key HKLM\SYSTEM\ControlSet001\Services\WSearchIdxPi\Performance
procexp64.exe 1096 Mutant \Sessions\1\BaseNamedObjects\WSearchIdxPi_Perf_Library_Lock_PID_448
explorer.exe 4292 DLL C:\Windows\System32\Windows.Storage.Search.dll explorer.exe 4292 Key HKCU\SOFTWARE\Microsoft\Windows\CurrentVersion\Search
explorer.exe 4292 Key HKLM\SOFTWARE\Microsoft\Internet Explorer\SearchScopes\{0633EE93-D776-472f-A0FF-E1416B8B2E3A}
explorer.exe 4292 Key HKLM\SOFTWARE\Microsoft\Windows Search\CrawlScopeManager\Windows\SystemIndex\SearchRoots
explorer.exe 4292 Key HKLM\SOFTWARE\Microsoft\Internet Explorer\SearchScopes
The main conundrum is why there were a hundred SearchApp.exe threads?
It seems the only way to stop them, so far anyway, is the original move.
Every search box on the machine, likely hooks into the search
system, so there would be a thread for each one.
As for the package folder coming back, it's hard to say for sure
what happened. It could be that search got patched on Patch Tuesday.
Or, the OS decided that the "inventory did not match the goods"
and did some DISM work to fix the package structure.
Windows has a mix of stuff that is protected by signing, and
stuff that is not protected by signing. If you download an App
from the Microsoft App Store, the integrity of those packages are
checked. The manifest file contains info about the package.
But whether the entire WinSxS is protected that way, I couldn't say.
The WinSxS undoubtedly gets scanned enough times during the day,
for that kind of checking to be done. The state of it might be
checked any time a Windows Update run is scheduled.
But so far, I have not been able to detect a completely autonomous
repair scheme. It was my biggest fear, they would design one, and
if they had, there would be "unintended consequences", such as
every Windows computer in the world not able to boot or function
on a certain Wednesday. It's like when your AV (with good intentions)
has a false positive, and quarantines critical OS resources. It's all
fun and games, until it won't boot.
Between you and me, I can't imagine that anyone finds Windows Search useful.
I use Windows search only occasionally, when I want to find and run a program I don't have a shortcut for, but remember the name of. For
everything else I use everything.exe.
On 15 Feb 2023 at 4:21:51 PM, Paul <nospam@needed.invalid> wrote:
Every search box on the machine, likely hooks into the search
system, so there would be a thread for each one.
Thanks for that assumption because I didn't even look at first because
I thought I had killed it. After moving the search folder, they're gone now.
As for the package folder coming back, it's hard to say for sure
what happened. It could be that search got patched on Patch Tuesday.
Or, the OS decided that the "inventory did not match the goods"
and did some DISM work to fix the package structure.
If the search was patched, would the date for everyone be the new date? C:\Windows\SystemApps> dir *Search*
02/15/2023 06:58 AM <DIR> Microsoft.Windows.Search_cw5n1h2txyewy.bck
01/29/2023 04:56 AM <DIR> Microsoft.Windows.Search_cw5n1h2txyewy.old
Windows has a mix of stuff that is protected by signing, and
stuff that is not protected by signing. If you download an App
from the Microsoft App Store, the integrity of those packages are
checked. The manifest file contains info about the package.
Luckily, I never download any apps from the Microsoft Store.
I certainly don't have a MS account although I know many don't need it.
But whether the entire WinSxS is protected that way, I couldn't say.
The WinSxS undoubtedly gets scanned enough times during the day,
for that kind of checking to be done. The state of it might be
checked any time a Windows Update run is scheduled.
I remember some kind of "dism" fix for when something gets corrupted.
I don't remember exactly how to run it but if I remember, I'll try it.
If it comes back from that chkdsk/dism sequence, then you're right!
But so far, I have not been able to detect a completely autonomous
repair scheme. It was my biggest fear, they would design one, and
if they had, there would be "unintended consequences", such as
every Windows computer in the world not able to boot or function
on a certain Wednesday. It's like when your AV (with good intentions)
has a false positive, and quarantines critical OS resources. It's all
fun and games, until it won't boot.
I'm looking to see what's using up CPU resources where SearchApp.exe
was near the top so now I'm digging deeper. I don't know what to do
with the many svchost.exe processes (I've never understood them.)
To me any one of them can be a rogue app since they're all the same name. https://i.postimg.cc/13W5G7sV/clipboard03.jpg
What do you do to figure out what any one svchost is doing on your PC?
On 2023-02-15 08:47:06 +0000, Ken Blake said:
Between you and me, I can't imagine that anyone finds Windows Search useful.
I use Windows search only occasionally, when I want to find and run a
program I don't have a shortcut for, but remember the name of. For
everything else I use everything.exe.
It's not a surprise at all that you would find something as useless as the Search feature useful since you only do what others tell you what to do.
You're stupid.
You can't help anyone. You never can. You never could. You never will.
You only prove you're stupid every single time you post to this newsgroup.
tasklist /svc
and I can't find wuauserv now.tasklist /svc | findstr wuauserv
The Search service works.
But you have to set it up.
It's not the epitome of stability. It starts
re-indexing when not commanded to do so. Search
is then degraded until it finishes. It can take
24 hours of computing, to finish a re-index.
Microsoft admits it does not scale above 1 million files.
The test I've carried out on it, was with 1 million files
(on the other computer).
It works sometimes, but depending on what you ask it,
it can take three to five minutes to answer.
One of your first chores, is finding the web page with the *current*
search language. This was a problem, even back in Windows XP days!
How can you use a product, if there's no Help?
Third party searches can be simpler, mainly focused on filenames,
and for many people, this is the most frequent kind of search.
If Windows Search takes 3 seconds one time and 5 minutes the next,
who needs that exactly ??? It all depends what mood it is in,
as to what happens. It is not "Apple Magical". If Jobs were here,
he would kick the ass of the individual who wrote WS.
You can do a Windows Search from a script. Someone posted a chunk of
script code to call Windows Search from powershell. And this avoids
the wasted time when File Explorer tries to draw the results. Part
of the wasted time, is wasted by File Explorer. In 3 minutes,
it can find 50,000 items.
But this is all novelty stuff, when you want to get something done.
If I go back to my Mac G4, I used to whine that it was "slow" on
search. However, compared to Windows Search, it's a cheetah. It
has consistent search times (search 20 partitions in about 20 seconds),
and short of using Everything.exe , you're not going to beat it for
speed. Part of this is likely due to the file table scheme used.
There were likely on the order of a million files on that setup too.
I've done the work. And I'm not impressed. But at least some times,
it settles down. Occasionally, on the more modern Windows, the
search service does not even start in a timely manner, and it
is "not running" when you go to use it. How cool is that ???
On 2/13/2023 8:23 PM, RJH wrote:
On 13 Feb 2023 at 9:59:16 AM, Stan Brown <the_stan_brown@fastmail.fm>
wrote:
If you really want to turn off search indexing, why not just go to
Services.msc, select Windows Search, stop it, and then set it to
Disabled?
Why not? Well. Sir. I'll tell you why not.
You asked bloody why not, right?
Ahem! You sir! You challenged me sir!
(I'm stalling. I'm trying to think of a witty reply while I'm stalling.)
Sheesh. The real answer is that I didn't know how to do that.
Not until you just said so. That's why.
I just did it.
<1> Windows+R services.msc
<2> Windows Search > General > Stop
<3> Windows Search > General > Startup type > Disabled
Thanks! :->
Check after a reboot and see if that control has
been altered on you.
There is a certain level of aggression around
search. This is why I was expecting trouble,
because it has a history of being aggressive
(infinite services restarts instead of three service restarts).
Because there's a Bing module in that folder (SearchApp folder),
it could be tied into recording the things you do on
the computer, which is why the subsystem should be
aggressive.
And it could be, that SearchApp keeps tabs on Search Service,
and maybe it is the thing that restarts the service. Since
you killed the SearchApp.exe first, maybe that will change
the outcome of the experiment (of disabling the service). Microsoft
uses a tag-team approach, like a malware would, for things
it wants to have running on the machine. They will use a
"second" software, to make sure the "first" software is
running and has not croaked. Scheduled Tasks can be wired up
for this stuff, too.
On 15 Feb 2023 at 11:31:24 AM, Paul <nospam@needed.invalid> wrote:
tasklist /svc
and I can't find wuauserv now.tasklist /svc | findstr wuauserv
svchost.exe 6860 wuauserv
Am I supposed to kill whatever that is doing? wuauserv?https://www.google.com/search?q=what+is+wuauserv.exe
https://www.minitool.com/lib/wuauserv.html
"Wuauserv is the Windows Update Service, which is responsible for automatically downloading and installing software created by Microsoft"
In services.msc my "Windows Update" is set to manual.
What is your recommendation?
The biggest "hog" now in my system is "MSMpEng.exe" but I can't kill that because it's the antivirus I think. I couldn't even lower the Affinity because it wouldn't let me change the number of CPUs that it runs on.
On 14 Feb 2023 at 8:27:04 PM, Andy Burns <usenet@andyburns.uk> wrote:
<3> click Modify, then expand the folder tree and untick every folder
that you don't want indexed (possibly all of them)
<4> click advanced and then click rebuild
Got it. Thanks. This is a perfect example of how this newsgroup works for us! >This is useful for the archives too, so that it's useful for everyone later. >For that, I'll summarize the solution that remained after a Windows Update.
Recommended solution. (survives Windows Update)
<1> Windows+R services.msc
<2> Windows Search > General > Stop
<3> Windows Search > General > Startup type > Disabled
It was that simple in Windows too!You could have put that in a batch .BAT file and there would no worry about timing.
<1> Open an admin window
<2> cd %windir%\SystemApps
<3> copy (but do not yet paste!) this into your clipboard
move Microsoft.Windows.Search_cw5n1h2txyewy Microsoft.Windows.Search_cw5n1h2txyewy.old
<4> taskkill /f /im SearchApp.exe
<5> Immediately paste your clipboard contents into the window!
It took a few tries before I realized I had to be fast.
But then it gave up without a fight.
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 297 |
| Nodes: | 16 (2 / 14) |
| Uptime: | 10:57:34 |
| Calls: | 6,666 |
| Files: | 12,213 |
| Messages: | 5,336,371 |
