How do I adjust the logging level on Windows?

When you encounter an issue relating to the Windows workstation, the troubleshooting process often requires reading through the log files generated by the client. By default the log files may not contain all of the information needed to get a clear understanding of the issue. It is possible to adjust the amount of log messages captured by writing a setting to the Windows registry.
To edit the Windows registry, Click the search button on the taskbar and type "registry" to find Registry Editor. Administrator privileges are usually required to edit the registry. Right click the Registry Editor and select 'Run as an administrator'.

You will then have to navigate to the correct entry through the tree on the left hand side of the screen. The path to the entry is: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Authentication\Credential Providers\{C822931E-86C5-4482-85C1-049523A13A09}


If an entry for "Log Level" isn't available, create one by right clicking on the "C822931E-86C5-4482-85C1-049523A13A09" registry entry on the left -> New -> String Value and name the entry "Log Level". 



After the entry has been created, right click on it, and choose Modify. You will be asked to enter a value here that corresponds to the debug level the Windows Client will use.



The valid values are listed below in order of least to most log messages.

0=NONE (no logging)
1=FATAL (only Fatal Errors)
2=ERROR (only Fatal and Error)
3=WARN (only Fatal, Error and Warning)
4=INFO (only Fatal, Error, Warning and Info)
5=DEBUG (only Fatal, Error, Warning, Info, Debug)
6=TRACE (only Fatal, Error, Warning, Info, Debug, Trace)


The image below is an example of a log level set to 5.



After you make registry changes, a restart of the service is required for the updates to take effect. You can find search for "services" from the taskbar. If you have Admin privileges on the machine you can open Services.


Find the HYPR Employee Unlock Service, right click, and select restart. A reboot will have the same effect. Then reopen the Employee Access client.  



Was this article helpful?
0 out of 0 found this helpful