specytechie
Technical User
My apologies for a pretty long first posting. Our Dell Power Edge 6005 Server OS MS Windows 2K. recently suffered a crash which has now happened twice - not in succession. After logging on and running Windows Critical updates allowing the 6 updates to flow, post a request from the system for a reboot our server has failed to come back up - both times displaying a message: "Windows 2000 could not start because the following file is missing or corrupt: Windows 2000 root>\system32\ntoskrnl.exe Please re install a copy of the above file".
Attempts to repair failed and we have re installing the Operating System as a second system (WINNT2). Last time, with some expert help, we managed to recover to the old OS and for two weeks (including an Windows Update) everything was fine. This time however, things are not looking so easy to recover. I remember that before I allowed the reboot the update had reported that some of the updates had failed. The new OS rebooted after repair of the boot.ini file.
Comparing WINNT and the new WINNT2 I see WINNT has numerous additional folders listed (e.g. $M121Uninstall_KB893803$, $M121Uninstall_KB893803v2$, $NTServicePackUninstall$, $NTUninstall_KB329115$,etc).
This leads me to suspect our problem resides with the update. Any advice available please.
N.B. I have tried asking MS about this but didn’t get any constructive assistance.
Geoff
Attempts to repair failed and we have re installing the Operating System as a second system (WINNT2). Last time, with some expert help, we managed to recover to the old OS and for two weeks (including an Windows Update) everything was fine. This time however, things are not looking so easy to recover. I remember that before I allowed the reboot the update had reported that some of the updates had failed. The new OS rebooted after repair of the boot.ini file.
Comparing WINNT and the new WINNT2 I see WINNT has numerous additional folders listed (e.g. $M121Uninstall_KB893803$, $M121Uninstall_KB893803v2$, $NTServicePackUninstall$, $NTUninstall_KB329115$,etc).
This leads me to suspect our problem resides with the update. Any advice available please.
N.B. I have tried asking MS about this but didn’t get any constructive assistance.
Geoff