Re: Windows logon failure

Tech-Archive recommends: Fix windows errors by optimizing your registry

">It seems that you have tried the usual recipies to resolve
your looping logon problem and that none of them had
any effect"

Has 'Ribs' tried to hit F8 > select boot to 'last known good configuration',
or 'safe mode' and troubleshooted there?
I tried this on a HDD I just cloned. It goes to the logon screen but there
is no message politely telling me "windows is Loading" or users to load. In
both normal and safe mode I dont get a chance to logon. I figure its probably
a wpa thing maybe?
--
Brandon Dub., TO canada, Shell ''explorer''


"Pegasus (MVP)" wrote:

It seems that you have tried the usual recipies to resolve
your looping logon problem and that none of them had
any effect. I now wonder if your machine had some hard
disk problem all along and that some files or the registry
suffered some damage that manifests itself in this loop
phenomenon.

If this was my machine then I would take some drastic action:
- Back up all important data files.
- Boot the machine with my WinXP CD, then perform
a Repair installation over the top of the existing installation.
- If this fails to resolve the problem, format the disk and
start afresh.


"ribs" <ribs@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:32FEF449-22A3-46F1-9DB8-25AB4C70ABE7@xxxxxxxxxxxxxxxx
I haven't done steps 1-17 again since it seemed like all I was doing was
renaming the drive o C:, but it is named C: already at this point. I
tried
the command you gave and that made some noise but doesn't appear to have
fixed the initial problem still. I don't suppose there's anyway I could
send
you the appropriate directory, you could make the adjustments from there
and
send it back and I could just replace what I have? I don't know if that's
feasible or not, but its just that everything i've tried seems to not work
or
not work right.

"Pegasus (MVP)" wrote:

Run this command from a Command Prompt:

cacls X:\windows\system32\userinit.exe /p everyone:F

where X: is the drive letter for your problem disk.


"ribs" <ribs@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:57327B6D-8E6C-4E18-AE7E-4E1B5180668A@xxxxxxxxxxxxxxxx
Alright, at this point the situation has changed somewhat. We decided
that
my friend's PC isn't a good choice to be using at this point due to
the
fact
that during the same session that he was able to read my disk, a
number of
hours later it reported that my disk had no file system.

On the recomendation of a different friend, i downloaded miniPE, an
operating system running from a boot disk and used it to save my
important
files. It also comes with a registry editor. Right now I've
basically
"forgotten" the second disk altogether and am running off of just one,
named
C:. My initial problem still exists. I'm planning on repeating steps
1-17
now but could you explain what I need to do regarding the permission
settings
on userinit.exe? Sorry for being such a hassle and thanks in advance

"Pegasus (MVP)" wrote:

This is correct. When you have a disk with multiple
partitions then the system may be looking for userinit.exe
on the wrong partition. Creating multiple copies overcomes
this problem temporarily until you can apply a permanent
fix. Since you have only one partition, this issue is
irrelevant.

I note that you did not report on the permission setting
for c:\windows\system32\userinit.exe. Furthermore -
does this file have the same size and date samp as the
one on your friend's PC?


"ribs" <ribs@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:BF017542-6292-46BA-B96F-64953A79BBD2@xxxxxxxxxxxxxxxx
I only have one partition on the problem hard drive, so there's
only 1
drive
letter assigned to it. Isn't this solution for paritioned drives
with
multiple drive letters?

"Pegasus (MVP)" wrote:

Assuming you have drives Q:, R: and S: on your problem
disk while it is installed in your friend's PC (corresponding
to drives C:, D: and E: while it is installed in your own PC),
you must ensure that userinit.exe exists in these folders:

Q:\Windows\system32
R:\Windows\system32
S:\Windows\system32

Create the folders if they do not already exist.

You must also set your ntfs permissions so that all copies
of userinit.exe are readable by "everyone".

If successful, you will need to make some changes to the
registry when logging in the first time.

Have a look at this link too:
http://www.smilecomputers.nl/helpdesk/unablelogonadaware.htm


"ribs" <ribs@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:20BB9CCB-F873-4DE6-98D8-0D7023D594EA@xxxxxxxxxxxxxxxx
Alright I used Acronis TrueImage to succesfully clone my drive
(I
ended up
having to buy the full version but if I can save my computer
it's
a
small
price to pay). As predicted it didn't solve the original
problem.
But my
friend's PC can now read my drive. Anyways, we tried 1-17 to
see
if
it
would
work and it didn't. We were ready to try 18 but we don't
really
understand
exactly what you mean.:

18. To add braces to your belt, copy
X:\windows\system32\userinit.exe
to \windows\system32 on ***every*** other drive on the problem
disk.
Make new folders if necessary.

We found the userinit.exe but we are unsure as to where we
should
copy
it
to. What do you exactly mean by every other drive on the
problem
disk?
I'd
appreciate it if you rewrote that step a bit more clearly.

"Pegasus (MVP)" wrote:

I see. Things are getting a little murky here. If this was
my
machine
then I would move immediately into "salvage" mode. The
easiest
way to do this is by installing the disk as a slave disk in
some
other
PC but since that "other" PC won't recognise the disk, you
cannot
use this option. Here are your remaining options:
a) Repartition & reformat the disk. Install WinXP and all
applications.
You will, of course, lose all data.
b) Hand the disk to a recovery service. They can probably
fix it
at a price.
c) Create a clone of your disk while on your own PC.

Option c) can be achieved in several ways. Here are two of
them:

1. Get a copy of Acronis TrueImage, install it on your
friend's
PC
and use it to burn a boot CD. Boot your own PC with this
CD
and create a clone of your problem disk on some spare
disk.
It may even be possible to do this with a demo version
of
TrueImage - you'll have to find out for yourself.

2. Burn a Bart PE boot CD on your friend's PC
(http://www.nu2.nu/pebuilder/#download),
then boot your own machine with this CD. Now use this
command to create a clone of your disk on some spare
disk:
xcopy /s /e /c /h /d /k /o /y d:\*.* e:\*.*
where D: is the problem disk and E: is the spare disk,
which
must have been formatted under WinXP.

Option c) involves spending money or spending two or three
hours to create a Bart PE CD. Since it is unlikely to
resolve
your
original problem, you might want to go for options a) or b).


"ribs" <ribs@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:A93FD5E8-48F4-4942-8FDB-D7AF46502270@xxxxxxxxxxxxxxxx
Sorry. I'm on a friend's PC, attempting to implement your
solution.
Once
we
got on, it claimed that my drive (the one i just installed
on
his
PC)
was
not
formatted. We tried to continue with the solution anyway,
getting
as
far
as
step 8. but on step 9. regedit claimed that
X:\windows\system32\config\system
did not exst. We then used the Computer Management tool
to
exam
the
drive
and found that it supposedly had about 500 GB of
unallocated
space
in
addition to the 70-something GB normal partition, and that
my
disk
didn't
appear to be formatted.
We assumed that my index was corrupt and were considering
finding
a
data
recovery specialist. I put the disk back on my machine
and it
still
booted
up as far as the login screen, meaning my index is NOT
corrupt
(or
else it
wouldn't have recognized that I have windows at all,
right?).
Any suggestions?

"Pegasus (MVP)" wrote:

I'm afraid your post makes no sense. Your initial
problem
was
a looping logon screen. This is in most cases caused by
an
incorrect system drive assignment.

In your most recent note you speak about Computer
Management
tools, implying that you could finally log on, and raw
disks,
which
implies that you have destroyed your Windows
installation.
This
is
contradictory.

I suggest you state clearly what you did and what you
have.
Statements
such as "I accidentally hit that this answered my
question"
or
"My
bad"
mean nothing to me.


"ribs" <ribs@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message

news:5FC1B90A-E748-4BE8-878F-1E0468BE1B46@xxxxxxxxxxxxxxxx
Oops I accidentally hit that this answered my
question.
My
bad.
Anyway
I'm
almost about to kill myself because according to my
friend's
PC,
My
disk's
file system is raw. I'm assuming I need to sell my
soul
to a
data
recovery
specialist now? or something like that? The Computer
.

Relevant Pages

  • Re: Windows logon failure
    ... "Pegasus (MVP)" wrote: ... disk problem all along and that some files or the registry ... a Repair installation over the top of the existing installation. ...
    (microsoft.public.windowsxp.general)
  • Re: Log in problems
    ... Pegasus (MVP) wrote: ... True, but getting into a stolen laptop is child's play anyway, even ... its disk, put it into a 2.5" USB disk case and connect that case to ...
    (microsoft.public.win2000.general)
  • Re: Spell checking
    ... that you can get a bad installation. ... What is the difference between Empty Trash and Empty Trash Securely? ... the disk file table to mark the file as "available for overwriting". ...
    (microsoft.public.mac.office.excel)
  • Re: Windows logon failure
    ... "Pegasus (MVP)" wrote: ... Temporarily install the problem disk as a slave disk in ... Find out the current drive letter for the bad disk's drive C:. ...
    (microsoft.public.windowsxp.general)
  • Re: Can you reduce bloated Windows Folder to increase disk space on La
    ... Installed Windows XP Home Edition SP1 from disk, ... Restore Point created and System files backed up in installation ... Highlight one of your drives and click on ...
    (microsoft.public.windowsxp.newusers)