Forum Search:
Forum.Brain-Cluster.com: Brain Cluster Technical Forum
Ultimate forum for Technical Discussions

Home » Microsoft » Windows Server » Windows Server General Help » windows could not start because the following file is missing
windows could not start because the following file is missing [message #163506] Tue, 02 June 2009 21:28 Go to next message
vdz  is currently offline vdz
Messages: 50
Registered: July 2009
Member
Hi All,

At the moment we got one critical server has gone down and upon at boot,
there is an error message as below:

------------------------------------------------------------ -----------------------------------
Windows could not start because the following file is missing or corrupt:
\WINDOWS\SYSTEM32\CONFIG\SYSTEM
You can attempt to repair this file by starting Windows Setup using the
original Setup CD-ROM.
Select ‘r’ at the first screen to start repair.

I have searched for this solution, it is more likely system hive.
We have a proper backup system everyday (tape backup -Backup Exec), my
question is that how can I restore the system files from a backup tape for
this server that currently is malfunction?

Any idea/help would be much appreciated.

Regards
Re: windows could not start because the following file is missing [message #163507 is a reply to message #163506] Tue, 02 June 2009 22:47 Go to previous messageGo to next message
Dave Patrick  is currently offline Dave Patrick  United States
Messages: 560
Registered: July 2009
Senior Member
If the system hive is corrupt, and assuming you already tried LKG (F8 and
choose Last Known Good), It may be possible to rename the system hive found
in
%systemroot%\system32\config\system
to system.old
then copy
%systemroot%\repair\regback\system
to
%systemroot%\system32\config\system

You can also restore the system state backup to an alternate location and
harvest the system hive for replacement (I'd use whichever is newer).


If that fails you haven't much choice but to copy/ use the
original-as-installed system hive from
%systemroot%\repair\system
to
%systemroot%\system32\config\system
You'll need to reinstall the device drivers for any hardware added since the
original OS install.

To start the Recovery Console, start the computer from the Windows 2003
installation media. At the "Welcome to Setup" screen. Press F10 or R to
repair a Windows 2003 installation, and then press C to use the Recovery
Console. The Recovery Console then prompts you for the administrator
password. If you do not have the correct password, Recovery Console does
not allow access to the computer. If an incorrect password is entered three
times, the Recovery Console quits and restarts the computer. Note If the
registry is corrupted or missing or no valid installations are found, the
Recovery Console starts in the root of the startup volume without requiring
a password. You cannot access any folders, but you can carry out commands
such as chkdsk, fixboot, and fixmbr for limited disk repairs. Once the
password has been validated, you have full access to the Recovery Console,
but limited access to the hard disk. You can only access the following
folders on your computer: drive root, %systemroot% or %windir%






--

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect


"vdz" wrote:
> Hi All,
>
> At the moment we got one critical server has gone down and upon at boot,
> there is an error message as below:
>
> ------------------------------------------------------------ -----------------------------------
> Windows could not start because the following file is missing or corrupt:
> \WINDOWS\SYSTEM32\CONFIG\SYSTEM
> You can attempt to repair this file by starting Windows Setup using the
> original Setup CD-ROM.
> Select ‘r’ at the first screen to start repair.
>
> I have searched for this solution, it is more likely system hive.
> We have a proper backup system everyday (tape backup -Backup Exec), my
> question is that how can I restore the system files from a backup tape for
> this server that currently is malfunction?
>
> Any idea/help would be much appreciated.
>
> Regards
Re: windows could not start because the following file is missing [message #163509 is a reply to message #163507] Tue, 02 June 2009 23:52 Go to previous messageGo to next message
vdz  is currently offline vdz
Messages: 50
Registered: July 2009
Member
Hi Dave,

Thanks for your reply,

No I didn't have a chance to get to LKG. I am just guessing this is too high
hive so it could not load the System files.

Now I am in the Recovery Console with correct password, since there are many
suggestions from my research including your help like from this web
http://support.microsoft.com/kb/269075

And I don't want to take a chance. Please confirm which suggestion?

Thank you very much again Dave

"Dave Patrick" wrote:

> If the system hive is corrupt, and assuming you already tried LKG (F8 and
> choose Last Known Good), It may be possible to rename the system hive found
> in
> %systemroot%\system32\config\system
> to system.old
> then copy
> %systemroot%\repair\regback\system
> to
> %systemroot%\system32\config\system
>
> You can also restore the system state backup to an alternate location and
> harvest the system hive for replacement (I'd use whichever is newer).
>
>
> If that fails you haven't much choice but to copy/ use the
> original-as-installed system hive from
> %systemroot%\repair\system
> to
> %systemroot%\system32\config\system
> You'll need to reinstall the device drivers for any hardware added since the
> original OS install.
>
> To start the Recovery Console, start the computer from the Windows 2003
> installation media. At the "Welcome to Setup" screen. Press F10 or R to
> repair a Windows 2003 installation, and then press C to use the Recovery
> Console. The Recovery Console then prompts you for the administrator
> password. If you do not have the correct password, Recovery Console does
> not allow access to the computer. If an incorrect password is entered three
> times, the Recovery Console quits and restarts the computer. Note If the
> registry is corrupted or missing or no valid installations are found, the
> Recovery Console starts in the root of the startup volume without requiring
> a password. You cannot access any folders, but you can carry out commands
> such as chkdsk, fixboot, and fixmbr for limited disk repairs. Once the
> password has been validated, you have full access to the Recovery Console,
> but limited access to the hard disk. You can only access the following
> folders on your computer: drive root, %systemroot% or %windir%
>
>
>
>
>
>
> --
>
> Regards,
>
> Dave Patrick ....Please no email replies - reply in newsgroup.
> Microsoft Certified Professional
> Microsoft MVP [Windows]
> http://www.microsoft.com/protect
>
>
> "vdz" wrote:
> > Hi All,
> >
> > At the moment we got one critical server has gone down and upon at boot,
> > there is an error message as below:
> >
> > ------------------------------------------------------------ -----------------------------------
> > Windows could not start because the following file is missing or corrupt:
> > \WINDOWS\SYSTEM32\CONFIG\SYSTEM
> > You can attempt to repair this file by starting Windows Setup using the
> > original Setup CD-ROM.
> > Select ‘r’ at the first screen to start repair.
> >
> > I have searched for this solution, it is more likely system hive.
> > We have a proper backup system everyday (tape backup -Backup Exec), my
> > question is that how can I restore the system files from a backup tape for
> > this server that currently is malfunction?
> >
> > Any idea/help would be much appreciated.
> >
> > Regards
>
>
Re: windows could not start because the following file is missing [message #163513 is a reply to message #163507] Wed, 03 June 2009 01:22 Go to previous messageGo to next message
vdz  is currently offline vdz
Messages: 50
Registered: July 2009
Member
Well, I followed your suggestion, I got this server back up and running now.
Much appreciated.

Regards

"Dave Patrick" wrote:

> If the system hive is corrupt, and assuming you already tried LKG (F8 and
> choose Last Known Good), It may be possible to rename the system hive found
> in
> %systemroot%\system32\config\system
> to system.old
> then copy
> %systemroot%\repair\regback\system
> to
> %systemroot%\system32\config\system
>
> You can also restore the system state backup to an alternate location and
> harvest the system hive for replacement (I'd use whichever is newer).
>
>
> If that fails you haven't much choice but to copy/ use the
> original-as-installed system hive from
> %systemroot%\repair\system
> to
> %systemroot%\system32\config\system
> You'll need to reinstall the device drivers for any hardware added since the
> original OS install.
>
> To start the Recovery Console, start the computer from the Windows 2003
> installation media. At the "Welcome to Setup" screen. Press F10 or R to
> repair a Windows 2003 installation, and then press C to use the Recovery
> Console. The Recovery Console then prompts you for the administrator
> password. If you do not have the correct password, Recovery Console does
> not allow access to the computer. If an incorrect password is entered three
> times, the Recovery Console quits and restarts the computer. Note If the
> registry is corrupted or missing or no valid installations are found, the
> Recovery Console starts in the root of the startup volume without requiring
> a password. You cannot access any folders, but you can carry out commands
> such as chkdsk, fixboot, and fixmbr for limited disk repairs. Once the
> password has been validated, you have full access to the Recovery Console,
> but limited access to the hard disk. You can only access the following
> folders on your computer: drive root, %systemroot% or %windir%
>
>
>
>
>
>
> --
>
> Regards,
>
> Dave Patrick ....Please no email replies - reply in newsgroup.
> Microsoft Certified Professional
> Microsoft MVP [Windows]
> http://www.microsoft.com/protect
>
>
> "vdz" wrote:
> > Hi All,
> >
> > At the moment we got one critical server has gone down and upon at boot,
> > there is an error message as below:
> >
> > ------------------------------------------------------------ -----------------------------------
> > Windows could not start because the following file is missing or corrupt:
> > \WINDOWS\SYSTEM32\CONFIG\SYSTEM
> > You can attempt to repair this file by starting Windows Setup using the
> > original Setup CD-ROM.
> > Select ‘r’ at the first screen to start repair.
> >
> > I have searched for this solution, it is more likely system hive.
> > We have a proper backup system everyday (tape backup -Backup Exec), my
> > question is that how can I restore the system files from a backup tape for
> > this server that currently is malfunction?
> >
> > Any idea/help would be much appreciated.
> >
> > Regards
>
>
Re: windows could not start because the following file is missing [message #163533 is a reply to message #163513] Wed, 03 June 2009 05:20 Go to previous messageGo to next message
Dave Patrick  is currently offline Dave Patrick  United States
Messages: 560
Registered: July 2009
Senior Member
Good to hear, you're welcome.


--

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect


"vdz" wrote:
> Well, I followed your suggestion, I got this server back up and running
> now.
> Much appreciated.
>
> Regards
Re: windows could not start because the following file is missing [message #163548 is a reply to message #163533] Wed, 03 June 2009 07:53 Go to previous messageGo to next message
vdz  is currently offline vdz
Messages: 50
Registered: July 2009
Member
one more thing I would like to know. Since I did not use the system state I
back up everyday. I'd like to know how to copy/restore the backup system
state to the problem server while it is dead.
As you mentioned copy to another folder, I did that as well but I could not
find "System" file from the backup.

Thanks again

"Dave Patrick" wrote:

> Good to hear, you're welcome.
>
>
> --
>
> Regards,
>
> Dave Patrick ....Please no email replies - reply in newsgroup.
> Microsoft Certified Professional
> Microsoft MVP [Windows]
> http://www.microsoft.com/protect
>
>
> "vdz" wrote:
> > Well, I followed your suggestion, I got this server back up and running
> > now.
> > Much appreciated.
> >
> > Regards
>
>
Re: windows could not start because the following file is missing [message #163773 is a reply to message #163548] Sun, 07 June 2009 13:15 Go to previous messageGo to next message
Dave Patrick  is currently offline Dave Patrick  United States
Messages: 560
Registered: July 2009
Senior Member
You can't restore the system state to a "dead" machine. You would have
needed to reinstall the operating system. As for the other you must use
ntbackup to restore to an alternate location. The system state should
include at least the Boot files, COM+ class registration database, and the
registry. Then the file should be in a directory named Registry


--

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect


"vdz" wrote:
> one more thing I would like to know. Since I did not use the system state
> I
> back up everyday. I'd like to know how to copy/restore the backup system
> state to the problem server while it is dead.
> As you mentioned copy to another folder, I did that as well but I could
> not
> find "System" file from the backup.
>
> Thanks again
Re: windows could not start because the following file is missing [message #163842 is a reply to message #163773] Mon, 08 June 2009 22:11 Go to previous messageGo to next message
vdz  is currently offline vdz
Messages: 50
Registered: July 2009
Member
Thank you Dave. Actually this server already died yesterday, I think it was
harddisk faulty, looks like I got a long day at work, I have to reinstall
windows server 2003, then SQL 2000, then restore all the databases from
backup tape which saves my life, or I would be out of job :(.

Thanks again Dave.

Best Regards,



"Dave Patrick" wrote:

> You can't restore the system state to a "dead" machine. You would have
> needed to reinstall the operating system. As for the other you must use
> ntbackup to restore to an alternate location. The system state should
> include at least the Boot files, COM+ class registration database, and the
> registry. Then the file should be in a directory named Registry
>
>
> --
>
> Regards,
>
> Dave Patrick ....Please no email replies - reply in newsgroup.
> Microsoft Certified Professional
> Microsoft MVP [Windows]
> http://www.microsoft.com/protect
>
>
> "vdz" wrote:
> > one more thing I would like to know. Since I did not use the system state
> > I
> > back up everyday. I'd like to know how to copy/restore the backup system
> > state to the problem server while it is dead.
> > As you mentioned copy to another folder, I did that as well but I could
> > not
> > find "System" file from the backup.
> >
> > Thanks again
>
>
Re: windows could not start because the following file is missing [message #163845 is a reply to message #163842] Mon, 08 June 2009 22:19 Go to previous message
Dave Patrick  is currently offline Dave Patrick  United States
Messages: 560
Registered: July 2009
Senior Member
Sorry to hear but glad you have the backups. You're welcome for anything I
was able to offer.


--

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect


"vdz" wrote:
> Thank you Dave. Actually this server already died yesterday, I think it
> was
> harddisk faulty, looks like I got a long day at work, I have to reinstall
> windows server 2003, then SQL 2000, then restore all the databases from
> backup tape which saves my life, or I would be out of job :(.
>
> Thanks again Dave.
>
> Best Regards,
Previous Topic:RDP to server not responding
Next Topic:Is it possible to run a domain controller on a 32-bit o/s and an Exchange server on a 64-bit o/s?
Goto Forum:
  


Current Time: Tue Aug 22 14:50:00 EDT 2017

Total time taken to generate the page: 0.05668 seconds
.:: Contact :: Home ::Sitemap::.

Powered by: FUDforum 3.0.0RC2.
Copyright ©2001-2009 FUDforum Bulletin Board Software