As the image shows below, randomly, but very often during the day when Kace Agent does something which im not sure what, it causes windows to throw the error "User Environment - Windows cannot load the user's profile but has logged you on with the default profile for the system. DETAIL - The configuartion registry database is corrupt."

All affected machines (~10 of 200) are completely up to date patched Windows XP SP3 machines. They vary in model I think but am not completely sure. They do complete the inventories and report as connected allowing scripts to run if we wanted. This happens with Kace agent 5.5XXXX, 5.4XXXX and 5.3XXXX. Windows logging only records userenv logs that are unhelpful. The K1000 server is on the latest version "5.5.90545". All are logged into windows as an local admin group user. I have checked the permissions of the document and settings folders and tried setting full access to everyone. Deleting the user profile and recreating it works only for about a day. Some machines it reoccurs every minute if you acknowledge the error, some only a couple times a day. All enough to be a serious issue impacting productivity.

Any ideas how to fix this other than to keep the agents uninstalled?

1 Comment   [ + ] Show Comment


  • I have considered running batch files to kill the notification non stop, as I have exhausted all other options i can think of. The task manager kace processes are only shown just after the error occurs
Please log in to comment



What makes you think they KACE agent is doing this?  Does it stop if you uninstall the agent?

If so, submit a support ticket so that KACE support can take a look.

Answered 10/14/2013 by: jknox
Red Belt

  • It does stop if the agent is removed and also the message disappears if you kill all kace agent related processes. I will log a ticket. Thanks
    • As a workaround, you can probably change the key HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\Userinit key from C:\Windows\system32\KUsrInit.exe to C:\Windows\system32\userinit.exe,

      That should allow log in in the meantime.
Please log in to comment
Answer this question or Comment on this question for clarity