UserInit Registry Setting
Some of our computers have their UserInit registry setting as the following:
UserInit=c:\windows\system32\userinit.exe,c:\windows\system32\kusrinit.exe,
Computers with this setting open the "Libraries" window on logon, which is problematic (well, not problematic, but annoying). Comparing with another computer I see that its registry has this instead:
UserInit=c:\windows\system32\kusrinit.exe,
I'm assuming that the correct value should only include the kusrinit.exe, but wanted to see if anyone else has seen this behavior. Also, one of our technicians has been removing the kusrinit.exe and leaving just the userinit.exe. Does anyone know what complications this will cause?
Thanks.
UserInit=c:\windows\system32\userinit.exe,c:\windows\system32\kusrinit.exe,
Computers with this setting open the "Libraries" window on logon, which is problematic (well, not problematic, but annoying). Comparing with another computer I see that its registry has this instead:
UserInit=c:\windows\system32\kusrinit.exe,
I'm assuming that the correct value should only include the kusrinit.exe, but wanted to see if anyone else has seen this behavior. Also, one of our technicians has been removing the kusrinit.exe and leaving just the userinit.exe. Does anyone know what complications this will cause?
Thanks.
0 Comments
[ + ] Show comments
Answers (7)
Please log in to answer
Posted by:
diverdaveman1
13 years ago
Just currious - but when your are cloning/imaging a client, does your image(s) have KACE installed?
Dave
Dave
Posted by:
lefttunknown
13 years ago
I had this same issue pop up after something weird happened to a machine that I was cloning. Now all machines that get that image popup that libraries window at logon. I have this for both windows 7 and windows xp. I noticed that UserInit=c:\windows\system32\userinit.exe,c:\windows\system32\kusrinit.exe existed on both machines after being imaged so I created a registry file that just includes c:\windows\system32\userinit.exe for the UserInit reg key. I have to run it manually after cloning on each machine. Kind of a pain.
But it fixes my issue and I haven't noticed any bad side effects. Been using it for a couple weeks now.
But it fixes my issue and I haven't noticed any bad side effects. Been using it for a couple weeks now.
Posted by:
GillySpy
13 years ago
The agent would like it to be:
kusrinit will invoke the agent's handler which will allow certain logon tasks (kbots, etc) to do their thing at the right time.
kusrinit will then call userinit so it can carry out what it would normally do.
It is possible that userinit.exe is not the OEM microsoft userinit.exe. I have seen other applications try to enforce userinit.exe in that key so that may be what is happening.
There was a time when we would as well, but we don't do that anymore to avoid any tennis matches. My guess is that something came along and insisted that userinit.exe be put back in there. Although, as you can see from the architecture above it's not needed because we will call it as part of the "chain".
UserInit=c:\windows\system32\kusrinit.exe, kusrinit will invoke the agent's handler which will allow certain logon tasks (kbots, etc) to do their thing at the right time.
kusrinit will then call userinit so it can carry out what it would normally do.
It is possible that userinit.exe is not the OEM microsoft userinit.exe. I have seen other applications try to enforce userinit.exe in that key so that may be what is happening.
There was a time when we would as well, but we don't do that anymore to avoid any tennis matches. My guess is that something came along and insisted that userinit.exe be put back in there. Although, as you can see from the architecture above it's not needed because we will call it as part of the "chain".
Posted by:
rmeyer
13 years ago
I have that problem in Turkey only for some reason (and we have sites in around 30 countries)
They look like this: UserInit=c:\WinXP\system32\userinit.exe,c:\WinXP\system32\kusrinit.exe
Everywhere else it's: C:\WINXP\system32\KUsrInit.exe, only
This causes it to do 30 * login script and 30* my documents at login, if I change it to what it should be and reboot then it works untill next checkin then it set it back.
The solution was to upgrade to the newest agent, but we are still holding back on the new version due to the current issues
They look like this: UserInit=c:\WinXP\system32\userinit.exe,c:\WinXP\system32\kusrinit.exe
Everywhere else it's: C:\WINXP\system32\KUsrInit.exe, only
This causes it to do 30 * login script and 30* my documents at login, if I change it to what it should be and reboot then it works untill next checkin then it set it back.
The solution was to upgrade to the newest agent, but we are still holding back on the new version due to the current issues
Posted by:
cblake
13 years ago
This has been around for a while: http://www.kace.com/support/kb/index.php?action=artikel&cat=2&id=662&artlang=en
Started irking me about 4 years ago now. A script from your K1 or postinstall task on your image could easily fix it.
Started irking me about 4 years ago now. A script from your K1 or postinstall task on your image could easily fix it.
Posted by:
rmeyer
13 years ago
I tried to fix it by changing it but it keeps changing back when ever a script or the agent check in, I had a ticket open about it and it ended with the ticket was forwarded to the programmers and the "current fix" was to update to the newest version of the agent.
And with all the errors on that versions I choose not to upgrade and wait with the Turkish sites untill a fix arrives for the newest version
And with all the errors on that versions I choose not to upgrade and wait with the Turkish sites untill a fix arrives for the newest version
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.
