G
Guest
This morning my computer spontaneously started giving a login screen to me
when I try to start up, even though I disabled it. When I try to login, it
won't let me, and it is giving me the message in the subject title. I never
had a problem like this before, and I am using XP Home edition (service pack
2). The startup process is taking much longer than it did before, and now it
ends up with that message when I try to login. I was on a home workgroup, but
this didn't give me a problem before today. I tried switching to another
workgroup name, but it hasn't changed anything. I am using Safe Mode with
networking right now to post this message using the same computer, using the
Administrator account. I tried making a new username, but it won't let that
one login either. I tried system restore, but that didn't change anything.
I noticed a KB article saying that Win 2000 had similar errors, with 128-bit
encryption, but I haven't found a solution that pertained directly to XP. I'm
reluctant to apply the Win 2000 solution to XP here, without some guarantee
that I'm not going to hurt the system by trying to fix it like that
when I try to start up, even though I disabled it. When I try to login, it
won't let me, and it is giving me the message in the subject title. I never
had a problem like this before, and I am using XP Home edition (service pack
2). The startup process is taking much longer than it did before, and now it
ends up with that message when I try to login. I was on a home workgroup, but
this didn't give me a problem before today. I tried switching to another
workgroup name, but it hasn't changed anything. I am using Safe Mode with
networking right now to post this message using the same computer, using the
Administrator account. I tried making a new username, but it won't let that
one login either. I tried system restore, but that didn't change anything.
I noticed a KB article saying that Win 2000 had similar errors, with 128-bit
encryption, but I haven't found a solution that pertained directly to XP. I'm
reluctant to apply the Win 2000 solution to XP here, without some guarantee
that I'm not going to hurt the system by trying to fix it like that