The program issued a command but the command length is incorrect

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

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. Implementing "Last
known good configuration" does not fix the problem.
 
help.me said:
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. Implementing "Last
known good configuration" does not fix the problem.

Google gives me about 300 hits for this error message.
 
Pegasus said:
Google gives me about 300 hits for this error message.
Me, too, but I still didn't find a solution. Lots of guesses about
malware, etc. All this tells me is that this is a common problem.
 
GateKeeper said:
Me, too, but I still didn't find a solution. Lots of guesses about
malware, etc. All this tells me is that this is a common problem.

Can you press F10 during boot, and do a non-destructive repair install?
 
Back
Top