cpu heat/cpu fan noise, always “Service Host: Windows Update” on top.

Topic

New Reply

[a]

always “Service Host: Windows Update” on top.

always lasts for a while.

Seems to happen frequently.

I use WuMgr so WU shouldn’t actually be doing anything.

WHY?

 

noticed this and expanded it but still there after reboot so apparently always there. correct?

• This topic was modified 2 years, 9 months ago by a.
• This topic was modified 2 years, 9 months ago by a.
• This topic was modified 2 years, 9 months ago by a.

Reply | Quote

Replies

Is this happening all the time, intermittently, or just for a period following a reboot?

According to Task Manager your CPU is running at 51%, which would account for the cpu heat/cpu fan noise.

Hopefully someone with experience using WuMgr will speak up with some advice on that Windows Update task. I replied because of “cpu heat/cpu fan noise” in the headline.

Windows 10 Pro 22H2

Reply | Quote

This happens perhaps every other day and lasts for maybe 10 minutes. It does not necessarily start with a re-boot. i can  be working along and suddenly hear the fan cranking, and check task mgr and sure enough. This laptop gets rebooted at least once every day.

The Service Host: Windows Update is the task that is using the most cpu and thus causing the increased heat and fan speed/noise. The fan speed is determined by cpu temperature. Automatically. In every computer.

The question is WHY is that task running??

Reply | Quote

“WuMgr (Update Manager for Windows) is a tool to manage updates of Microsoft products on the Windows operating system. It uses the “Windows Update Agent API” to identify as well as download and install missing updates. It allows the user fine control of updates on modern (Windows 10) operating system versions, comparable to what windows 7 and 8.1 offered.”

I’ve never used it so I can’t say for sure, but it would appear the WuMgr is checking for updates periodically.  “Service Host: Windows Update” is “Windows Update Agent API”.

Always create a fresh drive image before making system changes/Windows updates; you may need to start over!

We all have our own reasons for doing the things that we do with our systems; we don't need anyone's approval, and we don't all have to do the same things.

We were all once "Average Users".

Computer Specs

Reply | Quote

a wrote:

The Service Host: Windows Update is the task that is using the most cpu and thus causing the increased heat and fan speed/noise. The fan speed is determined by cpu temperature. Automatically. In every computer.

Understood. The fans are just doing their job, and the noise is evidently what raised your awareness of the task running.

You might want to consider editing your topic headline to be more focused on the real issue. Why is that WU task running? That might attract more readers to your actual issue.

The current headline reads like a potential hardware issue. Just my two cents!

Good luck!

Windows 10 Pro 22H2

Reply | Quote

No way I know of to change a topic headline. I think first post makes it clear that I am asking WHY WU is being run so often.

WuMgr is set to “Disable Automatic Update” yet WU (NOT WuMgr) is apparently doing something anyway, and frequently. But I surmise that nobody knows what…

Reply | Quote

a wrote:

WuMgr is set to “Disable Automatic Update” yet WU (NOT WuMgr) is apparently doing something anyway, and frequently. But I surmise that nobody knows what…

“This freeware identifies which update is missing on the computer and it downloads them.”

WuMgr is using “Service Host: Windows Update” to identify which update is missing.  Yes, it disables Automatic Update, but it still uses the Windows Update Agent API in order to accomplish that.  Every search entry I’ve found explains that.

So yes, what it is doing is known.

Always create a fresh drive image before making system changes/Windows updates; you may need to start over!

We all have our own reasons for doing the things that we do with our systems; we don't need anyone's approval, and we don't all have to do the same things.

We were all once "Average Users".

Computer Specs

Reply | Quote

When I open WuMgr and click on the circle-arrows and thus ask it to check and see what is available, “Service Host: Windows Update” does NOT pop up in the task manager.

I do not believe WuMgr is instigating “Service Host: Windows Update”. I believe old WU is doing it, though I am not sure why or how to change that. I have tried one thing and will see. If WuMgr were running “Service Host: Windows Update”, when it was finished I would get a popup telling me what it had found, but that is not part of the Santos module.

https://github.com/DavidXanatos/wumgr

Reply | Quote

“windows update facilitators”…

control panel / windows tools / task scheduler

Task Scheduler >Task Scheduler Library > Microsoft > Windows > UpdateOrchestrator

every 7 hours apparently.

Reply | Quote

Yeah, this is too zealous – once every couple of weeks or so more would be sufficient. You can try getting rid of it or changing the task(s) with these solutions here. This annoyance may come standard in newer releases from Microsoft now, but it seems to have famously appeared in one of several poison pill updates in older releases.

Hope this Helps…

Reply | Quote

Yeah.

That box “Disable Update Facilitators” in WuMgr (see pic above) interested me so I checked it and haven’t seen problem since and things like backups run faster. I will report back in a few more days as to whether that has fixed it. Else I will change the task scheduler line listed above and see if that gets rid of it, but they are probably the same thing. WuMgr is just a gate keeper (and a damn handy one!!!) doesn’t really “change” WU but allows or disallows it to function.

Reply | Quote

That did NOT fix the issue so I am trying the “disable the Update Orchestrator in Task Scheduler” route :

https://www.askwoody.com/forums/topic/logged-in-to-my-admin-account-but-task-sched-says-not-have-permission/#post-2466423

and will report further successes/failures in that thread. Thanks all!

Reply | Quote

I’m glad you were able to neutralize Update Orchestrator.

Reply | Quote

No. doesn’t work. See other thread for comment.

Reply | Quote