The People with advanced programming Skills: April 2014

Wednesday, 23 April 2014

PRESS ANY KEY TO BOOT FROM CD DOESN’T WORK

PRESS ANY KEY TO BOOT FROM CD DOESN’T WORK BECAUSE THE USB KEYBOARD IS NOT RECOGNIZED IN DOS MODE.

TRY TO CHANGE THE PORTS OF THE USB KEYBOARD AND TRY FOR PRESS ANY KEY TO BOOT FROM CD,OR IF U GOT THE SAME PROBLEM . THIS TIME GO FOR BIOS SETTINGS.TO ENTER INTO BIOS SETTINGS RESTART YOUR SYSTEM AND CONTINUE PRESSING DEL ,NOW U WILL ENTER INTO BIOS SETTINGS.

NOW GO TO BIOS FEATURES SETUP THERE U WILL FIND “USB DOS ” IN DISABLED MODE BY DEFAULT TURN IT TO ENABLED MODE .THATS IT,EVERYTHING IS FINE AND PRESS ESCAPE AND SAVE THE BIOS SETTINGS BY PRESSING F10.NOW CHECK OUT THE DOS SCREEN “PRESS ANY KEY TO BOOT FROM CD” WORKS FOR SURE …..

Description of the Windows XP Recovery Console for advanced users

Important note

This is an advanced-level reference article that describes what the Recovery Console is and how to use it. It does not contain information about how to troubleshoot specific problems.

To use the Recovery Console, you will need a Windows installation disc.

You must be logged on as an administrator or a member of the Administrators group in order to run the computer in Recovery Console. If your computer is connected to a network, network policy settings may prevent you from completing this procedure. If you encounter this problem, you should contact the network administrator.

Expand all | Collapse all

INTRODUCTION

This article describes the functionality and limitations of the Windows Recovery Console. If a Windows XP-based computer does not start correctly or if it does not start at all, you may be able to use the Windows Recovery Console to help you recover the system software. This article discusses the following topics:

How to start the Windows Recovery Console from your Windows XP installation disc
How to use the Command Console
Restrictions and limitations of the Windows Recovery Console
The commands that are available in the Windows Recovery Console

More information

When you use the Windows Recovery Console, you can obtain limited access to the NTFS file system, FAT, and FAT32 volumes without starting the Windows graphical user interface (GUI). In the Windows Recovery Console, you can perform the following actions:

Use, copy, rename, or replace operating system files and folders
Enable or disable service or device startup the next time that you start your computer
Repair the file system boot sector or the master boot record (MBR)
Create and format partitions on drives

Note Only an administrator can obtain access to the Windows Recovery Console. This prevents unauthorized users from using any NTFS volume.

Option 1: If you have already installed the Recovery Console

If you have already installed the Recovery Console, you can select it during your usual Windows Startup. To run the Recovery Console:

During Startup, select Recovery Console from the startup options menu.
If you have a dual-boot or multiboot system, select the installation that you want to access from the Recovery Console.
When you are prompted, type the Administrator password.
At the command prompt, type Recovery Console commands, and then you can refer to the commands that are listed in the "Available commands within Windows Recovery Console" section.
At any time, you can type Help for a list of available commands.
At any time, you can type Help commandname for help on a specific command.For example, you can type help attrib to display the help on the attributes command.
At any time, you can exit Windows Recovery Console by typing Exit at the command line.

Option 2: Starting the Windows Recovery Console from the Windows XP CD-ROM

If you have not preinstalled the Windows Recovery Console, you can start the computer and use the Recovery Console directly from your original Windows XP installation disc. If your computer is already in Windows and you want to add the Windows Recovery Console as a startup option, go to the next section "Adding the Windows Recovery Console as a startup option."

Insert the Windows XP CD into your CD drive and restart your computer. If you are prompted, select any options required to start (boot) from the CD.
When the text-based part of Setup begins, follow the prompts. Select the repair or recover option by pressing R.
If you have a dual-boot or multiboot system, select the installation that you want to access from the Recovery Console.
When you are prompted, type the Administrator password.
At the command prompt, type Recovery Console commands, and then you can refer to the commands that are listed in the "Available commands within Windows Recovery Console" section.
At any time, you can type Help for a list of available commands.
At any time, you can type Help commandname for help on a specific command. For example, you can type help attrib to display the help on the attributes command.
At any time, you can exit Windows Recovery Console by typing Exit at the command line.

Option 3: Adding the Windows Recovery Console as a startup option

If your computer starts Windows, you can add the Windows XP Recovery Console as a startup option from the Windows environment. To install the Recovery Console as a startup option, follow these steps:

With Windows running, insert the Windows CD into your CD drive.
Click Start and clickRun.
Type the following commands (where X: is the CD Drive letter), and then press ENTER on your keyboard.
X:\i386\winnt32.exe /cmdcons
Note There is a space before /cmdcons.
Click OK and follow the instructions to finish Setup.

Note This adds the Windows Recovery Console to the Windows Startup folder.
Restart your computer and select the Recovery Console option from the list of available operating systems.

Important If you are using software mirroring, see the following article in the Microsoft Knowledge Base:

229077 Mirroring prevents pre-installing the Recovery Console

Restrictions and limitations of the Recovery Console

When you use the Windows Recovery Console, you can use only the following items:

The root folder
The %SystemRoot% folder and the subfolders of the Windows installation that you are currently logged on to
The Cmdcons folder
The removable media drives such as the CD drive or the DVD drive

Note If you try to access other folders, you may receive an "Access Denied" error message. This does not necessarily mean that data that is contained in those folders is lost or corrupted. It only means that the folder is unavailable while you are running the Windows Recovery Console. Also, when you are using the Windows Recovery Console, you cannot copy a file from the local hard disk to a floppy disk. However, you can copy a file from a floppy disk or from a CD-ROM to a hard disk, and you can copy a file from one hard disk to another hard disk.

Using the Command Console within Windows Recovery Console

The Recovery Console gives you limited access to the NTFS file system, FAT, and FAT32 volumes. Recovery Console prevents the familiar Windows Graphical User Interface (GUI) from loading in order to repair and recover Windows functionality.

After you start the Windows Recovery Console, you receive the following message:

Microsoft Windows(R) Recovery Console

The Recovery Console provides system repair and recovery functionality.
Type EXIT to exit the Recovery Console and restart the computer.

1: C:\WINDOWS

Which Windows Installation would you like to log on to ?
(To cancel, press ENTER)

Enter the number for the appropriate Windows installation. In this example, you would press 1. Then, Windows prompts you to enter the Administrator account password.

Note If you use an incorrect password three times, the Windows Recovery Console closes. Also, if the Security Accounts Manager (SAM) database is missing or damaged, you cannot use the Windows Recovery Console because you cannot be authenticated correctly. After you enter your password and the Windows Recovery Console starts, type Exit to restart the computer.

When you use Windows XP Professional, you can set group policies to enable automatic administrative logon. For more information about how to set Recovery Console to enable automatic administrative logon, click the following article number to view the article in the Microsoft Knowledge Base:

312149 How to enable an administrator to log on automatically in Recovery Console

Available commands within Windows Recovery Console

The following commands are available within the Windows Recovery Console. The commands are not case-sensitive.

Warning Some of these commands can make your system inoperable. Read the whole explanation of any command before you enter it onto the command line. Seek the advice of a support professional if you have any questions or concerns about a particular command.

HELP

Use the help command to list all the following supported commands:

   attrib    del        fixboot   more     set
   batch     delete     fixmbr    mkdir    systemroot
   bootcfg   dir        format    more     type
   cd        disable    help      net           
   chdir     diskpart   listsvc   rd            
   chkdsk    enable     logon     ren           
   cls       exit       map       rename  
   copy      expand     md        rmdir

ATTRIB

Use the attrib command together with one or more of the following parameters to change the attributes of a file or a folder:

-R
+R
-S
+S
-H
+H
-C
+C

Notes

+ Sets an attribute
- Resets an attribute
R Read-only file attribute
S System file attribute
H Hidden file attribute
C Compressed file attribute

You must set or clear at least one attribute.

To view attributes, use the dir command.

BATCH

batch inputfile [outputfile]

Use this command to run commands that are specified in a text file. In the command syntax, inputfile specifies the text file that contains the list of commands to be run, and outputfile specifies the file that contains the output of the specified commands. If you do not specify an output file, the output appears on the screen.

BOOTCFG

Use this command for boot configuration and recovery. This command has the following options:

bootcfg /add
bootcfg /rebuild
bootcfg /scan
bootcfg /list
bootcfg /disableredirect
bootcfg /redirect [portbaudrate] | [useBiosSettings]

Examples:

bootcfg /redirect com1 115200

bootcfg /redirect useBiosSettings

You can use the following options:

/add Adds a Windows installation to the boot menu list.
/rebuild Iterates through all Windows installations so that you can specify which installations to add.
/scan Scans all disks for Windows installations and displays the results so that you can specify which installations to add.
/default Sets the default boot entry.
/list Lists the entries already in the boot menu list.
/disableredirect Disables redirection in the boot loader.
/redirect Enables redirection in the boot loader, with the specified configuration.

CD and CHDIR

Use the cd and chdir commands to change to a different folder. For example, you can use the following commands:

Type cd .. to change to the parent folder.
Type cd drive: to display the current folder in the specified drive.
Type cd without parameters to display the current drive and folder.

The chdir command treats spaces as delimiters. Because of this, you must put quotation marks ("") around a folder name that contains a space.The following is an example:

cd "\windows\profiles\username\programs\start menu"

The chdir command works only in the system folders of the current installation of Windows, in removable media, in the root folder of any hard disk partition, or in the local installation sources.

CHKDSK

chkdsk drive /p /r

The chkdsk command checks the specified drive and repairs or recovers the drive if the drive requires it. The command also marks any bad sectors and it recovers readable information.

You can use the following options:

/p Does an exhaustive check of the drive and corrects any errors.
/r Locates bad sectors and recovers readable information.

Note If you specify the /r option, the /p option is implied. When you specify the chkdsk command without arguments, the command checks the current drive with no options in effect.

When you run the chkdsk command, you must use the Autochk.exe file. CHKDSK automatically locates this file in the startup folder. If the Command Console was preinstalled, the startup folder is typically the Cmdcons folder. If CHKDSK cannot find Autochk.exe in the startup folder, CHKDSK tries to locate the Windows installation disc. If it cannot find the installation media, CHKDSK prompts you for the location of the Autochk.exe file.

CLS

Use this command to clear the screen.

COPY

copy source destination

Use this command to copy a file. In the command syntax, source specifies the file to copy and destination specifies the folder or file name for the new file. You cannot use wildcard characters indicated by an asterisk (*), and you cannot copy a folder. If you copy a compressed file from the Windows installation disc, the file is automatically decompressed while it is copied.

The source of the file can be removable media, any folder in the system folders of the current Windows installation, the root of any drive, the local installation sources, or the Cmdcons folder.

If destination is unspecified, the default destination is the current folder. If the file already exists, you are prompted whether you want the copied file to overwrite the existing file. The destination cannot be removable media.

DEL and DELETE

del drive: path filename

delete drive: path filename

Use this command to delete a file. In the command syntax, drive: path filename specifies the file that you want to delete. The delete command works only in the system folders of the current Windows installation, in removable media, in the root folder of any hard disk partition, or in the local installation sources. The delete command does not accept wildcard characters.

DIR

dir drive: path filename

Use this command to display a list of files and subfolders in a folder. In the command syntax, drive: path filename specifies the drive, folder, and files to list. The dir command lists all files, including hidden files and system files. Files can have the following attributes:

D Directory
H Hidden file
S System file
E Encrypted
R Read-only file
A Files ready for archiving
C Compressed
P Reparse point

The dir command works only in the system folders of the current Windows installation, in removable media, in the root folder of any hard disk partition, or in the local installation sources.

DISABLE

disable servicename

Use this command to disable a Windows system service or a driver. In the command syntax, servicename specifies the name of the service or driver that you want to disable.

Use the listsvc command to display all services or drivers that are eligible to be disabled. The disable command prints the old start type of the service before resetting the start type to SERVICE_DISABLED. Record the old start type if you must enable the service again.

The disable command displays the following start_type values:

SERVICE_DISABLED
SERVICE_BOOT_START
SERVICE_SYSTEM_START
SERVICE_AUTO_START
SERVICE_DEMAND_START

DISKPART

diskpart /add/deletedevice_name drive_name partition_name size

Use this command to manage the partitions on your hard disk volumes. You can use the following options:

/add Creates a new partition.
/delete Deletes an existing partition.
device_name The name of the device that is used to create a new partition.
drive_name A drive-letter-based name, for example D:.
partition_name The partition-based name for deleting an existing partition.
size The size of the new partition in megabytes.

You can determine the device name from the output of the MAP command, for example, \Device\HardDisk0. You can use the partition name instead of the drive name argument, for example, \Device\HardDisk0\Partition1. If you use no arguments, a user interface for managing your partitions appears.

Warning If you use this command on a disk that has a dynamic disk configuration, you may damage the partition table. Do not modify the structure of dynamic disks unless you are using the Disk Management tool.

ENABLE

enable servicename start_type

You can use the enable command to enable a Windows system service or a driver.

Use the listsvc command to display all eligible services or drivers to enable. The enable command prints the old start type of the service before it is reset to the new value. It is a good idea to note the old value, in case you have to restore the start type of the service.

Valid options for start_type are as follows:

SERVICE_BOOT_START
SERVICE_SYSTEM_START
SERVICE_AUTO_START
SERVICE_DEMAND_START

If you do not specify a new start type, the enable command prints the old start type for you.

EXIT

Use the exit command to exit the Recovery Console and restart your computer.

EXPAND

expand source [/F:filespec] [destination] [/y]

expand source [/F:filespec] /D

Use this command to expand a file. In the command syntax, source specifies the name of the file to be expanded and destination specifies the folder for the new file. If you do not specify a destination, the command uses the current folder by default. You cannot include wildcard characters.

You can use the following options:

/y Do not prompt before overwriting an existing file.
/f:filespec Identifies the files to be expanded.
/d Do not expand; display only a directory of the files in the source.

If the source contains more than one file, you must use the /f:filespec parameter to find the specific files to be expanded. You can include wildcard characters.

The destination can be any folder in the system folders of the current Windows installation, in the root of the drive, in the local installation sources, or in the Cmdcons folder. The destination cannot be removable media, and the destination file cannot be read-only. Use the attrib command to remove the read-only attribute.

Unless you use the /y option, the expand command prompts you if the destination file already exists.

FIXBOOT

fixboot drive name:

Use this command to write the new Windows boot sector code on the system partition. In the command syntax, drive name is the drive letter where the boot sector will be written. This command fixes damage in the Windows boot sector. This command overrides the default setting, which writes to the system boot partition. The fixboot command is supported only on x86-based computers.

FIXMBR

fixmbr device name

Use this command to repair the MBR of the boot partition. In the command syntax, device name is an optional device name that specifies the device that requires a new MBR. Use this command if a virus has damaged the MBR and Windows cannot start.

Warning This command can damage your partition tables if a virus is present or if a hardware problem exists. If you use this command, you may create inaccessible partitions. We recommend that you run antivirus software before you use this command.

You can obtain the device name from the output of the map command. If you do not specify a device name, the MBR of the boot device is repaired, for example:

fixmbr \device\harddisk2

If the fixmbr command detects an invalid or non-standard partition table signature, fixmbr command prompts you for permission before it rewrites the MBR. The fixmbr command is supported only on x86-based computers.

FORMAT

format drive: /Q /FS:file-system

Use this command to format the specified drive to the specified file system. In the command syntax, /Q performs a quick format of the drive, drive is the drive letter of the partition to format, and /FS:file-system specifies the type of file system to use such as FAT, FAT32, or NTFS. If you do not specify a file system, the existing file system format is used if it is available.

LISTSVC

The listsvc command lists all available services, drivers, and their start types for the current Windows installation. This command is useful together with the disable and enable commands.

The list is extracted from the %SystemRoot%\System32\Config\System hive. If the System hive is damaged or missing, the results are unpredictable.

LOGON

logon

The logon command lists all detected installations of Windows and then requests the local administrator password for the copy of Windows that you want to log on to. If your first three tries to log on fail, the console closes, and your computer restarts.

MAP

map arc

Use this command to list drive letters, file system types, partition sizes, and mappings to physical devices. In the command syntax, the arc parameter tells the map command to use ARC paths instead of Windows Device paths.

MD and MKDIR

The md and mkdir commands create new folders. Wildcard characters are not supported. The mkdir command works only in the system folders of the current installation of Windows, in removable media, in the root folder of any hard disk partition, or in the local installation sources.

more filename

Use this command to display a text file to the screen.

NET

Although the Help file states otherwise, the net command is not usable from the Recovery Console. The protocols stack is not loaded for the Recovery Console. Therefore, there is no networking function available.

RD and RMDIR

Use rd and rmdir commands to delete a folder. These commands work only in the system folders of the current Windows installation, in removable media, in the root folder of any hard disk partition, or in the local installation sources.

REN and RENAME

Use the ren and rename commands to rename a file.

Note You cannot specify a new drive or path for the renamed file. These commands work only in the system folders of the current Windows installation, in removable media, in the root folder of any hard disk partition, or in the local installation sources.

SET

You can use the set to display or modify four environment options.

AllowWildCards = FALSE AllowAllPaths = FALSE AllowRemovableMedia = FALSE NoCopyPrompt = FALSE

For more information about how to use the set command, click the following article number to view the article in the Microsoft Knowledge Base:

235364 Description of the SET command in Recovery Console

SYSTEMROOT

The systemroot command sets the current working folder to the %SystemRoot% folder of the Windows installation that you are currently logged on to.

TYPE

type filename

Use the type command to display a text file.

Repairing Windows XP in Eight Commands

Most of us have seen it at one time or another; perhaps on our own PC, the PC of a loved one, or perhaps a PC at your place of employment. The system spends weeks or months operating in a smooth fashion, taking you to the far reaches of the wide, wibbly web, and after one particularly late evening of browsing and gaming, you shut your PC off and go to bed. Millions of people across the globe do just this every night, but a few of us have turned our PCs on the next day not to the standard Windows XP loading screen, but instead this dreaded error:
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.
Which renders your PC inaccessible from the standard boot procedures of Windows XP. You try safe mode, to no avail. You’re particularly savvy and try issuing the FIXBOOT and FIXMBR commands in the Windows recovery console, but after each reboot, you’re merely greeted with the same obnoxious and terrifying blue screen of death that’s preventing you from accessing your precious data.
Perhaps you’ve also seen these error screens:
Windows NT could not start because the below file is missing or corrupt:
X:\\WINNT\\System32\\Ntoskrnl.exe
_________________
Windows NT could not start because the below file is missing or corrupt:
X:\\WINNT\\System32\\HAL.dll
_________________
NTLDR is Missing
Press any key to restart
_________________
Invalid boot.ini
Press any key to restart
Allow me to build tension by prefacing the end-all/be-all solution with my background: Having worked for the now-incorporated Geek Squad branch of Best Buy Corporation for the better part of eight months, I have seen dozens upon dozens of systems come through our department with any one of these errors, brought in by customers who are afraid they did something, have a virus, or are in jeopardy of losing their data. Prior to my discovery of an invaluable sequence of commands, our standard procedure was to hook the afflicted drive to an external enclosure, back up a customer’s data and then restore the PC with the customer’s restore discs or an identical copy of Windows with the customer’s OEM license key. If the customer wasn’t keen on the applicable charges for the data backup, we informed them of the potential risks for a Windows repair installation (Let’s face it, they don’t always work right), had them sign a waiver, and we did our best.
Neither of these procedures are cheap in the realm of commercial PC repair, nor do they inspire a tremendous level of confidence in the technician or the hopeful client.
In an effort to expedite our repair time and retain the sanity of myself and other technicians, I received permission to undertake a case study on a variety of PCs currently in service that exhibited any of the aforementioned symptoms, and I took it upon myself to find a better solution. After crawling through the MSKB, Experts Exchange, MSDN and sundry websites all extolling the virtues of a solution to these problems, I only found one that worked, and it has been reliably serving me for the better part of two weeks on seventeen PCs to date. The process is simple: Get to the Windows Recovery Console for your particular Windows installation, navigate to the root letter of your installation (C: in most cases), issue eight commands, and reboot. The cornerstone of this process is a command called “BOOTCFG /Rebuild” which is a complete diagnostic of the operating system loaded into the recovery console; the purpose of the command is to remove/replace/repair any system files that were preventing the operating system from loading correctly. Amongst the files it fixes are:

Windows Hardware Abstraction Layer (HAL)
Corrupt registry hives (\\WINDOWS\\SYSTEM32\\CONFIG\\xxxxxx)
Invalid BOOT.INI files
A corrupt NTOSKRNL.EXE
A missing NT Loader (NTLDR)

The command process may apply to other types of blue screens or Hive/HAL/INI/EXE/DLL-related stop errors, but I have not had the luxury of computers in this type of disrepair. The process I am about to outline is virtually harmless, and if you feel you may be able to correct your PC’s boot-time blue screens and stop errors with the sequence, feel free to try. Let us now begin with a step-by-step instruction for correcting these issues.

Getting to the Windows Recovery Console

Insert your Windows XP CD into your CD and assure that your CD-ROM drive is capable of booting the CD. Configuring your computer to boot from CD is outside of the scope of this document, but if you are having trouble, consult Google for assistance.
Once you have booted from CD, do not select the option that states: “Press F2 to initiate the Automated System Recovery (ASR) tool.” You’re going to proceed until you see the following screen, at which point you will press the “R” key to enter the recovery console:

After you have selected the appropriate option from step two, you will be prompted to select a valid Windows installation (Typically number “1″). Select the installation number, (As mentioned, “1″ in most cases), and hit enter. If there is an administrator password for the administrator account, enter it and hit enter. You will be greeted with this screen, which indicates a recovery console at the ready:

Proceeding With the Repair Functions

There are eight commands you must enter in sequence to repair any of the issues I noted in the opening of this guide. I will introduce them here, and then show the results graphically in the next six steps. These commands are as follows:
- C:\CD ..
- C:\ATTRIB -H C:\\boot.ini
- C:\ATTRIB -S C:\\boot.ini
- C:\ATTRIB -R C:\\boot.ini
- C:\del boot.ini
- C:\BOOTCFG /Rebuild
- C:\CHKDSK /R /F
- C:\FIXBOOT
To “Go up a directory” in computing is to revert back to the directory above the current folder you’re operating in. If, for example, I’m in the C:\WINDOWS\SYSTEM32 directory, and I want to get at a file in the WINDOWS directory, I would merely type CD .. and I would be taken out of the SYSTEM32 folder and up one level to WINDOWS. We’re going to do the same thing here from the WINDOWS folder to get to the basic root of C:

Now that we are at C:\ we can begin the process of repairing the operating system
and that begins with modifying the attributes of the BOOT.INI file. Briefly, BOOT.INI controls what operating systems the Windows boot process can see, how to load them, and where they’re located on your disk. We’re going to make sure the file is no longer hidden from our prying eyes, remove the flag that sets it as an undeletable system file, and remove the flag that sets it as a file we can only read, but not write to. To do this, we will issue three commands in this step:

C:\ATTRIB -H C:\BOOT.INI
C:\ATTRIB -R C:\BOOT.INI
C:\ATTRIB -S C:\BOOT.INI

to remove the Hidden, System and Read Only flags.

Now that we’ve modified the attributes for the BOOT.INI file, it’s up for deletion. The syntax for it is simple: { DEL | FILE NAME }, e.g., C:\DEL BOOT.INI deletes the BOOT.INI file.

Now for the most important step of our process, the BOOTCFG /REBUILD command which searches for pre-existing installations of Windows XP and rebuilds sundry essential components of the Windows operating system, recompiles the BOOT.INI file and corrects a litany of common Windows errors. It is very important that you do one or both of the following two things: First, every Windows XP owner must use /FASTDETECT as an OS Load Option when the rebuild process is finalizing. Secondly, if you are the owner of a CPU featuring Intel’s XD or AMD’s NX buffer overflow protection, you must also use /NOEXECUTE=OPTIN as an OS Load Option. I will demonstrate both commands for the purpose of this guide, but do not set NOEXECUTE as a load option if you do not own one of these CPUs. For the “Enter Load Identifier” portion of this command, you should enter the name of the operating system you have installed. If, for example, you are using Windows XP Home, you could type “Microsoft Windows XP Home Edition” for the identifier. This gives the process some authenticity, if you’re keen on being a perfectionist.

This step verifies the integrity of the hard drive containing the Windows XP installation. While this step is not an essential function in our process, it’s still good to be sure that the drive is physically capable of running windows, in that it contains no bad sectors or other corruptions that might be the culprit. No screenshot necessary here! Just type CHKDSK /R /F at the C:> prompt. Let it proceed; it could take in excess of 30 minutes on slower computers, when this is finished move on to the seventh and final step.
This last step also requires no screenshot. When you are at the C:> prompt,
simply type FIXBOOT. This writes a new boot sector to the hard drive and cleans up all the loose ends we created by rebuilding the BOOT.INI file and the system files. When the Windows Recovery Console asks you if you are “Sure you want to write a new bootsector to the partition C: ?” just hit “Y,” then enter to confirm your decision.

Results and wrap-up

It’s time to reboot your PC by typing EXIT in the Windows Recovery Console and confirming the command with a stroke of the enter key. With any luck, your PC will boot successfully into Windows XP as if your various DLL, Hive, EXE and NTLDR errors never existed. You’ve just saved yourself from many hours of work, frustration, potential data loss and shelling out your hard-earned greenbacks at a brick’n'mortar operation.
Keep in mind that this solution is only designed to resolve the issues introduced in the preface if the cause is unrelated to spyware and viruses; while I have had significant luck with rebuilding heavily-infected systems in the method I have described, it is not guaranteed. If you believe your PC has affected one of these symptoms due to spyware or viruses, today’s fastest-growing PC nuisance, here is our recommended list of software that can help keep your computer safe:
Most of us have seen it at one time or another; perhaps on our own PC, the PC of a loved one, or perhaps a PC at your place of employment. The system spends weeks or months operating in a smooth fashion, taking you to the far reaches of the wide, wibbly web, and after one particularly late evening of browsing and gaming, you shut your PC off and go to bed. Millions of people across the globe do just this every night, but a few of us have turned our PCs on the next day not to the standard Windows XP loading screen, but instead this dreaded error:
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.
Which renders your PC inaccessible from the standard boot procedures of Windows XP. You try safe mode, to no avail. You’re particularly savvy and try issuing the FIXBOOT and FIXMBR commands in the Windows recovery console, but after each reboot, you’re merely greeted with the same obnoxious and terrifying blue screen of death that’s preventing you from accessing your precious data.
Perhaps you’ve also seen these error screens:
Windows NT could not start because the below file is missing or corrupt:
X:\\WINNT\\System32\\Ntoskrnl.exe
_________________
Windows NT could not start because the below file is missing or corrupt:
X:\\WINNT\\System32\\HAL.dll
_________________
NTLDR is Missing
Press any key to restart
_________________
Invalid boot.ini
Press any key to restart
Allow me to build tension by prefacing the end-all/be-all solution with my background: Having worked for the now-incorporated Geek Squad branch of Best Buy Corporation for the better part of eight months, I have seen dozens upon dozens of systems come through our department with any one of these errors, brought in by customers who are afraid they did something, have a virus, or are in jeopardy of losing their data. Prior to my discovery of an invaluable sequence of commands, our standard procedure was to hook the afflicted drive to an external enclosure, back up a customer’s data and then restore the PC with the customer’s restore discs or an identical copy of Windows with the customer’s OEM license key. If the customer wasn’t keen on the applicable charges for the data backup, we informed them of the potential risks for a Windows repair installation (Let’s face it, they don’t always work right), had them sign a waiver, and we did our best.
Neither of these procedures are cheap in the realm of commercial PC repair, nor do they inspire a tremendous level of confidence in the technician or the hopeful client.
In an effort to expedite our repair time and retain the sanity of myself and other technicians, I received permission to undertake a case study on a variety of PCs currently in service that exhibited any of the aforementioned symptoms, and I took it upon myself to find a better solution. After crawling through the MSKB, Experts Exchange, MSDN and sundry websites all extolling the virtues of a solution to these problems, I only found one that worked, and it has been reliably serving me for the better part of two weeks on seventeen PCs to date. The process is simple: Get to the Windows Recovery Console for your particular Windows installation, navigate to the root letter of your installation (C: in most cases), issue eight commands, and reboot. The cornerstone of this process is a command called “BOOTCFG /Rebuild” which is a complete diagnostic of the operating system loaded into the recovery console; the purpose of the command is to remove/replace/repair any system files that were preventing the operating system from loading correctly. Amongst the files it fixes are:

Windows Hardware Abstraction Layer (HAL)
Corrupt registry hives (\\WINDOWS\\SYSTEM32\\CONFIG\\xxxxxx)
Invalid BOOT.INI files
A corrupt NTOSKRNL.EXE
A missing NT Loader (NTLDR)