Logon Error: "command length is incorrect" (NO ONE LOGON)

[Griobhtha]

I've seen another post somewhere and someone else had this problem,
but I haven't found a solution. We're using WXP Pro, SP2.

After doing a repair install (the other person just had it after using
Windows Update), at logon, after entering the correct, AND VALID,
password either for a user or the Administrator, Windows Logon
displays the following Logon Message in a box:


"! The system cannot log you on due to the following error:

"The program issued a command but the command length is incorrect.

"Please try again or consult your administrator."


No matter how many times logon is attempted, or with what account, the
message continues to be issued. Thus, NO ONE can logon to the GUI.

The Recovery Console can be used to logon as Administrator, but no
password is requested even though there is one in place. I've
searched the MSKB but didn't find any reference.

I am at a total loss and pulling my hair out. Please help.

Thanks,
Griobhtha

 

[Malke]

I've seen another post somewhere and someone else had this problem,
but I haven't found a solution. We're using WXP Pro, SP2.

After doing a repair install (the other person just had it after using
Windows Update), at logon, after entering the correct, AND VALID,
password either for a user or the Administrator, Windows Logon
displays the following Logon Message in a box:


"! The system cannot log you on due to the following error:

"The program issued a command but the command length is incorrect.

"Please try again or consult your administrator."

When a user tries to logon, he is asked for a password and gets the
error message: "Program issued a command but the command length is
incorrect".

This is caused by Update KB885835 and booting to Last Known Good
Configuration will get them in and this seems to solve the issue. Some
people have found that it is not necessary to remove the update and
some people have had the opposite experience.

Malke

 

[Griobhtha]

Addendum: Same occurs in Safe Mode and after utilizing "Last known
good configuration".

 

[Malke]

Addendum: Same occurs in Safe Mode and after utilizing "Last known
good configuration".

Ah, having the "addendum" information makes a big difference. The only
thing I can suggest is trying to change the Administrator password to a
blank and see if you can get in that way. Otherwise, I would guess that
whatever you were trying to fix with a Repair Install didn't get fixed
and you are looking at a Clean Install.

Boot with NTpasswd to change the Administrator password to a blank:
http://home.eunet.no/~pnordahl/ntpasswd/

Clean install:
http://michaelstevenstech.com/cleanxpinstall.html

Malke