HELP or I'LL DIE

[VKuk]

j/k
The problem is. I had Win NT Service pack 6. Then I had some problems and I decided to 'repair' it usind Win NT installation CD. I've repaired it back to Service Pack 1. And now lsass.exe and services.exe (programs whech you can see in Task Manager, are taking 100% of CPU. Trying to upgrade back to Service pack 6.0a, but it is so slow, almost impossible. Any ideas why lsass.exe and services.exe taking 100% CPU time????
HELP!!!!

[redwench]

who knows, its NT. you cant shut those programs down, but start shutting down others. its also possible that since you removed most of the patches that you now have a rather nasty bug on your computer, which is causing the problem.

[VKuk]

that's what I think too. BUG! I just hope that after 3-4-hours installation of SP6.0a, computer will work fine again.

[VKuk]

and I can't shut those two down, Access denied. :-(

[redwench]

you dont want to shut those down. find other things to turn off.

[ScottK]

1. Log-in as Administrator or as a user that is a member of the Administrative group.

2. Go into Control Panel -> Services

3. Go to items like FTP Publishing Service, Web Publishing Service, Telnet Service and any other Service that you do not need to be running at that time, get the Properties of each and click on the "STOP" button. Killing the process in Task Manager is NOT the proper & safe thing to do in regards to such items on WinNT. DO NOT "STOP" any of the Networking-related Services (Like the RPC Services) while you are trying to resolve this issue or performing the SP updates or you will bork things up nicely. While doing this, carefully keep track of the load that lsass.exe and Services.exe are taking up. Remember to keep track of each Service you've stopped.

4. As soon as you see your system performance level-off to a reasonable level, STOP - do not go any further.

5. Perform the SP upgrade.

6. When completed, DO NOT REBOOT - go back to Services and START all of the Services you stopped in Step 3.

7. Reboot.

Note: If you just re-installed WinNT by just overwriting the existing installation, you have a 95% chance of severely screwing your NT Install. The best solution would be to make sure that you have your 3 NT Install diskettes and the CD handy and *NUKE* the $systemroot$ directory (c:\windows or c:\winnt). Chances are that since you used the SRF (System Repair Facility) in WinNT that it might not have cleaned-up any tendencies in the Registry/Hive that were placed there by the SP6 updates, and the SP1 core is unable to properly use the entries in the SP6-adjusted Registry/Hive.

Hope this helps.

ScottK (former member of Kernel, API & Test Group in NT 3.1 DevTeam)

[VKuk]

Great!!!!!!
Okay, I ve stopped as many services as I could. Installed SP6.0a. It took computer only 6 hours (or8?) to do it. Then I started most of services I could. Restarted! WORKS FINE!
YEEEEEHHHHHAAAAAAAA !!!
redwench and ScottK - THANK YOU GUYS! You totally rock!