ChrisTitusTech / winutil

Chris Titus Tech's Windows Utility - Install Programs, Tweaks, Fixes, and Updates
MIT License
24.21k stars 1.47k forks source link

huge problem with Service Host: DCOM Server Process Launcher #980

Closed ChocolatCoco closed 8 months ago

ChocolatCoco commented 1 year ago

Describe the bug Before around the 20th of august, the search process was not opened automaticaly on system start (searchUI.exe) Now it opens automatically, when I close it in the task manager it instantly comes back Before it used to open only if I clicked on the search box of windows, then it would close when I click outside the searchbox

same thing for the system settings broker, it used to open when I click on the notification tray to access settings, then it would close if I click outside, now when I click, it launches it, then it doesnt close, when I close it manually in task manager it closes only then.

Same for windows installer, when I install a program, it launches windows installer, but it remains open in task manager even after the program has been installed

I also noticed a task called microsoft text input application, idk what it does.

all these things have to do and are controlled by Service Host: DCOM Server Process Launcher when I check the parent pid of the process like search box process for exemple, it always shows Service Host: DCOM Server Process Launcher as the parent.

I remember the time when system settings broker or searchUI would stop by themselves when not used. Now searchUI is always active and system settings broker will not stop after it is launched once.

I dont remember all the process that would close alone but I can guess that many other processes will have this problem of not closing even when unused. I remember that this problem didnt happen before.

Before all this, I would use CTT utility normaly, then get in the task manager's background processes around 20 process

now when I do a clean install and do everything the same and use ctt utility the same way, I get 30 process in background section of task manager, of course, I cant remember all the names and which were not there before, but the searchUI and runtime broker for the search box are a good exemple of things that used to launch only if I clicked the search box. so I guess so other background processes were also having the same problem, going from 20 to 30 is showing that this thing probably happened to other processes

I also noticed the the name of many services are followed by random numbers and letters, I noticed that the onesync service exists despite one drive not supposed to exists on LTSC

I even tried to disable cortana using ctt utility and it did nothing to solve

To Reproduce Steps to reproduce the behavior:

  1. Install LTSC 2019
  2. Run CTT utility (go to tweaks, select all essential tweaks and leave unchecked ooshutup and storage sense and disk cleanup) turn bing to off then run tweaks
  3. go to task manager and notice the things (for exemple searchUI (the searchbox process) runing without even having clicked on the search box
  4. notice the higher amount of process in the background 30 instead of 20

Expected behavior clean LTSC 2019 install install updates install best drivers with SDI driver tool have around 20 processes in the background tasks section of task manager (name is "processus en arrière-plan")

Screenshots If applicable, add screenshots to help explain your problem.

Additional context Windows LTSC 2019, does the same in LTSC2021 I tried all new drivers I tried uninstall windows updates I tried check system memory I reinstalled windows in a clean way at least 4 times trying to locate the problem all didnt work the only thing I know is that the Service Host: DCOM Server Process Launcher is launching processes that I dont use (searchUI) or maintaining other processes that should have been closed but for some reason are still maintained even after their respective program is closed.

I tried also many other things that I cant remember but at the end, even with clean installs it doesnt work when it used to work before, so I wonder if the Service Host: DCOM Server Process Launcher has been maybe vaccinated against the CTT utility by windows, maybe thats why windows auto creates duplicate services with random letters and numbers at the end. idk

I noticed certain services turned to manual have had a duplicate that runs on auto

ChocolatCoco commented 1 year ago

exemple

here is an exemple, the task is runing despite me not even using it or having clicked on it even once, it's there when I start windows as a reminder, before around the 20th of august, when I would do a clean install and everyhting the same, it would never open this searchui without me clicking on it, and even If I would click on it, it would use to close it right after I finish using the search box.

ChocolatCoco commented 1 year ago

update : I installed LTSB 2016, the problem was still there, however there are less useless processes than in windows 1809

I reach 48 processes on a clean install, as low as 36 with CTT utility on idle, then as low as 39 on idle with the ctt, and kaspersky installed. Imagine if the search box process would close, then I would have 38 processes instead of 39, maybe even lower

however because of driver compatibility, the disk has a higher temperture, it used to be 30°C now its 40°C (ssd and normal disk)

if someone knows how to prevent heat problems in LTSB 2016 feel free to share

I've read that the so called dch drivers (idk what that is) are not compatible with 1607 so when I use SDI driver tool it cant get some intel drivers (error 103)

why is LTSC 2019 not like 2016 ? if there was a way to turn LTSC 2019 into 2016 by comparing the processes that run and keeping the useful ones it would be good. why did microsoft made 1607 better than 1809 and 1809 better than 21h2 ? Following this trend it could probably mean that 1507 would be even better than 1607. now I want to try 1507 just to see

github-actions[bot] commented 8 months ago

Closed due to inactivity