You are currently offline, waiting for your internet to reconnect

Capturing debug and diagnostic logging from WZC for wireless NICs

Support for Windows XP has ended

Microsoft ended support for Windows XP on April 8, 2014. This change has affected your software updates and security options. Learn what this means for you and how to stay protected.

Support for Windows Server 2003 ended on July 14, 2015

Microsoft ended support for Windows Server 2003 on July 14, 2015. This change has affected your software updates and security options. Learn what this means for you and how to stay protected.

This article was previously published under Q328601
Windows Zero Configuration (WZC) is the Windows service that automatically configures 802.11 wireless network devices. Adapter manufacturers and NDIS miniport developers for those adapters may find additional diagnostic information from the WZC service helpful.

This article describes how to capture a very verbose log (one that is set to maximum output) from WZC.
To use the additional tracing capabilities that are built into WZC, install the checked build of Wzcsvc.dll on the test system. The trace will be written out to a log file on disk. Therefore, you do not have to hook up a Kernel debugger (for example, WinDbg) or install the whole checked build of the operating system.

If you are not using a complete checked build of the OS, you must obtain a copy of the binary Wzcsvc.dll from a system that is using a complete checked build of the OS.

Note To obtain the checked build on CD, you can subscribe to the Microsoft Developer Network (MSDN). For more information about subscriptions, visit the following Web site: To capture a log from WZC that is less than maximum output, follow these steps:
  1. Before you load the binary on the test system, you must disable System File Protection (SFP).

    To disable SFP, press F8 while the system is starting, and then select Safe Mode when you receive a prompt. Replace the file, and then restart the system.
  2. With the checked binary of Wzcsvc.dll in place (either because you are running a complete checked OS or because you replaced it), set the following registry entry to 1:
    HKEY_LOCAL_MACHINE\Software\Microsoft\Tracing\WZCTrace\EnableFileTracing (REG_DWORD)
  3. If any portion of the hive location does not exist, create the hives that you want (for example, Tracing and WZCTrace may not exist).
  4. To effect the changes to tracing, either restart the system, or stop and start the service. The service creates the log file WZCTrace in the %windir%\Tracing folder.
  5. Disable WZC tracing by setting EnableFileTracing to zero.
  6. By default, tracing output is set to maximum output. To tailor how much information is produced, you can create the registry entry FileTracingMask (REG_DWORD) using one or more of the following values (and OR them together as you need).
    0x80000000: Logs failed ASSERTs0x01000000: Logs 'State Machine' events0x00800000: Logs synchronization events0x00400000: Logs storage events0x00200000: Logs notifications0x00100000: Logs hash related activities0x00080000: Logs error conditions0x00040000: Logs memory allocations and releases0x00020000: Logs code path within WZCSVC0x00010000: Logs generic events0xFFFF0000: (default) logs all events					
    Note These flags may change.
For more information, visit the following MSDN Web sites:

Article ID: 328601 - Last Review: 07/28/2005 23:25:04 - Revision: 7.3

Microsoft Windows XP Driver Development Kit, Microsoft Windows XP Home Edition, Microsoft Windows XP Professional, Microsoft Windows Server 2003 Driver Development Kit (DDK), Microsoft Windows Server 2003, Standard Edition (32-bit x86), Microsoft Windows Server 2003, Enterprise Edition (32-bit x86), Microsoft Windows Server 2003, Datacenter Edition (32-bit x86)

  • kbinfo kbndis kbnetwork KB328601