I have had this happen twice on 2 different machines. Both are Win XP. After uninstalling the client, and restarting the machine we are unable to get logged into the machine, it logs off as soon as you log in. This occurs in normal mode and safe mode. The only fix that I have found is to do a repair install of windows. Has anyone else had this happen???
[align=left] [/align]
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
Yes, I have seen this few times. I dont know if its a known bug with Kace, but I thought it might just have been our environment.

What happens is, it looks like Kace has its own version of userinit.exe, called kuserinit.exe. Userinit is what loads your profile when you login, so without this the PC doesn't know what to do and logs you back out. Kace installer repaths the registry entry to point to its version of userinit, rather then the ms one. I believe that when you remove the Kbox agant from the computer this registry entry doesn't get fixed. So what you can do is remote registry the computer, go to hklm\software\Miscrosoft\Windows NT\CurrentVersion\Winlogon and change the entry to userinit, insted of Kuserinit.
Answered 08/26/2010 by: dtuttle
Purple Belt

Please log in to comment
0
Welcome to the forum.

I have indeed seen that problem. It happens when the userinit registry value is incorrect.

It has been a while since I last applied the fix, but if memory (and google) serve:

From another computer on the same network:
Run Regedit.exe (with a user with admin rights on the other PC)
Point your cursor to HKEY_LOCAL_MACHINE
Select File > Connect Remote Registry
Type broken computer name
Navigate to the following location in registry of broken computer

HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Winlogon

Change Userinit to equal C:\WINDOWS\system32\userinit.exe,
Exit from Registry
Restart broken computer

You should be able to log on to computer

Casey
Answered 08/26/2010 by: cmccracken
Orange Senior Belt

Please log in to comment
0
Which version of the agent? How did you uninstall the agent? Our uninstaller should restore that registry setting back to the original after it's done.
Answered 08/26/2010 by: jkatkace
Purple Belt

Please log in to comment
0
The agent version we are using is 5.1.31821, And I went to add remove programs, and when I clicked on the kbox client the installer window popped up and I just clicked uninstall.
Answered 08/26/2010 by: TiffinUniversityITS
Senior Yellow Belt

Please log in to comment
0
I just ran into an issue during an image deployment. When I logged in to the computer after the deploy, 50+ "My Documents" windows open up and threw up all kinds of errors. I actually used the same method you described to fix that issue. Not sure if it was the correct way to do it but it worked. I believe it was showing it as "KUsrinit.exe". I changed it to "userinit.exe" and everything went back to normal.

ORIGINAL: cmccracken

Welcome to the forum.

I have indeed seen that problem. It happens when the userinit registry value is incorrect.

It has been a while since I last applied the fix, but if memory (and google) serve:

From another computer on the same network:
Run Regedit.exe (with a user with admin rights on the other PC)
Point your cursor to HKEY_LOCAL_MACHINE
Select File > Connect Remote Registry
Type broken computer name
Navigate to the following location in registry of broken computer

HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Winlogon

Change Userinit to equal C:\WINDOWS\system32\userinit.exe,
Exit from Registry
Restart broken computer

You should be able to log on to computer

Casey
Answered 08/26/2010 by: ustacp
Second Degree Blue Belt

Please log in to comment
Answer this question or Comment on this question for clarity