XP Home will not allow any log on

RBBRMADE

Senior member
Oct 28, 2003
491
0
0
I have a XP Home system that will not allow the owner or admninistrator to log on, even in safe mode. Owner is the only account set up on the PC.
I have tried ntpassword with no luck, setting a blank pass, and another pass, on both owner and admin. I have used ntpassword many times with no issues.
Whenever I try to log on to Windows XP Home, I get the message:

Local Policy of this System does not Permit you to Logon Interactively

I have googled, but cannot find a fix.

I have a bootable Bart's PE disk, and I can connect the HDD to another machine easily, so I can edit the registry, but none of the fixes work so far.

CAN ANYONE HELP? It's going to be a pain reloading and finding all the software they were using on this thing.

The machine has a parallalel copy of Windows on it, so I am now trying to move as much stuff over to it as I can.

IS THER ANY WAY TO MOVE PROGRAMS FROM ONE INSTALL TO THE OTHER?

Thanx, Ron
 

Mutilator

Diamond Member
Aug 22, 2000
3,513
10
81
So is this your PC or someone elses? Any idea what caused the problem?
As far as I know, no, you can't move programs from 1 to the other.

I'm pretty sure I know how to fix the problem, but I'm not sure how you're going to be able to apply the fix. The problem is most likely a local security policy setting that somehow got changed so no users are allowed to log on locally.
The fix would be to do this:
Start -> Run -> secpol.msc
Expand Local Policies
Click on User Rights Assignment
Look for Log on locally - make sure users are listed - my PC has "Guest, Administrators, Users, Power Users, Backup Operators" - if none are listed there (or at least not the group(s) your particular user(s) are in then that's your problem.

But since you can't get in even in safe mode then you could always try a repair install, or see if a CD like Barts lets you open the secpol.msc console.

Typically what you're seeing only affects PCs logging on remotely using remote desktop connection - but if that setting above got changed then it would cause the same thing for local users as well.
 

Turkey22

Senior member
Nov 28, 2001
840
0
0
That's what I was thinking too, that the local policy is set to not let you logon. I'm guessing either a prank or a possible virus could do that.