none
How do I change the setupapi.dev.log logging level in Windows 8? RRS feed

Answers

All replies

  • Look at http://msdn.microsoft.com/en-us/library/windows/hardware/ff550887(v=vs.85).aspx or get OSRSYSTOOLS or SetDbgPrintFiltering from http://www.osronline.com/section.cfm?section=27  

    Don Burn Windows Filesystem and Driver Consulting Website: http://www.windrvr.com

    Monday, December 8, 2014 4:32 PM
  • OsrSysTools reports that the most verbose logging is configured both for the general logging and for the device logging level.

    But I still don't get the verbosity I'm expecting in setupapi.dev.log: for instance, when I connect a USB thumb drive, nothing gets written to that file...

    Monday, December 8, 2014 4:42 PM
  • Why would something be written when a USB drive is inserted?  This is for you debug prints being enabled.  Note: you do need to reboot to even see you printouts.  For things like system components you are out of luck, Microsoft converted all the debug print type stuff to WPP tracing statements with Win7 and then did not distribute the files to capture most of that.


    Don Burn Windows Filesystem and Driver Consulting Website: http://www.windrvr.com

    Monday, December 8, 2014 4:46 PM
  • What we're trying to troubleshoot is a potential HW glitch where the device would transiently disappear from the bus and then reappear. So we need something that causes device removals and insertions to be logged.

    We're going to look at http://msdn.microsoft.com/en-us/library/windows/hardware/jj151573%28v=vs.85%29.aspx and friends.

    Sounds sensible?

    Monday, December 8, 2014 4:56 PM
  • I haven't used them but that is the recommended way of doing things.  I believe you can access much of that functionality through Traceview and USB Disk provider also.


    Don Burn Windows Filesystem and Driver Consulting Website: http://www.windrvr.com

    Monday, December 8, 2014 5:02 PM
  • setupapi.dev.log will not show device surprise removals and insertions after install (which is logged). As don said, you need to capture a USB ETW trace log which will tell you about the on the USB wire glitch

    d -- This posting is provided "AS IS" with no warranties, and confers no rights.

    Monday, December 8, 2014 6:32 PM