Nothing solved this problem. I decided to re-install OS from scratch. First deleted system partition, then made new partition and installed Windows 7 Premium SP1 from DVD and installed nothing else but necessary drivers. System was working fine. Normal cpu level, no svchost hogging cpu.. Then I connected the computer to Internet and tried to update Windows 7.
The update problem appeared immediately! This was a fresh install, with no programs installed, and nothing added from backup. That means: no corrupted system files, and no virus. I decided to restore latest working system backup March After system restore, I deactivated wuauserv immediately, and set windows update to never search for updates.
Then I connected to Internet and updated my antivirus program. The system is still working fine. It seems that the problem with svchost-wuauserv high cpu usage starts with, and is caused by attempts at windows update.
Until mid Juliy this problem did not exist at my computer, since last successful update was done then, and I noticed the problem shortly after. No system files are corrupted before attempts at windows update on at clean install. It is clear to me that windows update is causing this problem. I think Microsoft may have changed the way updates are done since July , and the result is that some computers with Windows 7 cannot download updates anymore.
Hackers, welcome to my computer! One workaround can be to use a tool like Wsus offline or Autopatcher. The next time you need to Ask a Question start a new thread by clicking Participate towards the top of this page or the page accessed from the link below and click Ask a question on the drop down menu.
Access your profile. Make sure you have signed in. Click on All Threads, click on the Star towards the top right of the screen you will need to press F11 to see it if you are reading Full Screen , click the scroll to the right of Add to Favourites and select Add to Favourites Bar. Edit the long name to something memorable and you can immediately access your threads from your Internet Explorer Home Page.
Threats include any threat of suicide, violence, or harm to another. Any content of an adult theme or inappropriate to a community web site. Any image, link, or discussion of nudity. Any behavior that is insulting, rude, vulgar, desecrating, or showing disrespect.
Any behavior that appears to violate End user license agreements, including providing product keys or links to pirated software. Unsolicited bulk mail or bulk advertising. Any link to or advocacy of virus, spyware, malware, or phishing sites. Any other inappropriate content or behavior as defined by the Terms of Use or Code of Conduct. Any image, link, or discussion related to child pornography, child nudity, or other child abuse or exploitation.
Details required : characters remaining Cancel Submit. What would be the solution to bring my Windows Updater back to normal? This thread is locked.
You can follow the question or vote as helpful, but you cannot reply to this thread. I have the same question By default if you're using Windows Server or a later version of Windows, the Costly performance counters are disabled starting from the following Cumulative Updates:.
After the cumulative update is installed, if you need the classes that are related to the Costly performance counters, set the value Enable Costly Providers to 1 DWORD under the following registry subkey to make them available again:.
The cumulative update will not affect the behavior when a process is using a large number of handles. This issue happens when a client is querying the performance classes. This is usually a monitoring application. As a workaround, you can also disable the monitoring application to prevent the creation of the performance classes. WMI provides several performance classes. For more information, see Performance Counter Classes.
These classes are created dynamically based on the Performance Counters that are available on the system. All the classes are created at the same time, not only the classes that are being queried. WMIPerfClass is the module that handles creating these classes when the WMI client queries any of them or enumerates the available classes. These performance classes are stored in a cache that's invalidated after 15 to 20 minutes. On System and Security screen, click on System. On the System screen, click on Advanced system settings link in the side menu.
On the next screen, click on Advanced tab and click on the Settings button in Performance section. Make sure you Restart the computer for above changes to be implemented. Right-click on Start button and click on Device Manager.
0コメント