Windows System32 Config System Fix

How to Fix BAD SYSTEM CONFIG INFO: Repairing any blue screen of death errors is not an simple task. But, If you can find out or guess the appropriate reasons behind the errors, It will be much more easier to resolve BSODs. Before troubleshooting with actual methods, I recommend you to boot into safe mode and then boot into normal mode. If you are lucky, It may help you. 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.

Bad System Config Info is a common bug check error on Windows systems, caused mainly by malfunctioning of system and registry files or the Boot Configuration Data (BCD) file. Some boot order files in the BCD, or even some older ones, may conflict with newer, stable files. When this happens, the error otherwise known as the Blue Screen of Death (BSoD) occurs.

The bug check error can also be caused by:

  • faulty hardware
  • incorrect system settings
  • a bad driver
  • installing an important update

However, most error messages will often have a description of what the problem may be. Below are some tried and tested solutions to help you fix a Bad System Config Info error in Windows 10.

Related: Latest Windows 10 Update Problems and How to Fix Them

Check your hardware

Faulty hardware, like RAM or a bad hard drive, can cause the error. The easiest way to resolve it is by replacing your hard drive, but be sure to perform a detailed hardware inspection.

Update drivers

Incompatible or outdated drivers are a source of several issues, like they may hinder you from using some hardware. The worst thing bad drivers can do is bring up BSoD errors, such as the Bad System Config Info.

To resolve this, update your drivers as often as possible to ensure all major components have the latest drivers.

  • Verify that your devices all have the latest and correct drivers.
  • Visit your device manufacturer’s website, and download the latest drivers. (Choose only those compatible with your Windows 10 version.)
  • Install and update the drivers.

Note: you need to install and update as many drivers as required to fix this issue successfully.

bcdedit command

Quite often the Bad System Config Info error can appear when system configuration is incorrect or not configured properly. Additionally, if the memory and processors in the configuration file have the wrong value, the error will appear as well, preventing access to Windows 10.

To resolve this, trigger Windows 10 to access the Advanced Startup menu:

1. Click Start.

2. Click Power.

3. Press and hold Shift, and click Restart.

4. The “Choose an Option” screen will display. Select Troubleshoot.

5. In the Troubleshoot window select “Advanced Options.”

6. In the Advanced Options window select Command Prompt.

7. Your computer will restart and then display the Command Prompt blue screen. You’ll be asked to select an account to continue. Press Enter and then key in your password for that account.

8. Enter the following lines once Command Prompt starts:

Reinstall Windows System32 Config System

9. Close Command Prompt.

10. Start Windows 10 again.

Related: How to Troubleshoot Critical Structure Corruption in Windows 10

Fix BCD file

If your BCD file is corrupt or damaged, the Bad System Config Info error may appear and deny you access to Safe Mode and Windows 10 altogether.

To resolve this, you need your bootable USB flash drive with Windows 10 or installation DVD. You can also use the Media Creation Tool if you don’t have a bootable USB drive.

Fix

Here’s what to do next:

1. Insert the bootable Windows 10 installation DVD and boot from it.

2. Windows 10 setup will begin.

3. Click Next.

4. Click “Repair your computer.”

5. Select “Troubleshoot -> Advanced Options -> Command Prompt.”

6. Enter the following lines when Command Prompt starts. (Press enter after each line to execute it.)

7. Close Command Prompt.

8. Restart your computer.

Note: the last command you enter will delete and then recreate Master Boot Records. Be careful using it.

Fix the Registry

There are specific registry issues that can bring up the error, but you can repair the registry to resolve it by following these steps:

1. Boot from the Windows 10 installation DVD.

Windows System32 Config System Fix

2. Select “Troubleshoot -> Advanced Options -> Command Prompt.”

3. Enter the following lines when Command Prompt starts. (Press enter after each line to execute it.)

Note: the folders of each of these commands are renamed as you press Enter, and once this is done, Windows 10 won’t use them again. They can be deleted, but you’re better off renaming in case you need to do a system restore much later.

4. Next, enter the lines below into Command Prompt:

This process copies the registry’s backup and replaces old files. Close Command Prompt and restart your PC.

System Restore

If the other methods don’t help, this may be one of your last two solutions to try:

1. Click Start.

2. Click Power.

3. Press and hold Shift and click Restart.

4. Select “Troubleshoot -> Advanced Options -> System Restore.”

5. Choose your username.

Windows System32 Config System Fix Without Cd

6. Follow the on-screen prompts.

7. Select the restore point you want.

8. Click Next and wait for the process to complete.

Reset Windows 10

This is the last solution to try if none of the others worked. Before resetting, create a backup because once you reset Windows, all files will be deleted from the C partition.

1. Click Start.

2. Click Power.

3. Press and hold Shift and click Restart.

4. Select “Troubleshoot -> Reset this PC.”

5. Select “Remove everything -> Only the drive where Windows is installed -> Just remove my files.”

6. Click Reset and wait for it to complete the process. You’ll have a fresh Windows 10 installation once this is done.

The reset should fix the problem if it was related to your PC’s software.

Were you able to fix the Bad System Config Info error using any of these solutions? Tell us below.

Image Credit: Microsoft Support,Laptopmag

The Complete Windows 10 Customization Guide

In this ebook we’ll be exploring the multitude of options to fully customize Windows 10. By the end of this ebook you’ll know how to make Windows 10 your own and become an expert Windows 10 user.

Manual Recovery of Windows registry, c:windowssystem32configsystem - software, or corrupt hive file or hal.dll errors with no CD.


This information is supplied without warranty. It can help if done correctly. Use at your own risk. If this Fixes your problem please give $2 with paypal link at the bottom of this article.
This article may help with the following stop error messages.

Windows XP could not start because the following file is missing or corrupt:

WINDOWSSYSTEM32CONFIGSYSTEM

Windows XP could not start because the following File is missing or corrupt:

WINDOWSSYSTEM32CONFIGSOFTWARE

This stop message

Stop: c0000218 {Registry File Failure} The registry cannot load the hive (file): SystemRootSystem32ConfigSOFTWARE or its log or alternate

This system error

Unmountable boot volume


Don't forget to listen to your computer to see if it has the 'Clunk of death' in the hard drive before starting any windows repairs.

Recovering from a corrupt hive, windows system32/config file errors or even some registry stop errors like c0000218 can be easy if you know how to get into system restore without windows being able to load. In an earlier help page I wrote about using a Windows XP disk and using the recovery console to get to a very primitive but effective DOS like screen (command prompt) that allows the user the ability to put the files from the system restore folder into the system32 config folder to restore the registry.
This time I am going to do the repair without the aid of a live CD. I am using another computer to move the files. It can be done by using the run command from the start menu in XP.
First you need to have another computer and an adapter for the hard drive. If you don't have an adapter you can plug the hard drive into the inside of the computer that works. (This article assumes you know how to do this.)

Once you have the drive working on the functional computer, check to see what drive letter it ends up in the new computer. (This is important since you will need to know what drive letter to use in the run command.) I will be using the command prompt the same way I did with the XP CD only this will be from a Windows Command Prompt instead.
Click START
Click RUN
Type CMD
Hit the 'ENTER' key
You should now see a black window with white lettering. The following commands will be typed into the command prompt window.

1. Type: cd

( Reminder: between 'cd' and ' there should be a 'blank space' otherwise the command won't work. These are similar to old DOS commands where spaces had to go between each command so DOS knew where one command stopped and another started.)

Note: this is when you will have to know what letter the drive ended up being in the computer. For this example we will say it ended up being drive E:

2.Type: E: thats E with the colon symbol. Then hit enter.

3.Type: Cd system~1_resto~1

4.Type: dir

Then click enter

NOTICE: When you hit enter it will list all the restore points folders like 'rp1', 'rp2' we have to see the last restore point to copy the file from a recent backup. If the restore points have more than one page then you have keep on hitting the key to view the last restore point folder.

NOTICE: It is a good rule of thumb to choose the files from the restore point folder which the second to the last one.

5.Type: cd rp {with the second to the last restore point no. } (Note: Example: cd rp9. if rp10 is the last restore point. where last restore point no. =10)

Then click enter

6.Type: cd snapshot

NOTICE: Now the command Prompt will look like the example below.

c:system~1resto~1rp9snapshot

( Note : restore point 9 assumed for clarity of the content, you have to go to the last restore point folder as described in the previous lines) Now according to the error message we have to copy the appropriate file from the restore point folder.

II.

NOTE: The appropriate command should be used according to the error message. But often times I do both to make sure they match each other.

If the file 'system' is corrupted

Type: copy _registry_machine_system e:windowssystem32configsystem

Then click enter

If the file 'software' is corrupted

Type: copy _registry_machine_software e:windowssystem32configsoftware

Then click enter

Type: Exit


Now you should be able to remove the hard drive from the computer and put it back into the computer that was not working. Start the computer and see if it comes up without the error message.
If it does start correctly then you are finished.
If it does not start correctly go through the above steps again going back to a lower number in the restore points.
If it still does not start correctly you should stick the hard drive back in the working computer.
Go back to the command prompt
Type E: and hit ENTER When the prompt shows you as being on that drive,
Type chkdsk /r and hit Enter. This will do a very thorough scan of the hard drive including a surface and file scan.
The computer may tell you that it can not access the drive correctly and ask you if you want to check it on the next reboot (keep in mind that this is a time consuming process and can take several hours. Also if you have used a USB adapter, the system may not know where to find that drive till Windows starts up so you may get an error at boot.) if the error message comes up and you want to scan the drive then click okay and then reboot the computer. After you have scanned the drive take it out of the computer and put it back in the original computer and try rebooting.
If the computer will still not start a Windows Repair Install may fix the problem but keep in mind that once you start the Windows Repair Install that you will be removing all system restore points. If a repair install does not work then it may be time to back up the data on the drive and reinstall Windows from scratch.
Once again I remind you that once you have recovered your system you need to check your drive with software that can detect a bad drive. No sense in having the thing working again and have it quit after your repair. Better to know the drive is bad and replace it than go through all this just to have the drive die and loose it all again.

If this helped give $2 dollars with the PayPal Make a Donation button.

Please leave a comment with your Donation. Thanks... Dale
This recently added counter saves unique visitors. It does not count return visitors.