I'm a newby. But I noticed that my CPU runs at 100% only after installing the service pack 1. This seems odd. But I've done 3 total restores, back to factory settings. I never have this problem before the service pack - only after.
Open Resource Monitor and switch to CPU tab. Sort by CPU on Processes and Services, see which one is consuming the CPU. Report back.
What operating system did your Toshiba satellite come with?
Does it have one of these stickers from Microsoft?
Are you trying to go from Windows 8 to Windows 7?
Hi and welcome to SevenForums,
High cpu usage has been a common item of late,
Be one of the first to follow instruction on what is consuming the resources :)
Resource Monitor
Oh, a tutorial for Resource Monitor, swiftly added to FavoritesBets for svchost.exe (netsvcs)?
I have seen this 100% CPU usage issue on my own machine a few times especially after installing SP1 following a fresh install of windows. Possibly this explains it:
What is mscorsvw.exe and why is it eating up my CPU? What is this new CLR Optimization Service?
Also see:One important thing is that while you may see 100% CPU usage, the compilation happens in a process with low priority, so it tries not to steal the CPU for other stuff you are doing
Windows 7 computer slow after SP1 upgrade due to high mscorsvw.exe CPU usage
to GokAy.
It is the svchost.exe.
I believe it has something to do with the windows update setting.
The only way to stop it is to "end process".
Can I upgrade to Win10 without it?
Can you open Resource Monitor, switch to CPU tab and confirm it is "svchost (netsvcs)"?
If so, stop and disable in Services (services.msc):
- SuperFetch (sometimes needed)
- Background Intelligent Transfer Service (BITS)
- Windows Update
Restart PC.
Then download https://support.microsoft.com/en-us/kb/3050265
If you get service not running or similar error, switch Windows Update to Auto (delayed) and start it.
And install the KB without waiting.
Change BITS back to Auto (delayed), restart PC.
If ok, change SuperFetch to Auto and restart.
Thanks for the help.
But I decided to circumvent the problem by upgrading to Windows 10.
Quote