Click to See Complete Forum and Search --> : XP starts to login user then logs out


rudebwoy
September 30th, 2004, 07:14 PM
After updating to service pack 2 I could only logon and the user name I do the update under If I try to user any other user name at the welcome screen it will just say login on user and then say saving user setting and go back to the welcome screen

Bald Monkey
October 1st, 2004, 08:35 AM
After updating to service pack 2 I could only logon and the user name I do the update under If I try to user any other user name at the welcome screen it will just say login on user and then say saving user setting and go back to the welcome screen

This sounds as though the version of Windows is unregistered, or possibly the license number is one on Microsofts' list of banned COA's?

rudebwoy
October 1st, 2004, 08:47 AM
This sounds as though the version of Windows is unregistered, or possibly the license number is one on Microsofts' list of banned COA's?

It's a registered version it was check by ms

freddy
October 1st, 2004, 09:16 AM
This sounds as though the version of Windows is unregistered, or possibly the license number is one on Microsofts' list of banned COA's?

if you have a "bent" copy of xp pro , and it is on there "banned" list ,,,it will not load sp2 ,,,

you will not get sp2 loaded on a bent machine ,,


i know ,,,,been there ,,,,got the t shirt.

MBatson
October 1st, 2004, 12:10 PM
My suggestion would be to create a Windows XP CD with service pack 2 slipstreamed into the install CD and then do a repair install with the new SP2 CD. I had done that on a few computers at our county building when they upgraded all the systems to SP2. A few would go to log in and then they would immediately log back out. After the repair install the system would log in and work fine.

geoscomp
October 1st, 2004, 12:57 PM
I've had three machines come in with the same problem except the normal user login wasnt available either..a repair install and reinstall of sp2 solved the problem

Radical Dreamer
October 3rd, 2004, 11:27 AM
I had this same issue when image casting to some labs this week, it was odd, nothing I did would fix it, I just had to send the image again. Happened on 3-4 out of 24 machines