Sign in with
Sign up | Sign in
Your question

Logon Error - The parameter is incorrect

Last response: in Windows XP
Share
Anonymous
April 5, 2005 3:29:03 PM

Archived from groups: microsoft.public.windowsxp.help_and_support (More info?)

I am running Windows XP Home and have recently tried to install the SP2.
However, this installation was unseuccessful resulting in the computer
crashing.

On restarting instead of going direct to the logon screen it went to a
'Recovery Screen' resetting windows prior to the SP2 update.

After this, It restarted. I tried to log on but after a few seconds it kept
coming up with the old error box, saying explorer needs to close?!?!

After this I started the comp and slected the last know good configuration
method and yet more problems.

Now when the logon screens appears (eventually) after entering my password I
get the error message:

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

The parameter is incorrect.

Please try again or consult you system administrator.

I am unable to run the Recovery console, in selecting it I just get a blank
screen. I have a Startup CD if I run that and select the recovery console
from there, it takes me to DOS asks me which windows to repair, needs a
password?!?!? Doesn't accept any of my passwords and by leaving it blank it
exits the recovery console!!!

AArrggghh!!!! If you still reading my dilema thanks for you time and can
anyone help me at all?!?!? I know the easy answer is a wipe and reinstall
but stupidly my backups are out of date and I stand to loose months of design
work!

Help!!

Thanks to anyone who can and the beers on me!!!
Anonymous
April 14, 2005 12:49:06 PM

Archived from groups: microsoft.public.windowsxp.help_and_support (More info?)

Try using the 'last known good configuration' on bootup. I work in a
school district where this has become a widespread problem.

We use a SUS server to push down updates and I havea bout 20 machines
that are all doing this. 'Last known good sonfiguration' seems to work
on them, but it seems like it is only a temporary fix and reimaging
isn't an option for me.

Has microsoft acknowledged this problem yet? It seems like it is
happening all over the place when sp2 is installed.

Any further info is much appreciated...
!