asked on

mystery log files

What writes the following log files:- WBEMCORE.LOG; WinMgmt.log; Setupapi.log. They seem to have error messages & are getting bigger.
examples of entries are:

WBEMCORE.LOG
Two providers supplied conflicting instances for key Name="C:\\WINDOWS\\SYSTEM\\ir32_32.dll"
.....msyuv.dll
Core physically unloaded!

WinMgmt.log
core is being shut down by WinMgmt.exe, it returned 0x0

Setupapi.log
Munged cmdline: C:\WINDOWS\SYSTEM\CMDNINST.EXE C29AE650 00000001 00000002
EXE name: C:\WINDOWS\SYSTEM\CMDNINST.EXE
The file (c:\windows\inf\machine.inf) is not digitally signed, ignoring driver date.
Selected driver installs from section ACPI_DRV in c:\windows\inf\machine.inf.
Changed class GUID of device to {4D36E97D-E325-11CE-BFC1-08002BE10318}.
Set selected driver.
Device install function: DIF_INSTALLINTERFACES.
Installing section ACPI_DRV.Interfaces from c:\windows\inf\machine.inf.
The driver signing class list (C:\WINDOWS\INF\certclas.inf) was missing or invalid. Error 2: The system cannot find the file specified.
Assuming all device classes are subject to driver signing policy.
An unsigned or incorrectly signed driver (c:\windows\inf\machine.inf) was installed for Advanced Configuration and Power Interface (ACPI) BIOS. Error 0x800b0001: Unknown trust provider.

Am I heading for trouble? Like most I have the odd unexplained hang or hiccup.

ASKER CERTIFIED SOLUTION

CrazyOne

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

silvers

ASKER

thanks CrazyOne, that takes care of the setupapi.log.
Anybody any info on the others?

CrazyOne

To tell you the truth I haven't found any useful info on the other two logs.

>>>WinMgmt.log
core is being shut down by WinMgmt.exe, it returned 0x0

If you are not experiencing any prolems than I wouldn't be to concerned about this message. I think it has to do with what is called debugging and this info is mostly useful to developers.