Built-in admin account screwed by KB912812

[LeDave]

Hi,

I have my built-in administrator account screwed after I applied patch
KB912812.
When I reboot, after I passed the logon screen, it crashes with a fatal
error, logon failure BSOD.
The workaround I have is to logon with a different user, log off then
login with the built-in admin account. Sounds like the order of the
starting of services is messed up in my profile.
Note: At the initialization of my laptop, I was asked to give a logon
for the Administrator (I didn't know it was the built-in account) so it
is not 'Administrator' but 'LeDave'. I can see that in the admin
console.

The other thing I noticed: under "Documents and Settings", after the
patche was applied, the data under \Administrator was moved to \LeDave
(well, not everything). Because, althgouth the name changed, it was
still using \Administrator folder and there was no \LeDave.
If I look at the available profiles (System Properties/Advanced/User
Profiles), there is now no Administrator.
Some apps are still writing to \Administrator folders.

Question: How can I have my built-in account revert back to use
\Administrator folders for sure?

 

[Gordon]

Hi,

I have my built-in administrator account screwed after I applied patch
KB912812.
When I reboot, after I passed the logon screen, it crashes with a fatal
error, logon failure BSOD.
The workaround I have is to logon with a different user, log off then
login with the built-in admin account.

Not an answer directly, but you do know that it is NOT good practice to use
just the built-in administrator account for day-to-day use? If that account
becomes corrupted, there is NO WAY you can access your machine without
doing a repair install of XP. Create another user account (give it Admin
rights if you want) and use that one for day-to-day use. Leave the built-in
administrator account for emergencies.

 

[LeDave]

Thank you reminding me how safe, secure and solid is the Neanderthal
Technology.

I know I got screwed by an official MS update not by my misuse of the
system... if using the built-in account is that bad.

I dunno what these idiots changed but even in last ressort I tried for
the 1st time in my windows user's life the PC restore to a checkpoint
made earlier before applying the patch and it didn't resolve.
What I am afraid of is now that built-in account is made to use the
profile named of the login name instead of 'Administrator'. So I am not
keen to copy 'LeDave' profile into the 'Administrator'.
I am pretty sure it has something to do with a service starting in my
profile but can see which one it is.