The system cannot start. Using the command line. The FIXBOOT command writes a new boot sector
Sometimes when you try to start or restart Windows XP, the above error may appear. This is due to missing or damaged necessary files. Windows registry. Sometimes other directories may be missing, for example: /WINDOWS/SYSTEM32/CONFIG/SOFTWARE, /WINDOWS/SYSTEM32/CONFIG/SYSTEM or /SystemRoot/System32/Config/SOFTWARE. In this case, errors may look like this:
- "Windows XP cannot start because the /WINDOWS/SYSTEM32/CONFIG/SOFTWARE file is corrupted or missing"
- "Stop: c0000218 (Registry file failure) The registry cannot load the partition family (file) /SystemRoot/System32/Config/SOFTWARE or its log or backup copy"
How to restore Windows XP boot.
A file error may also occur Lsass.exe. The reasons for these errors may be as follows:
- Incorrect or unexpected termination Windows operation.
- Problems with the hard drive of your computer or laptop, it may have failed or is almost out of order.
- You yourself, accidentally or on purpose, deleted Windows XP necessary for operation system files.
How can I remove this error and start Windows XP, the solution to the problem?
Besides reinstalling the operating system, there are several ways to solve this problem. The meaning of these methods comes down to restoring damaged or deleted files and registry directories.
First option.
You need to start the computer from a bootable CD/DVD disk or flash drive. Products such as Live CD from Dr.Web are suitable for this; it has a convenient built-in file manager and a program for checking your PC for viruses and Trojans. In order to boot a computer or laptop from a disk or flash drive, you need to press F1, F2 or Del when loading normally, and set the boot priority from the disk.
We boot, launch the file manager, select the /windows/system32/config/system directory on the left, /windows/repair/system on the right. We copy everything on the right into the left window. After this, reboot your computer or laptop, not forgetting to set it back to boot from hard drive. If the steps described above did not help, and the system does not start as before, then do not despair, since there is a second way to solve the problem.
Second option.
if you have installation disk With Windows XP, you can recover missing files using the Recovery Console. To do this, set the BIOS to boot from disk. When running from disk, press +R to launch the console Windows recovery. After starting, enter the commands sequentially, after entering each one, press +Enter:
MD tmp copy c:/windows/system32/config/system c:/windows/tmp/system.bak copy c:/windows/system32/config/software c:/windows/tmp/software.bak copy c:/windows/ system32/config/sam c:/windows/tmp/sam.bak copy c:/windows/system32/config/security c:/windows/tmp/security.bak copy c:/windows/system32/config/default c:/ windows/tmp/default.bak
delete c:/windows/system32/config/system delete c:/windows/system32/config/software delete c:/windows/system32/config/sam delete c:/windows/system32/config/security delete c:/windows/ system32/config/default
copy c:/windows/repair/system c:/windows/system32/config/system copy c:/windows/repair/software c:/windows/system32/config/software copy c:/windows/repair/sam c:/ windows/system32/config/sam copy c:/windows/repair/security c:/windows/system32/config/security copy c:/windows/repair/default c:/windows/system32/config/default
You can use standard features system: try to boot from the "latest successful configuration". This is done when the computer starts. Also, if you previously activated automatic recovery system, you can roll it back.
If you solved the problem, but the error repeats again and again, most likely there are serious problems with your hard drive and it does not have much life left, so consider replacing it and backup important data.
Windows cannot start due to a corrupted or missing file: \WINDOWS\SYSTEM32\CONFIG\SYSTEM You can try to restore this file by running the program Windows installations from the original installation CD-ROM. Select "r" in the first dialog screen to start the recovery procedure.
This is probably one of my least favorite problems with Windows, not counting the blue screens of death. And not in vain... the fact is that such a message in 90% of cases does not bode well and quick recovery systems can be forgotten.
Why such a gloomy forecast? It simply appears for two reasons (we will not consider the user’s curvature):
- A problem with hard drive- appeared on it bad sectors. I advise changing such disks in any case, even if there are not many BAD blocks and they can be “fixed”. No one can guarantee that this will be the end of the dying process of the screw.
- Stopping the computer "on the go" (power loss, no correct shutdown). Such cataclysms are precisely the key to the successful emergence of the first problem.
As I already said, quick ways there is no solution to the problem...
Method one
First, you can try to do what Microsoft suggests - boot from the installation disk. It is advisable to have an ORIGINAL disk with Windows (assemblies most likely will not work, since most of them do not have a recovery function) and boot from it.
Accordingly, after the installer shell appears, click R to download the recovery console:
Windows XP(TM) Recovery Console. Use the Recovery Console to troubleshoot and restore your system. Type EXIT to exit the recovery console and restart your computer. 1: C:\WINDOWS Which copy of Windows should I sign in to? (To cancel, press<ВВОД>) 1 Enter the administrator password:
Here we have Windows installed on the disk WITH:. When the system prompt appears:
C:\WINDOWS>
We give commands fixboot And fixmbr- fix and rewrite the bootloader and master boot record on the disk. We answer all questions in the affirmative. But that’s not all, now let’s run a disk check:
C:\WINDOWS>chkdsk C: /F /R
CHKDSK checks the specified disk (if you do not specify the disk explicitly, then the current one is checked).
- /F - check for errors and fix them automatically
- /R - search bad sectors and restoration of their contents. Requires the /F switch to be used
Reboot and see what happens. If the system files are not damaged, the system will come back to life.
Method two
The second method complements the first if it did not bring the desired result, because system files could end up on faulty areas hard drive.
So we will need boot disk or a flash drive with a file manager (a very simple Live CD from Dr.Web). In the next article I’ll tell you how to make a bootable USB flash drive with everything necessary software to restore computers.
First, it is advisable to check the surface of the disk (for example HDD program Regenerator), but you can try your luck right away, which will significantly reduce the recovery time if successful (if HDD in good condition).
- Booted from a disk or flash drive, we get access to our hard drive, on which the system is located.
- Copy the contents of the C:\Windows\repair\system folder to C:\Windows\system32\config\system and agree to the replacement.
Catalog \Windows\repair\system contains backup system files. By rebooting, you can get a working system (if luck is on your side today). If not... well then the only option left is a complete reinstallation.
It often happens that clients come to me with one problem, windows stopped loading due to a corrupted or missing \Windows\system32\config\system file
This usually happens on Windows XP
What to do in this case? Reinstall the system stupidly? This is an extreme and last thing. Let's go another way.
There are two options to restore Windows startup.
If none of them help, then you will only have to reinstall the system. But first we need to find out why this error occurred and Windows stopped loading.
The most common reasons for corruption of the system file is, as I noticed, either the lights were suddenly turned off and the computer was forcibly turned off (in short, an emergency shutdown of the computer). Either the hard drive has physically worn out and the so-called BAD sectors or damaged blocks, along with damage to the sector on the hard drive, system boot files are also lost.
Which leads to such a problem as Windows stopped loading due to a damaged or missing \Windows\system32\config\system file
The first solution to the problem, as written in the screenshot. You can try to recover this file by running Windows Setup from the original installation CD-ROM. Select 'r' on the first dialog screen to start the recovery procedure.
To do this we insert original disc with Windows XP (not a beast build, SamLab because the builds do not have a recovery function) into a CD drive and boot from it.
At this point, instead of Enter, press R to load the recovery console
If one OS is installed on the computer and it is located on drive C by default, then enter 1 and click enter.
If the password was set to account administrator dial the password and click Enter. If you have not set an administrator password, then skip, just press Enter.
When the system prompt appears:
C:\WINDOWS>
Enter fixboot
A message will appear:
End section: C:.
Do you want to record a new one? boot sector to section C:?
Enter y(which means yes) and click Enter
A message will appear:
File system on boot partition: NTFS (or FAT32).
The FIXBOOT command writes a new boot sector.
The new boot sector was successfully written.
C:\WINDOWS>
enter fixmbr
A message will appear:
**WARNING**
This computer has a non-standard or invalid primary boot record. Using FIXMBR may damage your existing partition table. This will result in loss of access to all sections current tough disk.
If there are no disk access problems, it is recommended that you abort the FIXMBR command.
Are you confirming the new MBR entry?
Enter y(which means yes) and click Enter
A message will appear:
A new master boot record is produced on physical disk\Device\Harddisk0\Partition0.
The new master boot record has been successfully created.
At the system invitation C:\WINDOWS>
enter exit, the computer will reboot. Enter Bios and prioritize booting from your hard drive.
For the second option To restore the system boot, we need a bootable LiveCD.
Boot from the disk, setting boot priority in BIOS from the SD-DVD drive
After LiveCD downloads launch the file manager, better Total Commander and open the following folders.
In the left window, open the full path indicated in the error when loading the system C:\Windows\system32\config\system provided that Windows folder installed on drive C.
Open in the right window From:/Windows/repair here are copies of system files.
Copying the file System from folder repair to a folder config, we affirmatively agree to the request to replace. In short, we replaced the damaged file system to working backup system.
We reboot the computer, boot from the hard drive and voila, the system starts to boot.
This method often helps, but not always. Various cases and there are reasons. If none of the options help, then unfortunately only reinstalling the system will help.
Reasons why operating room Windows system(Windows) may not load much. At least three: hardware failure, software glitch and HZ.
In my case, the laptop turned on, blinked the lights, loaded the BIOS, but that was all. Wherein BIOS settings no one changed and they were correct.
The hard drive was removed from the laptop and passed all tests perfectly. From which we conclude that the error is software. And since the BIOS does not issue any more messages, then most likely the partition table known as MBR (Master Boot Records) has failed.
Windows XP Home was installed on the laptop during its “lifetime”. Therefore, we take the installation Windows disk XP and use the recovery console. To do this, during boot (immediately after the BIOS prompt), press F12 and select boot from CD-ROM. Or if this is not possible, then go into the BIOS settings and change the boot order so that the CD-ROM comes first.
Don't forget to press any key in response to the invitation to boot from the CD-ROM.
After the installer loads everything into memory necessary files, you will be prompted with the Install Windows menu or launch recovery console(R).
Select R.
In most cases, computers have one operating system installed, so I will further consider this option. Moreover, this is the option on the “dead” laptop.
After loading the recovery console, the following message appears:
1: C:\WINDOWS Which copy of Windows should I sign in to?
Type 1 , press Enter.
A message will appear:
Enter the administrator password:
Enter your password, press Enter (if there is no password, just press Enter). As a rule, no one remembers the administrator password. But I was lucky, it simply wasn’t there, that is, we stupidly press Enter :)
A system prompt appears:
C:\WINDOWS>
enter fixmbr (don’t forget to press Enter) Actually, this is the command to restore a damaged partition table.
A message will appear:
**WARNING** This computer has a non-standard or invalid Master Boot Record. Using FIXMBR may damage your existing partition table. This will result in loss of access to all partitions of the current hard drive. If there are no disk access problems, it is recommended that you abort the FIXMBR command. Are you confirming the new MBR entry?
Type y (which means yes).
A message will appear:
A new master boot record is created on the physical disk DeviceHarddisk0Partition0. The new master boot record has been successfully created.
When the system prompt appears:
C:\WINDOWS>
Type fixboot
A message will appear:
End section: C:. Do you want to write a new boot sector to the C: partition?
Type y (which means yes).
A message will appear:
File system on boot partition: NTFS (or FAT32). The FIXBOOT command writes a new boot sector. The new boot sector was successfully written.
At the system invitation
C:\WINDOWS>
Enter exit, the PC will reboot. Press Del, sign in BIOS Setup and set to boot from your hard drive (if you changed the boot order).
I did all this with the ill-fated laptop. But Windows never booted. But instead of a black screen there was now the inscription
"Windows cannot start due to disk configuration hardware errors. The selected startup disk cannot be read. Please check the specified path and that the disk hardware is healthy. For more information about boot requirements hard parameters disk, see your Windows documentation and documentation for your hardware."
However, this “menacing” inscription only tells us that BOOT.INI is corrupted, that is, the table MBR partitions correct and the bootloader works. And the reason could be the following:
- The Default value in the boot section of the Boot.ini file is missing or corrupted.
- The location specified in the Boot.ini file is missing installed copy Windows XP
- The path to the partition in the Boot.ini file is incorrect.
To fix the Boot.ini file, use the Bootcfg recovery agent program.
To do this, let's start the computer again using the Windows XP CD.
Next, launch the Windows recovery system by pressing the R key when prompted.
Then select necessary copy Windows and when prompted, enter your administrator password.
Type bootcfg /rebuild and press ENTER.
After discovery copies of Windows appear following commands:
After completing the steps above, restart your computer and select the first option from the boot menu. After this, Windows XP should boot normally.
After successful download Windows systems XP, you can delete the incorrect entry in the Boot.ini file.
These manipulations helped me. The laptop started working, Windows booted, everyone was happy.
And problems that significantly complicate the operation of the PC, or even completely prevent it from starting. “Windows cannot start because the \WINDOWS\SYSTEM32\config\system file is corrupted or missing” is one of the most common errors encountered primarily by users of the Windows XP operating system (I haven’t encountered it on other versions yet, but anything can happen) , That's why this instruction designed more for this OS.
ADVICE. sometimes the same message may have different ending words. For example, instead of “system” it will be written “software”, “default” or “security”.
First, let's figure out what it is and where it came from. Speaking in simple language, the computer cannot boot due to a damaged system registry. Reinstalling the system is the easiest and most effective way solve the problem, but only if you are not afraid of losing data. This could happen for all sorts of reasons, from improper shutdown of the computer to worn out hard drive. Of course, in the latter case, it may be necessary to replace the hard drive, but not always. This does not change the essence of the error, so this manual should help in any case.
Fix Windows startup error.
So, you are trying to turn on your PC, and you receive a message that the \Windows\System32\config\system file is damaged. "Fix" system registry There are two ways: force the system to restore it yourself or fix the error manually. Let's start with a simpler option.
- Click “Restart computer”. In the process, press F8. The monitor will display additional options downloads.
- Select "Load last known known configuration".
- Reboot the computer again and see if the problem is resolved.
This method forces the operating system to use those configuration files under which the OS launched successfully. By restarting the system again, the boot error should no longer appear.
Manual System Restore
If previous method did not help, you should try to solve the problem manually. IN general outline, your task is to copy the backup boot files to the \system folder from \repair. There are several ways to do this.
Recovering using a file manager
Not to say that this method is more difficult than simply launching the last successful configuration, but there is one caveat: this method is suitable if you have a boot disk or flash drive with any manager. But, if you have to choose, a Live CD is best. Recording it on media is not so problematic, and the program will later be useful not only for system recovery, but also for a banal virus scan. So, if you have a disk, then do the following:
- Insert the media.
IMPORTANT. if the boot is not performed, then go into the BIOS and set the priority for USB or CD/DVD, depending on the boot resource.
- After everything has loaded, launch the explorer.
- In the explorer itself, open two tabs (almost all explorers allow this): in one - the same folder with: \windows\system32\config\system, and in the other - the folder with backup files with: \windows\repair\system. We look carefully at the damaged file, which, according to the system, should not have an extension.
ADVICE. The folder names are usually preceded by the letter C, but it may be different if they are on a different hard drive.
There is another, safer way. Instead of deleting damaged data, you can rename it, and then copy the original files from the recovery folder.
- Reboot and check if the problem is resolved.
Restoring using the command line
If you don’t have any manager at hand, and the problem needs to be solved urgently, then there is another way using command line. You can enter it in the following ways:
- Through safe mode. To do this, as mentioned earlier, press F8 immediately after restarting the PC. However, this mode does not always start, and sometimes does not support the command line.
- Using Windows XP media. There you can enter the console and find the same command line. To do this, after the welcome screen appears, press the R key and select the system needed to restore.
- Using media with Windows 7 or 8. We remember very well that we need XP to “fix” it, but this option is also acceptable for calling the console. Press Shift+F10 as soon as the language selection window appears.
The next step after opening the command line is to define specific name damaged file(software, system, sam, default or security) and the exact letter system disk, on which the OS is located. There are two commands for this:
- wmic logicaldisk get caption (to find out the letter of the system drive);
- dir c: (displays folders on drive C; if you don’t find folders with the desired name there, look at drive D in the same way).
Archiving existing files
copy c:\windows\system32\config\system c:\windows\system32\config\system.bak
Removing problematic files
delete c:\windows\system32\config\system
Restoring from a backup
copy c:\windows\repair\system c:\windows\system32\config\system
IMPORTANT. the commands may vary depending on which particular drive the file is located on and which of them is damaged.
For example, they can be written like this:
copy c:\windows\system32\config\software c:\windows\system32\config\software.bak
or so (if system folder located on drive D):
copy d:\windows\system32\config\sam c:\windows\system32\config\sam.bak
In the same way, the commands change in the future both when deleting and restoring a file. Exit the console (type and execute the Exit command) and restart the PC. If you entered everything correctly, the message should not appear again.
In some cases, none of the options help. This can only mean one thing - it's time to reinstall operating system completely, this will surely solve the problem. We hope everything worked out for you. If something remains unclear, ask questions!
