C
CIBC
Had a problem last week - here's the problem, scroll down
to ********* for our solution.
This is a problem that I have found listed on a few
websites, but no one seems to have a solution. It is not
an easy solution as we have tried the easy fixes and also
spent 2+ hours on the phone with microsoft and dell
today. I think that we are somehow being locked out of
the system because of a MS security update from 2/22.
Are there any settings I can changed in the recovery
console to allow entry to our desktop. User names and
passwords are ok, I checked to make sure, but I just
can't seem to logon.
Here is the history:
The last thing that was done at night was to install the
update (I believe it is KB887742 but can't get into the
computer to confirm)
In the morning, we get the blue screen that says to
logon. There are no user names as options to logon as.
Doing ctrl-alt-del gets you to the classic style logon,
but still can't logon as eitehr our user name or as
administrator.
Neither account has a password set for them. We
confirmed that this was so this afternoon using a linux
program that let us look at passwords even if we can't
logon.
We have tried:
1. Logon as usual - get blue screen that says logon,
only no possible way to do so.
2. Start up in safe mode. - Same thing happens - get
blue screen that says logon, but no possible way to do so.
3. Starting up with recovery consol. Can't get anywhere
from there either, but I don't totally know what else to
do from here or what settings to try and change.
4. Tried the repair reinstall of windows. Took us back
to SP1 I think, but still can't logon.
We do think it is related to the update released on
Tuesday, Feb 22. Maybe there was some glitch in phone
lines when we were downloading? Seems to have happened
to a few people but not an extremely high number.
*****************************
We spent time with microsoft and dell on the phone,
neither could help.
Tried to reset the passwords first using this program:
http://home.eunet.no/~pnordahl/ntpasswd/
Tried info on this page which seemed like a good
workaround fix, but it didn't work for us. Maybe it
would work for you? A basic repair to the registry using
original installation info.:
http://www.digitalwebcast.com/articles/viewarticle.jsp?
id=8658-0
We ended up puttin in a 4 GB hard drive as the primary
drive with our original drive as slave. Put xp on the 4
gig hard drive so we could boot to that. Copied
everything from our original hard drive to the 4G drive
(even the windows folder) and then switched the hard
drives again so our original was the master and the 4GB
as the slave. Formatted the original, reinstalled XP
home on the original, and moved to the original all the
my documents, etc. that we had backed up onto the 4 GB
drive. The 4 GB was out of an old computer so no
expense, and we'll keep it in the computer as a secondary
drive for easy backup. With the backup all internal, I
didn't worry about formatting and reinstalling xp as knew
I could always find the file or info I needed on the
backup, but I couldn't have backed up that much info onto
a CD.
Hope the rest of you with this problem end up with an
easy fix.
to ********* for our solution.
This is a problem that I have found listed on a few
websites, but no one seems to have a solution. It is not
an easy solution as we have tried the easy fixes and also
spent 2+ hours on the phone with microsoft and dell
today. I think that we are somehow being locked out of
the system because of a MS security update from 2/22.
Are there any settings I can changed in the recovery
console to allow entry to our desktop. User names and
passwords are ok, I checked to make sure, but I just
can't seem to logon.
Here is the history:
The last thing that was done at night was to install the
update (I believe it is KB887742 but can't get into the
computer to confirm)
In the morning, we get the blue screen that says to
logon. There are no user names as options to logon as.
Doing ctrl-alt-del gets you to the classic style logon,
but still can't logon as eitehr our user name or as
administrator.
Neither account has a password set for them. We
confirmed that this was so this afternoon using a linux
program that let us look at passwords even if we can't
logon.
We have tried:
1. Logon as usual - get blue screen that says logon,
only no possible way to do so.
2. Start up in safe mode. - Same thing happens - get
blue screen that says logon, but no possible way to do so.
3. Starting up with recovery consol. Can't get anywhere
from there either, but I don't totally know what else to
do from here or what settings to try and change.
4. Tried the repair reinstall of windows. Took us back
to SP1 I think, but still can't logon.
We do think it is related to the update released on
Tuesday, Feb 22. Maybe there was some glitch in phone
lines when we were downloading? Seems to have happened
to a few people but not an extremely high number.
*****************************
We spent time with microsoft and dell on the phone,
neither could help.
Tried to reset the passwords first using this program:
http://home.eunet.no/~pnordahl/ntpasswd/
Tried info on this page which seemed like a good
workaround fix, but it didn't work for us. Maybe it
would work for you? A basic repair to the registry using
original installation info.:
http://www.digitalwebcast.com/articles/viewarticle.jsp?
id=8658-0
We ended up puttin in a 4 GB hard drive as the primary
drive with our original drive as slave. Put xp on the 4
gig hard drive so we could boot to that. Copied
everything from our original hard drive to the 4G drive
(even the windows folder) and then switched the hard
drives again so our original was the master and the 4GB
as the slave. Formatted the original, reinstalled XP
home on the original, and moved to the original all the
my documents, etc. that we had backed up onto the 4 GB
drive. The 4 GB was out of an old computer so no
expense, and we'll keep it in the computer as a secondary
drive for easy backup. With the backup all internal, I
didn't worry about formatting and reinstalling xp as knew
I could always find the file or info I needed on the
backup, but I couldn't have backed up that much info onto
a CD.
Hope the rest of you with this problem end up with an
easy fix.