NTLite does not remove Search completely - or I'm missing something

M

mkaracsony81

New Member
Hi,

I have a laptop with just 2gb ram and trying to make Windows 10 working on it by removing some memory intensive stuff (defender, search...etc). I thought I removed Windows Search but when I checked the memory usage Resource Monitor said "SearchApp.exe" is up and running. So what gives? Is this an error or am I missing something? Thank you in advance.
 

Attachments

  • Auto-saved session {DF257C5C-0650-4DB5-A70A-0F2128EE99E9}.xml
    42.7 KB
  • IMG_20201003_144542.jpg
    IMG_20201003_144542.jpg
    366.6 KB
on occasion some parts of a removed component may need to be kept for compatibilities for the remaining stuff to work correctly, this may or may not be one of them. i would look at a ram upgrade if possible, i always used to run 4gb and that used to be very tight at times.
 
I was going for a RAM upgrade in the first place since it's a no-brainer, but that's not an option since the RAM is soldered to the motherboard with no extra slots available... Removing stuff with NTLite is my only viable course of action at the moment. It would be nice to know what this "SearchApp.exe" is needed for though so then I could make an informed decision if I want to sacrifice that specific component or not. Any ideas? I'm trying to save this thing from going to the landfill.
 
ahh, you got a hardware limitation, fair enough. are you running the ARM version by any chance, if you are then there is a thread here by an ARM user you may find helpful. even if you are not on ARM it may still be worth a look, its a fairly recent thread. i dont work with w10 anymore and i cant help you, wait for nuhi.
 
Thank you for the suggestion. "Search" is my main target because when I removed it in 1809 that worked wonders in terms of both CPU and RAM usage. Instead of the usual 800-900Mb usage the RAM usage was floating around 500-600Mb which is more tolerable. This machine has a dual core CPU with no Hyper-Threading so CPU is an issue here as well. I'll wait till Nuhi sees this message. I hope there is a way to remove that resource-hog process. Is there a way to mark this thread to make sure Nuhi sees it? Again, thank you for your help.
 
yep, wait for nuhi. crippling search and indexing makes a big difference.
i treated every new windows 10 build like a new os because although there are many similarities there can also be many differences, tweaks and removals that worked on xxx1 dont work on xxx2.
 
mkaracsony81 said:
Hi,

I have a laptop with just 2gb ram and trying to make Windows 10 working on it by removing some memory intensive stuff (defender, search...etc). I thought I removed Windows Search but when I checked the memory usage Resource Monitor said "SearchApp.exe" is up and running. So what gives? Is this an error or am I missing something? Thank you in advance.
Click to expand...
Go to 'Page Components':
|---Windows Apps​
|---System App​
|--- Search App​
 
mkaracsony81 said:
I didn't realize that the search app and the search service was separate in 2004. Thank you.
Click to expand...
I have read somewhere that removing Cortana doesn't break Search, now I see, it comes apart.

Ms is changing everything to apps, some components every 6 months at a time.
 
mkaracsony81 said:
I didn't realize that the search app and the search service was separate in 2004. Thank you.
Click to expand...

They have always been separated. Cortana and Search app that were connected but were separated in the version 2004.

You may not have seen that Start Menu (StartMenuExperienceHost) now depends on the Search app too so you have to remove the 2 if you want to get rid of the Search app. In that case you will need to use Open-Shell or StartisBack to get the start menu.
 
AeonX said:
They have always been separated. Cortana and Search app that were connected but were separated in the version 2004.

You may not have seen that Start Menu (StartMenuExperienceHost) now depends on the Search app too so you have to remove the 2 if you want to get rid of the Search app. In that case you will need to use Open-Shell or StartisBack to get the start menu.
Click to expand...
I see. Thank you for the explanation. I'll just stick to 1909 for now as I need the Start Menu and I don't want to use any 3rd party apps for stuff I need working out of the box.
 
You must log in or register to reply here.
Back
Top