The logon script is running twice and there may be two diagnostic trace files created at the same time in the upload repository if that feature is enabled in Global Options. In addition, there might be an entry in the trace file indicating that "A logon event did not complete".
The Userinit registry value, has been modified from the default in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon, and the script is being called twice as a result. The default Microsoft data in the Userinit value should be: C:\Windows\system32\userinit.exe,
This issue can be caused by any software package that relies on, and subsequently modifies, the default data in the Userinit value in order for a particular set of features to run as desired.
This issue has been detected when the KACE agent is installed in certain circumstances and where it appends the KUserInit.exe data to the value instead of overwriting the data with KUserInit.exe (which also calls the default Microsoft UserInit). So, if the data in the value contains both of the entries below, one would expect the logon script to be launched twice as instructed.
If the additional UserInit data is associated to the KACE Agent, the correct value (to avoid the agent malfunction) is:
If the additional UserInit data is different, and is not attributed to the KACE Agent, then it can be changed to the original value, but the software that changed the value might stop functioning.
This profile can be used to fix the issue when the KACE Agent is involved. Import it into the Desktop Authority server. Be sure to set the appropriate validation logic so that it is targeted properly. It is also recommended to test the changes on a small sample of target machines before pushing the changes out to the entire client base. Please backup registry before any change is done.
Quest does not provide support for problems that arise from improper modification of the registry. The Windows registry contains information critical to your computer and applications. Make sure you back up the registry before modifying it. For more information on the Windows Registry Editor and how to back up and restore it, refer to Microsoft Article ID 256986 “Description of the Microsoft Windows registry” at Microsoft Support.