• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 628
  • Last Modified:

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:

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

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

Munged cmdline: C:\WINDOWS\SYSTEM\CMDNINST.EXE C29AE650 00000001 00000002
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.
  • 2
1 Solution
MS KB article about the Setupapi.log


Incorrectly or Improperly Signed" Files Listed in the Setupapi.log File (Q268606)

The information in this article applies to:

Microsoft Windows Millennium Edition


When you open the Setupapi.log file after installing Windows Millennium Edition you notice that various entries show "Incorrectly or improperly signed."

The Setupapi.log file is created at the end of Setup and it is not possible to verify that the files are signed during Setup because the cryptography files are not yet installed or initialized.

Microsoft has confirmed this to be a problem in the Microsoft products that are listed at the beginning of this article.

The entry "Incorrectly or improperly signed" in the Setupapi.log file does not impact the system performance in any way.

Published Aug 4 2000 3:54PM  Issue Type kbprb  
Last Modifed Jan 30 2001 12:00PM  Additional Query Words  
Keywords kbWinME  

COPYRIGHT NOTICE. Copyright 2002 Microsoft Corporation, One Microsoft Way, Redmond, Washington 98052-6399 U.S.A. All rights reserved.

The Crazy One
silversAuthor Commented:
thanks CrazyOne, that takes care of the setupapi.log.
Anybody any info on the others?
To tell you the truth I haven't found any useful info on the other two logs.

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.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now