Installation of 34 updates has screwed something up on log-in

[Guest news.microsoft.com]

Had a computer die on me yesterday (only processor fan working on plug in,

nothing whatsoever else and on/off switch lights up but doesn't do anything)

so I pulled out a box I hadn't used in some months

 

It logs in in a peculiar way, with the need to CAD and then type in

ADMINISTRATOR (and no password) before it will start windows. Never figured

out why though it calls it some type of 'security policy'. There are two

names in the lower part of the screen, DOMAIN1 and some past user. Neither

of which will log on. I assume someone in a past life had this on some

network but I certainly don't need this any more.

 

On start, I used it for a few hours successfully and then shut down. On

restart it wanted to install updates and installed 34 of them, all

successfully. Something was telling it however not to let me go on line,

presumably as these updates hadn't been installed and it wasn't considered

safe by the OS?

 

However I cant now get the computer to start properly: It wont get past the

CAD log in screen. It wont accept the ADMINISTRATOR user name or accept OK

in either instance or let me cancel out (canceling out just gets me back to

the screen telling me to CAD again.

 

Does anyone recognise these symptoms please? Do I just boot into a UBCD4WIN

file manager screen, delete the SAM file and edit the boot.ini in some way

and if so, how? Delete everything to the right of the windows start line and

put in /fastdetect?