kavorka Posted April 20, 2011 Share Posted April 20, 2011 I've done clean installations of Win 7 with SP1 x32 (MSDN iso) on both virtual and real systems, and all of them report Even 10 WMI errors in event viewer on every boot. Event filter with query "SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 99" could not be reactivated in namespace "//./root/CIMV2" because of error 0x80041003. Events cannot be delivered through this filter until the problem is corrected.After googling it seems that this is a known issue with previous versions of Windows, (Microsoft Support), although all my pre-SP1 Win 7 machines actually do not have this error. What I would like to know is, has anyone figured out a real fix? It doesn't seem to affect system stability, but it's rather annoying to see error reports flooding the event viewer. Link to comment Share on other sites More sharing options...
MagicAndre1981 Posted April 20, 2011 Share Posted April 20, 2011 this also happened after Vista Sp1. Run the script to stop it. Link to comment Share on other sites More sharing options...
kavorka Posted April 20, 2011 Author Share Posted April 20, 2011 Andre do you get the error too? Link to comment Share on other sites More sharing options...
MagicAndre1981 Posted April 20, 2011 Share Posted April 20, 2011 yes (Win7 y64 Sp1) Link to comment Share on other sites More sharing options...
kavorka Posted April 20, 2011 Author Share Posted April 20, 2011 OK maybe I'll just have to ignore it. Win 7 was fine, I don't know why Microsoft has to create new errors with SP1. Link to comment Share on other sites More sharing options...
MagicAndre1981 Posted April 20, 2011 Share Posted April 20, 2011 same was in Vista, too. I don't know why this happens. Apply the script from the KB article. Link to comment Share on other sites More sharing options...
myselfidem Posted April 21, 2011 Share Posted April 21, 2011 Using sysprep method to integrate SP1 inside my Windows 7 Ultimate x86, I haven't this problem with WMI errors! Weird. Link to comment Share on other sites More sharing options...
MagicAndre1981 Posted April 21, 2011 Share Posted April 21, 2011 I use the original MS ISO from Technet. Strange that you don't have it. Link to comment Share on other sites More sharing options...
bs1 Posted April 21, 2011 Share Posted April 21, 2011 I have 5 Computers which i have integrated sp1 (Ultimate 64 Bit) using WAIK. on these Computers i have not got this error. i recently built another Computer und also bought an original Microsoft Ulimate System Builder DVD with SP1 already integrated, on this Computer i had the error, so using WAIK i integrated sp1 from one of my old DVDs and now the error ist not present. Link to comment Share on other sites More sharing options...
kavorka Posted April 23, 2011 Author Share Posted April 23, 2011 Thanks bs1. So it looks like the error is created by Microsoft's official integration. Link to comment Share on other sites More sharing options...
ricktendo Posted April 23, 2011 Share Posted April 23, 2011 Its a longshot but try ResetWMI by Kai LiuInfo: http://www.ryanvm.net/forum/viewtopic.php?t=5285Download: http://code.kliu.org/misc/resetwmi/Launch resetwmi.exe (leave it where you launched it from), reboot and next boot it will do its thing Link to comment Share on other sites More sharing options...
MagicAndre1981 Posted April 23, 2011 Share Posted April 23, 2011 or run the Script from the KB article. After I did this the messages no longer occur. Link to comment Share on other sites More sharing options...
kavorka Posted April 26, 2011 Author Share Posted April 26, 2011 The KB article's solution merely stops the reporting of the error, it does not actually fix the error. But I have to admit not seeing it does help me forget about it. Link to comment Share on other sites More sharing options...
ricktendo Posted April 26, 2011 Share Posted April 26, 2011 (edited) or run the Script from the KB article. After I did this the messages no longer occur.Because ResetWMI is more likely to fix the problem as opposed to the script which does notI have asked the author to see about adding a fix for this error into his tool (if it does not already fix it, I cant test to see because I already ran the stupid script) Edited April 26, 2011 by ricktendo64 Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now