Windows 2003 ntoskrnl exe
Профиль | Отправить PM | Цитировать | пробовал копировать с установочного диска » |
——-
Если сообщение оказалось полезным, нажмите, пожалуйста, соответствующую кнопку.
Windows 2003 ntoskrnl exe
| пробовал копировать с установочного диска » |
——-
Если сообщение оказалось полезным, нажмите, пожалуйста, соответствующую кнопку.
Windows 2003 ntoskrnl exe
This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.
Answered by:
Question
A Windows 2003 Server was bluescreening with 0x00000007b error, which was a result of p2v conversion (scsi drivers were not injected at the end of the conversion). I no longer have access to a physical machine, so all I have is a virtual that needs to be repaired. Checkdisk identified logical problems on the drive and was able to repair them. After checkdisk finished I am getting
Windows could not start because the following file is missing or corrupt:
Windows root\system32\ntoskrnl.exe
Please re-install a copy of the above file.
I am able to boot in to recovery console from the installation CD, but if I attempt to reintall windows on the top of the existing installation, the installer does not give me an option to repair and wants to install Windows in another directory.
Any suggestions are greatly appreciated.
Answers
If you still think controller driver issue then you can try loading a controller driver at boot. Edit the boot.ini to give it a correct ARC path for the machine you wish to boot.
In order for this to work you’ll want to change the arc path in boot.ini from multi syntax to scsi syntax to indicate that Windows 2003 will load a boot device driver and use that driver to access the boot partition. Then also copy the correct manufacturer controller driver to C:\ but renamed to ntbootdd.sys
Something like this below;
[boot loader]
timeout=10
default=scsi(0)disk(0)rdisk(0)partition(1)\WINNT
[operating systems]
scsi(0)disk(0)rdisk(0)partition(1)\WINNT=»Windows 2003 0,1″
scsi(0)disk(0)rdisk(0)partition(2)\WINNT=»Windows 2003 0,2″
scsi(0)disk(1)rdisk(0)partition(1)\WINNT=»Windows 2003 1,1″
scsi(0)disk(1)rdisk(0)partition(2)\WINNT=»Windows 2003 1,2″
Regards, Dave Patrick .
Microsoft Certified Professional
Microsoft MVP [Windows]
Disclaimer: This posting is provided «AS IS» with no warranties or guarantees , and confers no rights.
Windows 2003 ntoskrnl exe
1. Do you mean that you were even not able to boot from CD/DVD? Did you change the boot order in BIOS to boot the computer from CD/DVD first? It normally won’t happen unless there’s something wrong with your DVD drive.
2. What’s the exact error on the screen?
If you are able to boot from installation media, please perform a startup repair of Windows Server 2003 R2. To do this, please follow these steps.
1. Insert the Windows Server 2003 R2 CD in the CD-ROM or DVD-ROM drive.
2. Restart the computer to boot from CD/DVD.
If you are prompted to start your computer from the CD, do so.
3. After Setup starts, press ENTER to continue the setup process.
4. Press ENTER to select the option To set up Windows now, press ENTER. Do not select the Recovery Console option.
5. Press F8 to accept the licensing agreement.
Setup searches for previous installations of Windows.
o If Setup does not find a previous installation of Windows Server 2003, you might have a hardware failure.
o If Setup does find a previous installation of Windows Server 2003, you may receive the following message:
If one of the following Windows Server 2003 installations is damaged, setup can try to repair it. Use the up and down arrows to select an installation. To repair the selected installation, press R. To continue without repairing, press ESC.
Select the appropriate Windows Server 2003 operating system installation, and then press R to try to repair it.
o Follow the on-screen instructions to repair the installation.
Karen Ji
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ” This posting is provided «AS IS» with no warranties, and confers no rights.
I tried this procedure but it went into the long process of windows installation. Is this normal? And if it is, does the process not cause me to lose any data or policies already set up on the server?
Hi All,
My related question; I have some responsibility for a server running (an OEM Version of) SBS2003 Std R2;
In the last few days Its 2003 SBS O/S (On Raid5) Disks, crashed and as the remaining 2 disk became corrupted , We were left with an absolutely dead system; The site uses AppAssure as a back-up/Recovery solution, So with some trouble I managed to restore the C Drive to a new single drive (Not to the RAID 5Array); But on trying to boot the restored O/S I am also getting the «missing or corrupt ntoskrnl.exe» Error; I have to add that it seems that all of the original System, Driver & utilities (Including the OS) CDs have been lost; So therefore I am not able to run the Repair routine from the set up disks; I did try taking an older back-up copy of ntoskrnl.exe, and replacing it on the restored drive but it seems that this file is Ok and its throwing up the error message due to some other dependancy?
My question is: Is it feasible that I’ll be able to repair this restored drive, just by using Copies of the backed up C: Drive that were taken a few weeks before it died and therefore the file/s condition should be considered «healthy»? As I have no other copy of the install or original disks.
I have looked around for (Risky) Torrent copies of the install disks in the hope of finding away of running the Repair routine, but have not found it online as yet.
Any helpful advise or input appreciated; I may also be giving some prayer & laying-on of hands, with attitude!! 😉
Windows 2003 ntoskrnl exe
| пробовал копировать с установочного диска » |
——-
Если сообщение оказалось полезным, нажмите, пожалуйста, соответствующую кнопку.
