<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.technet.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Basic WMI Testing</title><link>http://blogs.technet.com/b/askperf/archive/2007/06/22/basic-wmi-testing.aspx</link><description>OK - following on from our recent WMI Architecture post, let's start digging into some Basic WMI Troubleshooting. There's a lot of material to cover, so this is going to be a multi-part series! It's important to note that these are general concepts and</description><dc:language>en-US</dc:language><generator>Telligent Evolution Platform Developer Build (Build: 5.6.50428.7875)</generator><item><title>re: Basic WMI Testing</title><link>http://blogs.technet.com/b/askperf/archive/2007/06/22/basic-wmi-testing.aspx#3478535</link><pubDate>Thu, 02 Feb 2012 14:38:54 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3478535</guid><dc:creator>Blake Morrison - MSFT</dc:creator><description>&lt;p&gt;WMIDiag 2.1 is now available!&lt;/p&gt;
&lt;p&gt;&lt;a rel="nofollow" target="_new" href="http://www.microsoft.com/download/en/details.aspx?id=7684"&gt;www.microsoft.com/.../details.aspx&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Supported Operating Systems: Windows 7, Windows Server 2003, Windows Server 2008, Windows Server 2008 R2, Windows Vista, Windows XP&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=3478535" width="1" height="1"&gt;</description></item><item><title>re: Basic WMI Testing</title><link>http://blogs.technet.com/b/askperf/archive/2007/06/22/basic-wmi-testing.aspx#3372022</link><pubDate>Tue, 30 Nov 2010 13:56:06 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3372022</guid><dc:creator>Greg DeCecco</dc:creator><description>&lt;p&gt;I&amp;#39;m running Vista with a WMI version of 6001.18226. &amp;nbsp;The button that enables us to change credentials when connection to WMI on another computer does not exist.&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=3372022" width="1" height="1"&gt;</description></item><item><title>re: Basic WMI Testing</title><link>http://blogs.technet.com/b/askperf/archive/2007/06/22/basic-wmi-testing.aspx#3317410</link><pubDate>Sun, 07 Mar 2010 20:28:43 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3317410</guid><dc:creator>Diane Lind</dc:creator><description>&lt;p&gt;Yes. I too encountered Hi PerfCooker_v1. Just before the bios on my HP dv6000 series laptop game computer was fried. &lt;/p&gt;
&lt;p&gt;There were many freeze ups. There was one final crash.&lt;/p&gt;
&lt;p&gt;I found HiPerfCooker_v1 on a computer management log.&lt;/p&gt;
&lt;p&gt;The HP dv6000 series laptops have a well known graphics processor weakness that was exploited to destroy the computer. Read motherboard here. &amp;nbsp;The DRM or spyware forces the wireless, probably with its own drivers, to open either to fry the computer or transmit data. The hard drive winds up trashed, it can be check discked but not healed, like a worm, maybe it is, it fills up again with fragments. The wireless unit will become extremely hot. That heat transfers to whatever is nearby. It corrupts memory. Power cords were also defective, but that might be because of feedback from the wireless. Just FYI. &lt;/p&gt;
&lt;p&gt;I tried looking at the hard disk later, couldn't even get into it, didn't want to at that point, and I doubt that I'll even try to use the ram. Once your physical equipment has been corrupted with strange electrical or radio charges, who knows what it's goin to do, it will retain negative and positive polarities that it shouldn't be keeping. It's a subtle thing. Deep fried notebook isn't. Thank you. &lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=3317410" width="1" height="1"&gt;</description></item><item><title>re: Basic WMI Testing</title><link>http://blogs.technet.com/b/askperf/archive/2007/06/22/basic-wmi-testing.aspx#2505895</link><pubDate>Sun, 18 Nov 2007 23:18:01 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:2505895</guid><dc:creator>Alfavazquez</dc:creator><description>&lt;p&gt;I am having problems with overflow of SeaMonkey and the error is always associated with an installation of HiPerfCooker_V1. Was not this only a statistical counter? I appreciate your help.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=2505895" width="1" height="1"&gt;</description></item><item><title>re: Basic WMI Testing</title><link>http://blogs.technet.com/b/askperf/archive/2007/06/22/basic-wmi-testing.aspx#2360772</link><pubDate>Thu, 08 Nov 2007 00:12:23 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:2360772</guid><dc:creator>CC Hameed</dc:creator><description>&lt;p&gt;Joe - &lt;/p&gt;
&lt;p&gt;You would be best served by opening a support incident with Microsoft Product Support.&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=2360772" width="1" height="1"&gt;</description></item><item><title>re: Basic WMI Testing</title><link>http://blogs.technet.com/b/askperf/archive/2007/06/22/basic-wmi-testing.aspx#2360668</link><pubDate>Wed, 07 Nov 2007 23:57:15 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:2360668</guid><dc:creator>joecastaldi</dc:creator><description>&lt;p&gt;having high processor usage associated with wmiprvse.exe. &amp;nbsp;After running &amp;quot;wmidiag checkconsistency&amp;quot; I have identified HiPerfCooker_v1 event in the log, along with &amp;quot;incorrect shutdown events&amp;quot;. &amp;nbsp;Symantec virus signatures have been checked and wmiprvse.exe passes the scan. &amp;nbsp;Running VS debugger on the process (from task manager) in the monitor view shows huge number of dlls continuously getting loaded. &amp;nbsp;Please help with solution.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=2360668" width="1" height="1"&gt;</description></item><item><title>WMI Troubleshooting: Permissions</title><link>http://blogs.technet.com/b/askperf/archive/2007/06/22/basic-wmi-testing.aspx#1751687</link><pubDate>Tue, 14 Aug 2007 14:14:39 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:1751687</guid><dc:creator>Ask the Performance Team</dc:creator><description>&lt;p&gt;Back in June, we published our post on Basic WMI Testing . Today we're going to go over some common issues&lt;/p&gt;
&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=1751687" width="1" height="1"&gt;</description></item><item><title>
		   Basic WMI Testing &amp;raquo; D&amp;#8217; Technology Weblog: Technology News &amp;amp; Reviews	</title><link>http://blogs.technet.com/b/askperf/archive/2007/06/22/basic-wmi-testing.aspx#1322556</link><pubDate>Fri, 22 Jun 2007 13:57:01 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:1322556</guid><dc:creator>
		   Basic WMI Testing » D’ Technology Weblog: Technology News &amp; Reviews	</dc:creator><description>&lt;p&gt;PingBack from &lt;a rel="nofollow" target="_new" href="http://www.ditii.com/blog/2007/06/22/basic-wmi-testing/"&gt;http://www.ditii.com/blog/2007/06/22/basic-wmi-testing/&lt;/a&gt;&lt;/p&gt;
&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=1322556" width="1" height="1"&gt;</description></item></channel></rss>