Fall update v.1709 creates problems: CPU usage and Desktop wallpaper

I may have fixed the wallpaper issue by logging on to a Microsoft account instead of a local account.... the excessive CPU usage remains,

bardos said:

I may have fixed the wallpaper issue by logging on to a Microsoft account instead of a local account...,

If it only happens in one local account it may have a corrupt profile. Try another local account as a check.

bardos said:

In MSCONFIG/Services, it does not appear... still draining 25% or so...

Enable it back in the services, to make it appear in the msconfig. Then uncheck.

bardos said:

Service Host: Local Service (No Network) (3) is draining 35%

Expand group to see what exactly drains. I suppose it will be "Superfetch".

I have the same issue after the Fall update. The CPU usage of these 2 services is constant.

Service Host: Local Service (No Network) (3) - CPU is constantly around 15%
Service Host: Internet Connection Sharing (ICS) - CPU is constantly around 10%

I've tried to disable ICS in Services and msconfig, and no matter what I do, it always starts automatically and keeps running.

Here is the screenshot from Task manager:

splus said:

I have the same issue after the Fall update. The CPU usage of these 2 services is constant.

Service Host: Local Service (No Network) (3) - CPU is constantly around 15%
Service Host: Internet Connection Sharing (ICS) - CPU is constantly around 10%

I've tried to disable ICS in Services and msconfig, and no matter what I do, it always starts automatically and keeps running.

Here is the screenshot from Task manager:

Haha... you were lucky. Mine were using 40% and 25%... So, after following some of the tips from this thread and googling my brains out and following various tips, none really related to this new v1709 cause it's way too soon, and coming up empty on results, I found the absolute fix.

I went back to version 1703 with which I was more than happy. There must be other folks out there with the same problem and maybe it'll get fixed. When it does, I'll experiment once more with v1709. I make images of my C:\ drive so it was pretty easy to go backwards. I did not use the built in Windows system to do it.

bardos said:

Haha... you were lucky. Mine were using 40% and 25%... So, after following some of the tips from this thread and googling my brains out and following various tips, none really related to this new v1709 cause it's way too soon, and coming up empty on results, I found the absolute fix.

I went back to version 1703 with which I was more than happy. There must be other folks out there with the same problem and maybe it'll get fixed. When it does, I'll experiment once more with v1709. I make images of my C:\ drive so it was pretty easy to go backwards. I did not use the built in Windows system to do it.

My situation is exactly the same as yours. I have tried SFC and DISM three times (as suggested in the official Microsoft answer.
I still get the following message after the SFC check.

Code:

Windows Resource Protection found corrupt files but was unable to fix someof them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. Forexample C:\Windows\Logs\CBS\CBS.log. Note that logging is currently notsupported in offline servicing scenarios.

Any idea on how to solve this issue? I can't revert back to the previous version because of running out disk space, so no longer have the old files...

Thanks

littlegtplr said:

My situation is exactly the same as yours. I have tried SFC and DISM three times (as suggested in the official Microsoft answer.
I still get the following message after the SFC check.

Code:

Windows Resource Protection found corrupt files but was unable to fix someof them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. Forexample C:\Windows\Logs\CBS\CBS.log. Note that logging is currently notsupported in offline servicing scenarios.

Any idea on how to solve this issue? I can't revert back to the previous version because of running out disk space, so no longer have the old files...

Thanks

What about using your win 10 dvd to do a recovery install... could work to get you back on track even if it's 1511 or 1607

bardos said:

What about using your win 10 dvd to do a recovery install... could work to get you back on track even if it's 1511 or 1607

The windows came with my laptop, and the recovery partition was gone due to some reason a long time ago. But I guess a Window 10 Image should do the trick? Thanks for the thoughts. It's really annoying to have windows updated but with such issues....

littlegtplr said:

My situation is exactly the same as yours. I have tried SFC and DISM three times (as suggested in the official Microsoft answer.
I still get the following message after the SFC check.

Code:

Windows Resource Protection found corrupt files but was unable to fix someof them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. Forexample C:\Windows\Logs\CBS\CBS.log. Note that logging is currently notsupported in offline servicing scenarios.

Any idea on how to solve this issue? I can't revert back to the previous version because of running out disk space, so no longer have the old files...

Thanks

An update: after terminating the ICS, the cpu got back to normal for a while, before another 'blank' (no name) Service Host entry showed up and occupying the cpu again. And I terminated it again, and again, and probably again (I don't remember how many time killing the blank entry, possibly 3-4 times). Then it's normal now (20 mins so far).

Not sure if this will help the situation with others, but just to share the observation.

This is what did the trick for me: I disabled and re-enabled from the settings app the Windows firewall.