6 Replies to “KB958909”

  1. RE: setupapi.app and .dev files. is there a simple way to also cut them off, and archive them every 5Meg, and keep the data they recorded?
    that way, wehave it all perfromance and functionality. Thank you. mine are 5 and 8 megs,
    and that makes boot at bit slow somedays.

  2. uding a dfault means, when thevendor wants to change .. u change! if u like a partuclar option.. code it..BUT be aware of vendor chnages if they occur, as you wont be part of that change. for non-experts code 0000 not 0020(log errors and warnings).. mine was set as 0000, so chnaging to 0020 just “seals the deal”!

    http://msdn.microsoft.com/en-us/library/dd406727.aspx lists all the bits..

    0x00000000 Use default settings (currently 0x20).
    0x00000001 Off (no Setup logging).
    0x00000010 Log errors.
    0x00000020 Log errors and warnings.
    0x00000030 Log errors, warnings and other information.
    0x00000040 Log errors, warnings and other information in verbose mode.
    0x00000050 Log errors, warnings and other information in verbose mode, plus time-stamped entries.
    0x00000060 Log errors, warnings and other information in verbose mode, plus time entries. Additionally, all entries are time-stamped.
    0x00000070 Log errors, warnings and other information in verbose mode, plus time messages. All entries are time-stamped. Additional messages that can slow down the system, such as cache hits, are included.
    0x000000FF Specifies the most verbose logging available.

    Device Logging Levels Meaning
    0x00000000 Use default settings (currently 0x3000).
    0x00000100 Off (no Setup logging).
    0x00001000 Log errors.
    0x00002000 Log errors and warnings.
    0x00003000 Log errors, warnings and other information.
    0x00004000 Log errors, warnings and other information in verbose mode.
    0x00005000 Log errors, warnings and other information in verbose mode, plus time-stamped entries.
    0x00006000 Log errors, warnings and other information in verbose mode, plus time entries. Additionally, all entries are time-stamped.
    0x00007000 Log errors, warnings and other information in verbose mode, plus time messages. All entries are time-stamped. Additional messages that can slow down the system, such as cache hits, are included.
    0x0000FF00 Specifies the most verbose logging available.

    Special Flags Meaning
    0x08000000 (Windows XP and later) Add a time stamp to all log entries.
    0x20000000 (Windows XP and later) Don’t flush logging information to disk after each entry is written. (Logging is faster, but information could be lost if the system crashes.)
    0x40000000 Write log entries chronologically instead of grouping entries.
    0x80000000 Send the output to the debugger as well as to the log file.

    For example, SetupAPI interprets some sample LoggingFlags values as follows:

    0x00000000 means default logging.
    0x0000FFFF means verbose logging.
    0x8000FF00 means log verbose device installation information to both the log file and the debugger.
    0x0000FFFF means verbose logging.
    0x8000FF00 means log verbose device installation information to both the log file and the debugger.
    0x8000FF00 means log verbose device installation information to both the log file and the debugger

  3. I aded this to MSDN website… under how to name the folder for the APP and DEV log files.
    defualt being “inf”..
    http://msdn.microsoft.com/en-us/library/aa477114.aspx

    If the existing files are large and we wish to maintain them as archives, I’d like to see this:
    A) microsoft intrrduce a limit key (0- no chnage from today, 5- to indicate in Megabytes, when to archive existing file as DOT.YYmmdd appended and start a new file for use. This in addition to verbose/terse bits warn/err/etc now in place.
    Having these self-healing activities will make for quicker boot-times. Meanwhile, I guess we can all do this… allocate a new file for bot DEV and APP in a unique diretcory called BOOTLOG1 and 2, and adjust the name used to flip-flop between the 2 folders, and do user-maintaed archiving.

    ————————————————-
    By default, the SetupAPI text logs are located in the %Windir%\Inf directory. For information about how to change the directory where the text logs are located, see below: Setting the Directory Path of the Text Logs.

    By default, the SetupAPI text logs are located in the system Windows directory. The location of the SetupAPI text logs can be changed by setting the following REG_SZ registry value:

    HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Setup\LogPath

    The LogPath registry value must be a fully-qualified directory path. The path must exist, and the path cannot include a file name.

    If the LogPath registry value is not present, the path does not exist, or the path includes a file name, SetupAPI locates the text logs in the %Windir%/Inf directory.

    My registry has no such key , YET!

  4. do u guys know anything about the CBS.LOG file
    mine is 32Meg..

    Windows Resource Protection found integrity violations. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log

    my event viwer has many violationsfor code-integrity, I guess each creates a LOG entry.
    i’ve got a LOT!! (it also has, if u view with RUNAS, a bunch of UPDATE histories).

    also found another biggee!! WINDOWSUPDATE .LOG file…(2 meg)

  5. Flag settings: actually x’00002020′ seems better, that would give u both log and dev options of err/warn ONLY.any comments?

Leave a Reply