I did not post anything about the Windows Management Instrumentation
service. Leave it set to Automatic in services.msc.
I suggested disabling WMI logging. I have it disabled. My wmiprov.log is
0KB.
The following has nothing to do with the Windows Management Instrumentation
service.
All it does is disable WMI logging so that nothing is added to the
wmiprov.log.
Administrative Tools | Computer Management | Click on [+] Services and
Applications | Right click on WMI Control | Click on properties | Click on
Logging. Change the logging level to Disabled.
Apparently you have WMI logging set to verbose. That means that it shows
not only errors, but SUCCESS as well.
[[Verbose logging can negatively impact system performance, so select
Verbose only when you need more extensive information about the events
leading to errors. ]]
To turn WMI error logging on or off
http://www.microsoft.com/resources/d...ng_on_off.mspx
You do what ever you want.
--
Hope this helps. Let us know.
Wes
MS-MVP Windows Shell/User
In news:loo5byk23neu$.1xdiea6nkwjka.dlg@40tude.net,
Tom Quan <tquan@telleride.com> hunted and pecked:
>>> Is it normal for wbem logs to constantly report repeated errors?
>> Are you saying these errors in the wmi log files are meaningless?
>
> I looked up what happens if I kill this service and I'm even more
> confused.
>
> While the filemon.exe log does not show the failure which exists inside
> the wmiprov.log and wbemess.log files, filemon does implicate the process
> which is constantly being called as "wmiprvse.exe" (whatever that is).
>
> Looking this up, I find wmiprvse.exe is a Windowx XP SP2 Windows
> Management Instrumentation (WMI) process which is not supposed to be
> killed according to http://www.auditmypc.com/process/wmiprvse.asp
>
> Process Library & Answers that Work imply this service essential to XP:
> http://www.processlibrary.com/directory/files/wmiprvse
> http://www.answersthatwork.com/Taskl...tasklist_w.htm
>
> It may be useful to note my anti-virus software has been running and is up
> to date even though this intermittent daily Windows XP lockup has been
> occurring for weeks.
>
> Are you sure that killing the wmiprvse service will solve the problem
> intimated by the constant errors in the WBEM log files?